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

[Chris Stone]

Ovidiu,

On Wed, Feb 9, 2011 at 3:02 PM, Ovidiu Sas <osas at voipembedded.com> wrote:
> It may be that something on the way out that is changing the message.
> I've seen some routers messing with the INVITE that is sent out.
>
> I want to see the message as it is when it leaves opensips and before
> being sent out into the network.

Well, using this in the script:

loadmodule "tm.so"

route{
        xlog("L_INFO", "SIP message in route():\n");
        xlog("L_INFO", "$mb\n");

        forward("67.212.153.179");
        exit;
}

local_route {
        xlog("L_INFO", "SIP message in local_route():\n");
        xlog("L_INFO", "$mb\n");
}

The first message is logged, but nothing for the one in local_route().
 Sorry, don't mean to be stupid - guess I must be missing something
yet.....

Anyway, here's what was logged:

Feb 10 17:58:28 mars /usr/sbin/opensips[19343]: SIP message in route():
Feb 10 17:58:28 mars /usr/sbin/opensips[19343]: INVITE
sip:17204497101 at 67.212.153.178:5060;transport=udp SIP/2.0^M From:
"STONE C AND C"
<sip:+13038382386 at 208.94.157.10:5060>;tag=a9d5ed0-13c4-4d5489b4-2b1f9707-34d78458^M
To: <sip:17204497101 at 67.212.153.178:5060>^M Call-ID:
CXC-195-5df63d90-a9d5ed0-13c4-4d5489b4-2b1f9707-3c07ffca at 208.94.157.10^M
CSeq: 1 INVITE^M Via: SIP/2.0/UDP
208.94.157.10:5060;branch=z9hG4bK-fa3a0-4d5489b4-2b1f9707-5e2659b1^M
Max-Forwards: 69^M P-Asserted-Identity: "STONE C AND C  "
<sip:+13038382386 at cxc.dashcs.com:5060>^M Supported: timer,100rel^M
Content-Disposition: session;handling=required^M Contact:
<sip:+13038382386 at 208.94.157.10:5060;maddr=208.94.157.10;transport=udp>^M
Session-Expires: 1800^M Content-Type: application/sdp^M
Content-Length: 238^M ^M v=0^M o=Acme_UAS 0 1 IN IP4 208.94.157.10^M
s=SIP Media Capabilities^M c=IN IP4 208.94.157.10^M t=0 0^M m=audio
22478 RTP/AVP 0 18 101^M a=rtpmap:0 PCMU/8000^M a=rtpmap:18
G729/8000^M a=rtpmap:101 telephone-event/8000^M a=maxptime:20^M
a=sendrecv^M
Feb 10 17:58:31 mars /usr/sbin/opensips[19345]: INFO:core:buf_init:
initializing...
Feb 10 17:58:31 mars /usr/sbin/opensips[19345]: SIP message in route():
Feb 10 17:58:31 mars /usr/sbin/opensips[19345]: ACK
sip:17204497101 at 67.212.153.179:5060 SIP/2.0^M From: "STONE C AND C"
<sip:+13038382386 at 208.94.157.10:5060>;tag=a9d5ed0-13c4-4d5489b4-2b1f9707-34d78458
^M To: <sip:17204497101 at 67.212.153.178:5060>;tag=as6c8f0e36^M Call-ID:
CXC-195-5df63d90-a9d5ed0-13c4-4d5489b4-2b1f9707-3c07ffca at 208.94.157.10^M
CSeq: 1 ACK^M Via: SIP/2.0/UDP
208.94.157.10:5060;branch=z9hG4bK-fa3ba-4d5489b7-2b1fa2e2-68bee566^M
Max-Forwards: 69^M Contact:
<sip:+13038382386 at 208.94.157.10:5060;maddr=208.94.157.10;transport=udp>^M
Content-Length: 0^M ^M
Feb 10 17:58:39 mars /usr/sbin/opensips[19347]: INFO:core:buf_init:
initializing...
Feb 10 17:58:39 mars /usr/sbin/opensips[19347]: SIP message in route():
Feb 10 17:58:39 mars /usr/sbin/opensips[19347]: BYE
sip:17204497101 at 67.212.153.179:5060 SIP/2.0^M From: "STONE C AND C"
<sip:+13038382386 at 208.94.157.10:5060>;tag=a9d5ed0-13c4-4d5489b4-2b1f9707-34d78458
^M To: <sip:17204497101 at 67.212.153.178:5060>;tag=as6c8f0e36^M Call-ID:
CXC-195-5df63d90-a9d5ed0-13c4-4d5489b4-2b1f9707-3c07ffca at 208.94.157.10^M
CSeq: 2 BYE^M Via: SIP/2.0/UDP
208.94.157.10:5060;branch=z9hG4bK-fa417-4d5489bf-2b1fc19c-3af7df9c^M
Max-Forwards: 69^M Content-Length: 0^M ^M


Thanks


Chris