[Kamailio-Users] Recording RTP session

Vikram Ragukumar vragukumar at signalogic.com
Fri Mar 26 16:28:28 CET 2010


Hector,

Seems like rtpproxy is allocating an rtp session properly. However 
rtpproxy's stats show that there are no RTP packets from the caller. I 
would recommend using wireshark or tcpdump, and
(a) Verifying the connection address in the SDP for messages leaving the 
proxy
(b) Make sure RTP packets are actually coming into the proxy from both 
endpoints.

Regards,
Vikram.

> Vikram
> 
> Thanks, that solved that problem but now I can only hear audio in one direction and here is what I see in the log
> 
> Mar 26 16:11:43 openser rtpproxy[30827]: DBUG:handle_command: received command "21119_2 U 1de249c9-f1fbbfa at 192.168.0.3 195.176.213.123 16476 a489077dc86f9d6o0;1"
> Mar 26 16:11:43 openser rtpproxy[30827]: INFO:handle_command: new session 1de249c9-f1fbbfa at 192.168.0.3, tag a489077dc86f9d6o0;1 requested, type strong
> Mar 26 16:11:43 openser rtpproxy[30827]: INFO:handle_command: new session on a port 60268 created, tag a489077dc86f9d6o0;1
> Mar 26 16:11:43 openser rtpproxy[30827]: INFO:handle_copy: starting recording RTP session on port 60268
> Mar 26 16:11:43 openser rtpproxy[30827]: INFO:handle_copy: starting recording RTCP session on port 60269
> Mar 26 16:11:43 openser rtpproxy[30827]: INFO:handle_copy: starting recording RTP session on port 0
> Mar 26 16:11:43 openser /usr/sbin/openser[21119]: ROUTE 4
> Mar 26 16:11:43 openser rtpproxy[30827]: INFO:handle_copy: starting recording RTCP session on port 0
> Mar 26 16:11:43 openser rtpproxy[30827]: INFO:handle_command: pre-filling caller's address with 195.176.213.123:16476
> Mar 26 16:11:43 openser rtpproxy[30827]: DBUG:doreply: sending reply "21119_2 60268 217.193.160.45 "
> Mar 26 16:11:43 openser /usr/sbin/openser[21119]: ROUTE 1
> Mar 26 16:11:43 openser /usr/sbin/openser[21123]: ONREPLY_ROUTE
> Mar 26 16:11:44 openser /usr/sbin/openser[21124]: ONREPLY_ROUTE
> Mar 26 16:11:44 openser rtpproxy[30827]: DBUG:handle_command: received command "21124_2 L 1de249c9-f1fbbfa at 192.168.0.3 62.65.128.61 12026 a489077dc86f9d6o0;1 f99504f8b00f1bd3fdfde331;1"
> Mar 26 16:11:44 openser rtpproxy[30827]: INFO:handle_command: lookup on ports 60268/37082, session timer restarted
> Mar 26 16:11:44 openser rtpproxy[30827]: INFO:handle_command: pre-filling callee's address with 62.65.128.61:12026
> Mar 26 16:11:44 openser rtpproxy[30827]: DBUG:doreply: sending reply "21124_2 37082 217.193.160.45 "
> Mar 26 16:11:44 openser /usr/sbin/openser[21121]: ROUTE_3^M
> Mar 26 16:11:48 openser /usr/sbin/openser[21120]: ROUTE_3^M
> Mar 26 16:11:49 openser /usr/sbin/openser[21126]: ONREPLY_ROUTE
> Mar 26 16:11:49 openser rtpproxy[30827]: DBUG:handle_command: received command "21126_2 L 1de249c9-f1fbbfa at 192.168.0.3 62.65.128.61 12026 a489077dc86f9d6o0;1 f99504f8b00f1bd3fdfde331;1"
> Mar 26 16:11:49 openser rtpproxy[30827]: INFO:handle_command: lookup on ports 60268/37082, session timer restarted
> Mar 26 16:11:49 openser rtpproxy[30827]: DBUG:doreply: sending reply "21126_2 37082 217.193.160.45 "
> Mar 26 16:11:49 openser /usr/sbin/openser[21122]: ACCOUNTING START
> Mar 26 16:11:49 openser /usr/sbin/openser[21122]: ACC: request accounted: timestamp=1269616309;method=ACK;from_tag=a489077dc86f9d6o0;to_tag=f99504f8b00f1bd3fdfde331;call_id=1de249c9-f1fbbfa at 192.168.0.3;code=200;reason=ok
> Mar 26 16:11:49 openser /usr/sbin/openser[21122]: ROUTE 1
> Mar 26 16:12:02 openser /usr/sbin/openser[21123]: ACCOUNTING STOP
> Mar 26 16:12:02 openser /usr/sbin/openser[21123]: ACC: request accounted: timestamp=1269616322;method=BYE;from_tag=f99504f8b00f1bd3fdfde331;to_tag=a489077dc86f9d6o0;call_id=1de249c9-f1fbbfa at 192.168.0.3;code=200;reason=ok
> Mar 26 16:12:02 openser /usr/sbin/openser[21123]: ROUTE 1
> Mar 26 16:13:03 openser rtpproxy[30827]: INFO:process_rtp: session timeout
> Mar 26 16:13:03 openser rtpproxy[30827]: INFO:remove_session: RTP stats: 587 in from callee, 0 in from caller, 587 relayed, 0 dropped
> Mar 26 16:13:03 openser rtpproxy[30827]: INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped
> Mar 26 16:13:03 openser rtpproxy[30827]: INFO:remove_session: session on ports 60268/37082 is cleaned up
> 
> I don't see any error messages. Any pointers?
> 
> Héctor
> 
> -----Original Message-----
> From: Vikram Ragukumar [mailto:vragukumar at signalogic.com] 
> Sent: Freitag, 26. März 2010 15:49
> To: Ortiz Héctor, SCS-SIS-ICC-SPC-SBU
> Cc: klaus.mailinglists at pernau.at; users at lists.kamailio.org
> Subject: Re: [Kamailio-Users] Recording RTP session
> 
> Hector,
> 
>> Just out of curiosity, could you please share your config file? 
>>
>> If I don't do the NAT detection and try using the function force_rtp_proxy and cannot hear sound in any direction, the called gets disconnected and see the following in the log
>>
>> Mar 26 14:15:11 openser /usr/sbin/openser[19389]: ONREPLY_ROUTE
>> Mar 26 14:15:11 openser /usr/sbin/openser[19389]: ERROR:nathelper:extract_body: message body has length zero
>> Mar 26 14:15:11 openser /usr/sbin/openser[19389]: ERROR:nathelper:force_rtp_proxy2_f: can't extract body from the message
> 
>  From the log it appears that you are trying to read the SDP from a SIP 
> message that does not contain an SDP. You might have to qualify your 
> force_rtp_proxy() call with an appropriate 'if' statement.
> 
> Regards,
> Vikram.
> 
> 
>> Regards
>>
>> Héctor
>>
>> -----Original Message-----
>> From: Klaus Darilion [mailto:klaus.mailinglists at pernau.at] 
>> Sent: Freitag, 26. März 2010 14:08
>> To: Ortiz Héctor, SCS-SIS-ICC-SPC-SBU
>> Cc: users at lists.kamailio.org
>> Subject: Re: [Kamailio-Users] Recording RTP session
>>
>>
>>
>> Am 26.03.2010 12:15, schrieb Hector.Ortiz at swisscom.com:
>>> Hi, I solved my issue. There was nothing wrong with my configuration.
>>>
>>> RTPProxy wasn't being enforced because the SIP Phone wasn't being detected as being behind NAT.
>> This is why I always remove NAT-detection as I want the rtpproxy in all 
>> cases.
>>
>> regards
>> klaus
>>
>>> I disabled SIP ALG on my ADSL Modem and now RTPProxy is being enforced and I'm able to do the recording. Now I have to find out how can I play the stored audio.
>>>
>>> Thanks for your help
>>>
>>> Héctor
>>>
>>> -----Original Message-----
>>> From: Klaus Darilion [mailto:klaus.mailinglists at pernau.at]
>>> Sent: Dienstag, 23. März 2010 16:01
>>> To: Ortiz Héctor, SCS-SIS-ICC-SPC-SBU
>>> Cc: users at lists.kamailio.org
>>> Subject: Re: [Kamailio-Users] Recording RTP session
>>>
>>>
>>>
>>> Am 23.03.2010 09:57, schrieb Hector.Ortiz at swisscom.com:
>>>> How can I then troubleshoot that it is really enforcing it?
>>> You have to put xlog() statements in your config (e.g. after an if ()
>>> statement in the blocks) and then watch syslog for the xlog messages -
>>> this is the way how you trace how a message is processed by the script.
>>>
>>> btw: if you always want to enforce the media relay then remove the if()
>>> conditions before the force_rtp_proxy calls.
>>>
>>> klaus
>> _______________________________________________
>> Kamailio (OpenSER) - Users mailing list
>> Users at lists.kamailio.org
>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
> 





More information about the sr-users mailing list