Hi, We are planning to use Openser in a large scale deployment. We are planning to stick to Linksys ATAs and IP Phones. Now all these phones have good NAT handling capablities. I just wanted to understand if it is better to handle these parameters on the UA side instead of Openser side. Will it cause some overhead to reduce at the Openser side. By using these UAs is it also possible to eliminate the use of Mediaproxy/RTPproxy at the Server side. I have the Openser working fine with Mediaproxy but I just wanted some expert suggestion from the people who are using these kind of UAs.
Thanks,
w/regards, Jayesh.
__________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/
Hi Users,
I have a problem with timeout for serial forking: I want to deviate a certain type of call to Voicemail after 19 seconds, then i do: ... modparam("tm", "fr_inv_timer_avp", "fr_inv_timeout") ... if (uri=~"^sip:xyz") { # set timeout for VoiceMail avp_write("i:19", "fr_inv_timeout"); t_on_failure("1"); }; ... if (!t_relay()) { sl_reply_error(); }; ... failure_route[1] { # send it to VM rewritehostport("xxx.xxx.xxx.xxx:5060"); forward(uri:host, uri:port); }
when the timer hits, OpenSER sends a new INVITE to VoiceMail and a 408 Request Timeout to the calling UA. this cause the calling UA (X-Lite) to hang up. is it my bad implementation or is it a problem of X-Lite? same configuration works when I call with an ALLNET Phone...
thanks for your interest, Stefano
Stefano Capitanio wrote:
Hi Users,
I have a problem with timeout for serial forking: I want to deviate a certain type of call to Voicemail after 19 seconds, then i do: ... modparam("tm", "fr_inv_timer_avp", "fr_inv_timeout") ... if (uri=~"^sip:xyz") { # set timeout for VoiceMail avp_write("i:19", "fr_inv_timeout"); t_on_failure("1"); }; ... if (!t_relay()) { sl_reply_error(); }; ... failure_route[1] { # send it to VM rewritehostport("xxx.xxx.xxx.xxx:5060"); forward(uri:host, uri:port);
I guess you have to use t_relay(...) instead of forward - you have to handle the whole scenario with tm module.
regards klaus
}
when the timer hits, OpenSER sends a new INVITE to VoiceMail and a 408 Request Timeout to the calling UA. this cause the calling UA (X-Lite) to hang up. is it my bad implementation or is it a problem of X-Lite? same configuration works when I call with an ALLNET Phone...
thanks for your interest, Stefano
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
with t_relay, when timer hits, openSER doesn't even send the new INVITE, it send only the 408 Request Timeout, and i have following errors in log:
ERROR: t_forward_nonack: no branched for forwarding ERROR: w_t_relay (failure mode): forwarding failed ERROR: run_failure_handlers: Error in do_action
and it doesn't work neither with the ALLNET Phone.
thanks for any help, Stefano
Klaus Darilion ha scritto:
Stefano Capitanio wrote:
Hi Users,
I have a problem with timeout for serial forking: I want to deviate a certain type of call to Voicemail after 19 seconds, then i do: ... modparam("tm", "fr_inv_timer_avp", "fr_inv_timeout") ... if (uri=~"^sip:xyz") { # set timeout for VoiceMail avp_write("i:19", "fr_inv_timeout"); t_on_failure("1"); }; ... if (!t_relay()) { sl_reply_error(); }; ... failure_route[1] { # send it to VM rewritehostport("xxx.xxx.xxx.xxx:5060"); forward(uri:host, uri:port);
I guess you have to use t_relay(...) instead of forward - you have to handle the whole scenario with tm module.
regards klaus
}
when the timer hits, OpenSER sends a new INVITE to VoiceMail and a 408 Request Timeout to the calling UA. this cause the calling UA (X-Lite) to hang up. is it my bad implementation or is it a problem of X-Lite? same configuration works when I call with an ALLNET Phone...
thanks for your interest, Stefano
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
add an "append_branch()" in failure route, before t_relay().
regards, bogdan
Stefano Capitanio wrote:
with t_relay, when timer hits, openSER doesn't even send the new INVITE, it send only the 408 Request Timeout, and i have following errors in log:
ERROR: t_forward_nonack: no branched for forwarding ERROR: w_t_relay (failure mode): forwarding failed ERROR: run_failure_handlers: Error in do_action
and it doesn't work neither with the ALLNET Phone.
thanks for any help, Stefano
Klaus Darilion ha scritto:
Stefano Capitanio wrote:
Hi Users,
I have a problem with timeout for serial forking: I want to deviate a certain type of call to Voicemail after 19 seconds, then i do: ... modparam("tm", "fr_inv_timer_avp", "fr_inv_timeout") ... if (uri=~"^sip:xyz") { # set timeout for VoiceMail avp_write("i:19", "fr_inv_timeout"); t_on_failure("1"); }; ... if (!t_relay()) { sl_reply_error(); }; ... failure_route[1] { # send it to VM rewritehostport("xxx.xxx.xxx.xxx:5060"); forward(uri:host, uri:port);
I guess you have to use t_relay(...) instead of forward - you have to handle the whole scenario with tm module.
regards klaus
}
when the timer hits, OpenSER sends a new INVITE to VoiceMail and a 408 Request Timeout to the calling UA. this cause the calling UA (X-Lite) to hang up. is it my bad implementation or is it a problem of X-Lite? same configuration works when I call with an ALLNET Phone...
thanks for your interest, Stefano
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
ok that's works perfectly!!! thank you very much, Stefano
Bogdan-Andrei Iancu ha scritto:
Hi,
add an "append_branch()" in failure route, before t_relay().
regards, bogdan
Stefano Capitanio wrote:
with t_relay, when timer hits, openSER doesn't even send the new INVITE, it send only the 408 Request Timeout, and i have following errors in log:
ERROR: t_forward_nonack: no branched for forwarding ERROR: w_t_relay (failure mode): forwarding failed ERROR: run_failure_handlers: Error in do_action
and it doesn't work neither with the ALLNET Phone.
thanks for any help, Stefano
Klaus Darilion ha scritto:
Stefano Capitanio wrote:
Hi Users,
I have a problem with timeout for serial forking: I want to deviate a certain type of call to Voicemail after 19 seconds, then i do: ... modparam("tm", "fr_inv_timer_avp", "fr_inv_timeout") ... if (uri=~"^sip:xyz") { # set timeout for VoiceMail avp_write("i:19", "fr_inv_timeout"); t_on_failure("1"); }; ... if (!t_relay()) { sl_reply_error(); }; ... failure_route[1] { # send it to VM rewritehostport("xxx.xxx.xxx.xxx:5060"); forward(uri:host, uri:port);
I guess you have to use t_relay(...) instead of forward - you have to handle the whole scenario with tm module.
regards klaus
}
when the timer hits, OpenSER sends a new INVITE to VoiceMail and a 408 Request Timeout to the calling UA. this cause the calling UA (X-Lite) to hang up. is it my bad implementation or is it a problem of X-Lite? same configuration works when I call with an ALLNET Phone...
thanks for your interest, Stefano
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Jayesh,
it is not something general accepted, but my personal advice is to try to do the nat traversal on the client side - if it has a robust and correct STUN implementation, use it. use nat traversal only for phones without STUN (or with bogus STUN) and for corner-cases when STUN does not work at all.
doing this, yo will minimize the impact on the server.
regards, bogdan
Jayesh Nambiar wrote:
Hi, We are planning to use Openser in a large scale deployment. We are planning to stick to Linksys ATAs and IP Phones. Now all these phones have good NAT handling capablities. I just wanted to understand if it is better to handle these parameters on the UA side instead of Openser side. Will it cause some overhead to reduce at the Openser side. By using these UAs is it also possible to eliminate the use of Mediaproxy/RTPproxy at the Server side. I have the Openser working fine with Mediaproxy but I just wanted some expert suggestion from the people who are using these kind of UAs.
Thanks,
w/regards, Jayesh.
Here₼s a new way to find what you're looking for - Yahoo! Answers http://us.rd.yahoo.com/mail/in/yanswers/*http://in.answers.yahoo.com/
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Jayesh Nambiar -
Klaus Darilion -
Stefano Capitanio