24 Jan
2008
24 Jan
'08
4:26 p.m.
Hey Peter,
I tried getting this going a while ago and wound up reconfiguring UM to stop
doing the redirect with this command: Set-UMDialPlan -Identity "My DialPlan"
-VOIPSecurity:unsecured
In Unsecured mode there are no redirects... I still had trouble getting the
UDP <-> TCP gateway working as desired so I hope you post your config after
its working!
Peter P GMX wrote:
UM2007 gives back the transport parameter which it receives.
If I add transport=tcp then the next 302 message answers with contact:
...... transport=tcp, so OpenSER can Reinvite on TCP.
If I add transport=udp then the next 302 message answers with contact:
...... transport=udp, so OpenSER will Reinvite via UDP and UM will not
accept it.
Unfortunately UM2007 only accepts TCP so OpenSER has to mediate between
tcp and udp (UA).
Best regards
Peter
Iñaki Baz Castillo schrieb:
--
View this message in context:
http://www.nabble.com/Openser-1.3-How-to-rewrite-transport-protocol-from-ud…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
On Thursday 17 January 2008 18:17:39 Peter P GMX
wrote:
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
Yes it does. Any way to suppress it, before I set
it to tcp?
Is really needed "transport=XXX" parameter in the RURI ??? what for?
If the proxy must contact a UAS yb TCP then it will use TCP as transport
layer, but AFAIK is not necessary at all to indicate it in the RURI.
In fact, note that the INVITE from the proxy to UM server arrives by TCP
with "transport=UDP" in the RURI and the INVITE is accepted !
Or maybe I'm wrong? Regards.