* Andres andres@telesip.net [050313 19:15]:
As I said I already have a solution to this. Using it I can know if a call did timeout because the gateway is dead, or it did timeout because the callee didn't answer which is all that I want. I tested it and it works just fine.
Dan,
Could you please share you ser.cfg trick to solve this issue? I am trying the "set flag" approach but have not quite nailed it.
In you reply_route, setflag(10);
and in failure_route(..);
if(is_flag_set(10)){
do_your_stuff();
};
Thanks,
-- Andres Network Admin http://www.telesip.net
Serdev mailing list serdev@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev
Atle Samuelsen wrote:
- Andres andres@telesip.net [050313 19:15]:
As I said I already have a solution to this. Using it I can know if a call did timeout because the gateway is dead, or it did timeout because the callee didn't answer which is all that I want. I tested it and it works just fine.
Dan,
Could you please share you ser.cfg trick to solve this issue? I am trying the "set flag" approach but have not quite nailed it.
In you reply_route, setflag(10);
and in failure_route(..);
if(is_flag_set(10)){
do_your_stuff();
};
Thanks Atle, We got it working as expected now.
We got it working as expected now.
What value is best for fr_timer? I am thinking between 5 to 10 seconds.
We have been using 8 on our network the past 2 years. Works fine.
Richard
Atle Samuelsen writes:
i have a question related to this:
In you reply_route, setflag(10);
in order to get to reply route, one must call t_on_reply(x) in a route block. is there some way to unset t_on_reply in reply_route and thus prevent further replies getting into there?
if i remember correctly, one must re-call t_on_failure in failure route, but t_on_reply seems to stick on forever.
-- juha
-----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Sunday, March 13, 2005 7:52 PM To: Atle Samuelsen Cc: serusers@lists.iptel.org Subject: [Serusers] Re: [Serdev] [Patch] Ability to check negative replycode in the failure_route
Atle Samuelsen writes:
i have a question related to this:
In you reply_route, setflag(10);
in order to get to reply route, one must call t_on_reply(x) in a route block. is there some way to unset t_on_reply in reply_route and thus prevent further replies getting into there?
if i remember correctly, one must re-call t_on_failure in failure route, but t_on_reply seems to stick on forever.
-- juha
try t_on_reply("0").
Richard
Does anybody know of an open Source SIP Soft phone that supports g723 and works on windows?
Thanks Deepak Singhal
I don't know if this will help, but you can try this link.
http://www.iptel.org/info/products/sipphones.php
Regards, Paul
On Mon, 14 Mar 2005 14:54:44 +0530, Deepak Singhal dsinghal@hotwireindia.com wrote:
Does anybody know of an open Source SIP Soft phone that supports g723 and works on windows?
Thanks Deepak Singhal
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers