26 Jul
2013
26 Jul
'13
9:39 a.m.
Hi,
I can't reproduce this, neither the empty IP address nor the segfault.
Can you tell me which version exactly of both mediaproxy-ng and the
rtpproxy-ng module you're using (downloaded from where, which
repository, which branch), as well as the entire log for a particular
call, i.e. everything from the initial offer to the final delete.
cheers
On 07/26/13 04:48, Khue Nguyen Minh wrote:
Hi,
I removed x parameter and re-run. But, I still got same error:
mediaproxy-ng[10607]: Got valid command from 127.0.0.1:54098
<http://127.0.0.1:54098>: answer - { "sdp": "v=0#015#012o=-
3583815381
3583815382 IN IP4 10.10.10.20#015#012s=pjmedia#015#012c=IN IP4
10.10.10.20#015#012t=0 0#015#012m=audio 4021 RTP/AVP 0 101#015#012c=IN
IP4 10.10.10.20#015#012a=rtcp:4012 IN IP4
10.10.10.20#015#012a=sendrecv#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
0-15#015#012a=ice-ufrag:498bc970#015#012a=ice-pwd:5f0321c0#015#012a=candidate:Ha0a0a14
1 UDP 2130706431 10.10.10.20 4021 typ host#015#012a=candidate:Ha0a0a14 2
UDP 2130706430 10.10.10.20 4012 typ host#015#012m=text 0 RTP/AVP 124
123#015#012", "flags": [ "force" ], "replace": [
"origin" ], "call-id":
"e2065031-89db-1460-0b8a-4670998bcb97", "received-from": [
"IP4",
"x.x.x.x" ], "from-tag": "17831887", "to-tag":
"Z-9BdndAjW4RvnSpPKLNt02ksKPJf1Fd", "command": "answer" }
mediaproxy-ng[10607]: [e2065031-89db-1460-0b8a-4670998bcb97 - ] Got
LOOKUP, but no usable callstreams found
mediaproxy-ng[10607]: Error rewriting SDP
mediaproxy-ng[10607]: Protocol error in packet from 127.0.0.1:54098
<http://127.0.0.1:54098>: Error rewriting SDP [d3:sdp457:v=0#015#012o=-
3583815381 3583815382 IN IP4 10.10.10.20#015#012s=pjmedia#015#012c=IN
IP4 10.10.10.20#015#012t=0 0#015#012m=audio 4021 RTP/AVP 0
101#015#012c=IN IP4 10.10.10.20#015#012a=rtcp:4012 IN IP4
10.10.10.20#015#012a=sendrecv#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
0-15#015#012a=ice-ufrag:498bc970#015#012a=ice-pwd:5f0321c0#015#012a=candidate:Ha0a0a14
1 UDP 2130706431 10.10.10.20 4021 typ host#015#012a=candidate:Ha0a0a14 2
UDP 2130706430 10.10.10.20 4012 typ host#015#012m=text 0 RTP/AVP 124
123#015#0125:flagsl5:forcee7:replacel6:origine7:call-id36:e2065031-89db-1460-0b8a-4670998bcb9713:received-froml3:IP414:x.x.x.xe8:from-tag8:178318876:to-tag32:Z-9BdndAjW4RvnSpPKLNt02ksKPJf1Fd7:command6:answere]
mediaproxy-ng[10607]: Returning to SIP proxy:
d6:result5:error12:error-reason19:Error rewriting SDPe
And rtpproxy-ng segment fault when I hangup call.
2013/7/26 Carsten Bock <carsten(a)ng-voice.com <mailto:carsten@ng-voice.com>>
Hi,
the "x"-Parameter in dlg_manage is for bridging IPv4/IPv6. You only
have configured one address, so the x-Parameter does not make any
sense here.
http://kamailio.org/docs/modules/devel/modules/rtpproxy.html#idp2994536
Kind regards from the implementor of the "x"-Parameter,
Carsten
2013/7/26 Khue Nguyen Minh <khuenm(a)vega.com.vn
<mailto:khuenm@vega.com.vn>>:
mailing list
I run mediaproxy-ng with command:
mediaproxy-ng --table=42 --ip=x.x.x.x --listen-ng=127.0.0.1:7723
<http://127.0.0.1:7723> --tos=184
--pidfile=/var/run/mediaproxy-ng.pid
--advertised-ip=x.x.x.x
And this is my config of sipproxy
1. when I receive INVITE message
if (is_request()) {
if (is_direction("downstream"))
rtpproxy_manage("fox");
else
rtpproxy_manage("foxr");
} else {
if (is_direction("downstream"))
rtpproxy_manage("foxr");
else
rtpproxy_manage("fox");
}
2. When I receive 200 OK response
if (is_request()) {
if (is_direction("downstream"))
rtpproxy_manage("foxr");
else
rtpproxy_manage("fox");
} else {
if (is_direction("downstream"))
rtpproxy_manage("fox");
else
rtpproxy_manage("foxr");
}
2013/7/26 Alexey Rybalko <alexey.rybalko(a)gmail.com
<mailto:alexey.rybalko@gmail.com>>
>
> Hi!
>
> Just my two cents. What parameters do you use for mediaproxy?
Smth like
> RUN_MEDIAPROXY=yes
> LISTEN_UDP=127.0.0.1:1111 <http://127.0.0.1:1111>
> LISTEN_NG=127.0.0.1:11123 <http://127.0.0.1:11123>
> ADDRESS=XXX.XXX.XXX.XXX
>
> ?
>
> regards,
> Alexey
>
>
>
> 2013/7/26 Khue Nguyen Minh <khuenm(a)vega.com.vn
<mailto:khuenm@vega.com.vn>>
>>
>> Thanks Richard. Now, rtpproxy-ng can work with mediaproxy-ng.
But, I
have
>> some error when run it. After rtpproxy-ng
send SDP information to
>> mediaproxy-ng, it receive wrong IP. please see follow log:
>>
>> Got valid command from 127.0.0.1:60340
<http://127.0.0.1:60340>:
offer - { "sdp":
>> "v=0#015#012o=doubango 1983 678901
IN IP4
10.0.0.19#015#012s=-#015#012c=IN
>> IP4 10.0.0.19#015#012t=0
0#015#012a=tcap:1
RTP/AVPF#015#012m=audio 18876
>> RTP/AVP 0 8
101#015#012a=ptime:20#015#012a=silenceSupp:off - - -
>> -#015#012a=rtpmap:0 PCMU/8000/1#015#012a=rtpmap:8
>> PCMA/8000/1#015#012a=rtpmap:101
telephone-event/8000/1#015#012a=fmtp:101
>> 0-16#015#012a=pcfg:1
>> t=1#015#012a=sendrecv#015#012a=rtcp-mux#015#012a=ssrc:434299437
>> cname:ldjWoB60jbyQlR6e#015#012a=ssrc:434299437
>>
mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2#015#012a=ssrc:434299437
>> label:Doubango#015#012m=text 2306 RTP/AVP
124
123#015#012a=rtpmap:124
>> t140/1000#015#012a=fmtp:124
cps=30#015#012a=rtpmap:123
>> red/1000#015#012a=fmtp:123 124/124/124/124#015#012a=pcfg:1
>> t=1#015#012a=sendrecv#015#012a=rtcp-mux#015#012", "flags": [
"force",
>> "auto-bridge" ],
"replace": [ "origin" ], "call-id":
>> "066cf8f8-fec9-7441-32f1-211298ff1715", "received-from": [
"IP4", "x.x.x.x"
>> ], "from-tag":
"15056954", "command": "offer" }
>>
>> [066cf8f8-fec9-7441-32f1-211298ff1715] Creating new call
>>
>> Returning to SIP proxy: d3:sdp1022:v=0#015#012o=doubango 1983
678901
IN
>> IP4 0.0.0.0#015#012s=-#015#012c=IN IP4
0.0.0.0#015#012t=0
0#015#012a=tcap:1
>> RTP/AVPF#015#012a=ice-lite#015#012m=audio
40000 RTP/AVP 0 8
>> 101#015#012a=ptime:20#015#012a=silenceSupp:off - - -
-#015#012a=rtpmap:0
>> PCMU/8000/1#015#012a=rtpmap:8
PCMA/8000/1#015#012a=rtpmap:101
>> telephone-event/8000/1#015#012a=fmtp:101 0-16#015#012a=pcfg:1
>> t=1#015#012a=sendrecv#015#012a=ssrc:434299437
>> cname:ldjWoB60jbyQlR6e#015#012a=ssrc:434299437
>>
mslabel:6994f7d1-6ce9-4fbd-acfd-84e5131ca2e2#015#012a=ssrc:434299437
>>
label:Doubango#015#012a=rtcp:40001#015#012a=ice-ufrag:7YFi3AH6#015#012a=ice-pwd:oZwjQ1y9WJbLLI6mjWMSOOSVMvdQ#015#012a=candidate:rfWFb7Vp3QisWSvf
>> 1 UDP 2130706432 0.0.0.0 40000 typ
host#015#012a=candidate:rfWFb7Vp3QisWSvf
>> 2 UDP 2130706431 0.0.0.0 40001 typ
host#015#012m=text 40004
RTP/AVP 124
>>> 123#015#012a=rtpmap:124 t140/1000#015#012a=fmtp:124
>>> cps=30#015#012a=rtpmap:123 red/1000#015#012a=fmtp:123
>>> 124/124/124/124#015#012a=pcfg:1
>>
t=1#015#012a=sendrecv#015#012a=rtcp:40005#015#012a=ice-ufrag:4SUsQrLE#015#012a=ice-pwd:qhLmZW7KFb6W7QOVFEOraZfcQaCG#015#012a=candidate:rfWFb7Vp3QisWSvf
>> 1 UDP 2130706432 0.0.0.0 40004 typ
host#015#012a=candidate:rfWFb7Vp3QisWSvf
>>> 2 UDP 2130706431 0.0.0.0 40005 typ host#015#0126:result2:oke
>>
>>> And in SIP
message I capture from network, IP address in SDP
body become
>> 0.0.0.0. The call setup success but I
don't hear anything. When
I hangup
>> this call, module rtpproxy-ng segment
fault, and this is call
stack:
>>
>>> #0
bencode_string (bencbuf=0x7fffb6206760, msg=0x7fd617cb13a0,
>> op=OP_DELETE, flags_str=0x7fd617cd5f90
"fox", body_out=0x0) at
bencode.h:349
>> #1 bencode_list_add_string
(bencbuf=0x7fffb6206760,
msg=0x7fd617cb13a0,
>> op=OP_DELETE, flags_str=0x7fd617cd5f90
"fox", body_out=0x0) at
bencode.h:407
>>> #2 rtpp_function_call (bencbuf=0x7fffb6206760, msg=0x7fd617cb13a0,
>> op=OP_DELETE, flags_str=0x7fd617cd5f90
"fox", body_out=0x0) at
>>> rtpproxy.c:1191
>>
>>> Please help me
fix it.
>>
>>> Thanks
>>> Khue.
>>
>>
>>> 2013/7/24 Richard Fuchs
<rfuchs(a)sipwise.com
<mailto:rfuchs@sipwise.com>>
>>>
>>> On 07/24/13 05:45, Khue Nguyen Minh wrote:
>>> > Hi all,
>>> >
>>> > I am using rtpproxy-ng to control mediaproxy-ng. I was
install and
>>> > config follow this guide:
>>> > https://github.com/sipwise/mediaproxy-ng
>>> > when I run kamailio with rtpproxy-ng module and
mediaproxy-ng
I got
>>> > error:
>>> > mediaproxy-ng[25216]: Failed to properly parse UDP command line
>>> > '30514_2
>>> > d7:command4:pinge' from 127.0.0.1:54621
<http://127.0.0.1:54621> <http://127.0.0.1:54621>,
>>> > using
>>> > fallback RE
>>> > ERROR: rtpproxy-ng [rtpproxy.c:1381]: rtpp_test(): proxy
responded
>>> > with
>>> > invalid response
>>>
>>> As a quick guess, I'd say that you used the -u option instead
of the -n
>>> option (or --listen-udp instead of
--listen-ng). Substitute
one for the
>>> other and it should work.
>>>
>>> cheers
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing
list
>>> sr-users(a)lists.sip-router.org
<mailto:sr-users@lists.sip-router.org>
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>
>>
>>>
_______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
>> sr-users(a)lists.sip-router.org
<mailto:sr-users@lists.sip-router.org>
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users sr-users(a)lists.sip-router.org
<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com <mailto:carsten@ng-voice.com>
Office +49 40 34927219
Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users