[OpenSIPS-Users] RTP Proxy Help

[Aqs Younas]

Have you transcoded your file to PCMU? What is the format of file you are
using?

On 10 March 2016 at 19:44, Jim DeVito <jim at devito.cc> wrote:

> Thanks Richard. I don't think that is true in this case as the DBUG output
> below comes right from running rtpproxy in the foreground so I would see
> the crash there. I'll look into rtpengine but that would require moving to
> 2.x.x and I need to be at 1.11.6 for the LTS right now.
>
> Thanks!!
>
> ---
> Jim DeVito
>
>
> On 2016-03-10 06:31, Richard Robson wrote:
>
>> Check the RTPProxy is not Segfaulting.
>>
>> I found that the Daemon was segfaulting despite seeming to be available.
>>
>> I have stopped using this and have found RTPEngine to work OK
>>
>> R
>>
>> On 10/03/2016 14:26, Jim DeVito wrote:
>>
>>> So it seems I have not had any luck getting rtpproxy to play an
>>> announcement upon receipt of the initial INVITE with SDP.
>>>
>>> Here is what I have when processing the initial invite from the client.
>>>
>>> rtpproxy_offer("r","");
>>> rtpproxy_stream2uac("/var/rtpproxy/audio/calling-area-error", "2");
>>> send_reply("503","No Routes");
>>>
>>> rtpproxy debug shows this on the INVITE before any reply is sent to
>>> the client.
>>>
>>> DBUG:get_command:GLOBAL: received command "19394_5 Uc0,101
>>> 2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060 66.228.40.119
>>> 10148 as1d2ea467;1"
>>> INFO:rtpp_command_ul_handle:GLOBAL: new session
>>> 2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060, tag as1d2ea467;1
>>> requested, type strong
>>>
>>> INFO:rtpp_command_ul_handle:2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060
>>> :
>>> new session on a port 37018 created, tag as1d2ea467;1
>>>
>>> INFO:rtpp_command_ul_handle:2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060
>>> :
>>> pre-filling caller's address with 66.228.40.119:10148
>>> DBUG:rtpc_doreply:GLOBAL: sending reply "37018
>>> "
>>> DBUG:get_command:GLOBAL: received command "19394_6 P2
>>> 2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060
>>> /var/rtpproxy/audio/calling-area-error session as1d2ea467;1 "
>>> INFO:handle_play:2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060:
>>> 2 times playing prompt /var/rtpproxy/audio/calling-area-error codec 0
>>> DBUG:rtpc_doreply:GLOBAL: sending reply "0
>>>
>>> Looks like it gets the Address and port from the INVITE SDP and sets
>>> them just fine. Then it even looks like it is playing the file. But no
>>> RTP is ever sent to the client and the next line that sends the 503 is
>>> immediately processed ending the call.
>>>
>>> Then rtpproxy will timeout like so.
>>>
>>> INFO:process_rtp:2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060:
>>> session timeout
>>> INFO:remove_session:2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060:
>>> RTP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped
>>> INFO:remove_session:2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060:
>>> RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped
>>> INFO:remove_session:2494595e5addcc12036b84f75312af3f at 66.228.40.119:5060:
>>> session on ports 37018/0 is cleaned up
>>>
>>> Any insight as to what I may be doing wrong would be a big help.
>>>
>>> Thanks!!
>>>
>>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160310/1be3bc83/attachment.htm>