[OpenSIPS-Users] Change in SDP/RTP routing with Opensips 1.4 and 1.6

Henk Hesselink opensips-users at voipro.nl
Wed Feb 9 02:23:43 CET 2011


Chris,

What does an ngrep trace on the interface (interfaces?) of the machine
show?  Are the packets changed when they leave the machine?  In that
case it must be happening on that machine, i.e. no external firewall
munging.  If that is the case then run OpenSIPS with debug level 9 or
so, save the output and then grep on the 2 different IP adresses that
are in the incoming/outgoing contact header to see why that header is
being changed.  That might give a clue as to the SDP routing.

Cheers,

Henk Hesselink


On 09-02-11 01:28, Chris Stone wrote:
> Ovidiu,
>
> On Tue, Feb 8, 2011 at 2:31 PM, Ovidiu Sas<osas at voipembedded.com>  wrote:
>> You din't posted a proper SIP capture (no UDP src/dst IP for your
>> packets), but it seems that you are having a firewall issue.  Just add
>
> I agree that it almost sounds like a firewall issue but....I
> completely disabled iptables on the server and tested again - issue
> persists...
>
> So the only other firewall is the PIX - external to this server. All
> of the protocol fixup in it for SIP is disabled. Not sure how the PIX
> can play in here when:
>
> UPSTREAM PROVIDER
>                |
>                |
>         PIX Firewall
>                |
>                |
>   Cisco 12 port Switch
>         |                  |
>         |                  |
> OpenSIPS     Asterisk
>
> Once the INVITE comes in, it would not see the PIX again - goes to
> Opensips and then Asterisk.....
>
>> an xlog into your opensips server and see that you will have no
>> entries in syslog.
>
> Added: xlog("L_ERR", "[method=$rm, from=$fu, to=$ru, src_ip=$si]\n");
>
> tested another call and the log entries do so up:
>
> Feb  8 17:22:53 mars /usr/sbin/opensips[7046]:
> INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255
> kb
> Feb  8 17:23:04 mars /usr/sbin/opensips[7058]: INFO:core:buf_init:
> initializing...
> Feb  8 17:23:04 mars /usr/sbin/opensips[7058]: [method=INVITE,
> from=sip:+13038382386 at 208.94.157.10:5060,
> to=sip:17204497101 at 67.212.153.178:5060;transport=udp,
> src_ip=208.94.157.10]
> Feb  8 17:23:07 mars /usr/sbin/opensips[7066]: INFO:core:buf_init:
> initializing...
> Feb  8 17:23:07 mars /usr/sbin/opensips[7066]: [method=ACK,
> from=sip:+13038382386 at 208.94.157.10:5060,
> to=sip:17204497101 at 67.212.153.179:5060, src_ip=208.94.157.10]
> Feb  8 17:23:18 mars /usr/sbin/opensips[7058]: [method=BYE,
> from=sip:+13038382386 at 208.94.157.10:5060,
> to=sip:17204497101 at 67.212.153.179:5060, src_ip=208.94.157.10]
>
>> The INVITE that is sent out is having the same "Max-Forwards" counter
>> and you have a second Via with exactly the same branch parameter.
>
> Would that not be then the result some 'default' within Opensips since
> it's occurring with such a basic simple config? The config just calls
> forward() essentially. No modules are loaded or initialized and the
> route() block looks simply like:
>
> route{
>          xlog("L_ERR", "[method=$rm, from=$fu, to=$ru, src_ip=$si]\n");
>          forward("67.212.153.179");
>          exit;
> }
>
>
> Thanks!
>
> Chris
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>



More information about the Users mailing list