3 Aug
2005
3 Aug
'05
8:12 a.m.
Another option is to use subst_uri() to add a transport=tcp parameter to
R-URI and then use t_relay(). For more, see:
http://openser.org/docs/modules/0.10.x/textops.html#AEN136.
To check if there is already a transport parameter use the regexp
operator (uri=~";transport=").
Daniel
On 08/03/05 02:44, Klaus Darilion wrote:
You must use it in conjunction with an IP
address/port:
http://openser.org/docs/modules/0.10.x/tm.html#AEN270
regards,
klaus
Erich Nahum wrote:
On Wed, Aug 03, 2005 at 12:17:40AM +0200, Klaus
Darilion wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
Erich Nahum wrote:
Thanks for the response. I did try this, and got a parser error
that t_relay_to_tcp is unrecognized.
-Erich Thanks to Bogdan, who pointed out that my UAC was
not behaving
properly.
Having solved that problem in sipp, I now have a new issue. The UAC
is opening a TCP connection to the proxy, but the proxy then forwards
the INVITE to the UAS over UDP. I'm using the stock openser.cfg file.
Any suggestions?
If a user agents wants to receive messages via TCP, it has to
REGISTER with with a contact which includes the transport=tcp
parameter. If there is no transport parameter, UDP is the default
(according to the RFCs).
You can force TCP by using t_relay_to_tcp instead of t_relay.