[Users] force_rtp_proxy() problem.
bogdan at voice-system.ro
Wed Aug 3 10:03:51 CEST 2005
double-check if you do not call twice force_rtp_proxy() for the INVITE -
this might be the reason for the double IP in "c=" - as hint: notice you
have the "a=nortpproxy:yes" twice!
Ray Van Dolson wrote:
>Thanks for the help earlier Bogdan.
>I've gotten things working for the most part, but am having a problem with the
>Once again, here is my setup:
> - 10.0.201.196
> - eth0: 188.8.131.52/24
> - eth1: 10.0.201.5/24
> - eth0: 184.108.40.206/24
> - eth1: 10.0.201.6/24
>Yes, Asterisk and OpenSER are on the same Private network currently. This is
>just for testing as clients were originally connecting directly to Asterisk.
>It will not always be the case.
>I have registration working correctly.
>If my SIP ATA makes an outbound call (INVITE) it appears to inform Asterisk in
>its SDP payload that media traffic (RTP) should be sent back to 10.0.201.5 (on
>eth1). Asterisk has no problem with this since it also has an IP on the
>10.0.201.0/24 network. However this obviously will not always be the case. I
>want media (RTP) to travel back via the eth0 IP addresses.
>I've tried the following:
> force_rtp_proxy("", "220.127.116.11")
>To hopefully force my media address to be the IP on eth0 on OpenSER. However,
>calls no longer succeed and I see the following in the SDP payload now:
>o=- 1298429 1298429 IN IP4 10.0.201.196
>c=IN IP4 18.104.22.1680.0.201.5
>m=audio 3508835088 RTP/AVP 0 2 4 8 18 96 97 98 100 101
>As you can see, the info in c= has both IP's and they are not seperate by a
>space. This same phenomenon occurs even if I use force_rtp_proxy by itself or
>with any of the flags.
>Normally there is just one IP address in this field it seems.
>Is this a bug in force_rtp_proxy or am I doing something incorrectly?
More information about the sr-users