Hi Michael,
I'm afraid I'm not following the scenario - rport is used only for
routing back replies for a requests - it has no usage outside the scope
of a transaction, and there is no way for a rport value to get into RURI...
Do you have a full SIP trace to show your case ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/28/2013 06:44 PM, Michael Schloh von Bennewitz wrote:
Hello list,
OpenSIPS 1.7.2
Solaris 11 AMD64
My OpenSIPS relays INVITEs from registered UACs to a upstream
gateway. OpenSIPS sends the INVITE over a random port. It listens
on 12.34.56.78:5060.
VIA RPORT
The upstream gateway writes the sending random port as
rport=<num-here> in the topmost Via of all replies as if
my OpenSIPS server were behind NAT (it's not though.)
When the upstream gateway sends new messages like reINVITE
or BYE, the RURI is like this:
BYE sip:[email protected]:<rport-num-here>
OpenSIPS sees that the BYE has a totag and relays happily to
a port that's not listening, leading to 477 send failed.
QUESTIONS
How can I avoid getting the rport port number in the RURI?
Or what to do about it in the route block of the config?
Regards,
Michael
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
