12 Jul
2013
12 Jul
'13
1:08 p.m.
i tried what happens when i make rtpproxy_answer("co2sp") call on 200 ok
from jssip ws client. mediaproxy-ng replied with failed to rewrite sdp
error. i don't know if there is something wrong in jssip sdp or if
there is a bug in mediaproxy-ng.
-- juha
Jul 12 12:00:35 siika /usr/sbin/sip-proxy[24258]: INFO: ===== making
rtpproxy_answer(co2sp)
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Got valid command from 127.0.0.1:37753: answer
- { "sdp": "v=0#015#012o=- 7784118477498446372 2 IN IP4
127.0.0.1#015#012s=-#015#012t=0 0#015#012a=msid-semantic: WMS
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012m=audio 52768 RTP/SAVPF 0 8 101#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:35156 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 52768 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 54654 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 35156 typ host generation 0#015#012a=candidate:3477369669 2 udp
2113937150 87.95.11.3 41538 typ host generation 0#015#012a=candidate:1403124357 1 tcp
1509957375 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 1 tcp
1509957375 87.95.11.3 0 typ host generation 0#015#012a=candidate:1403124357 2 tcp
1509957374 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 2 tcp
1509957374 87.95.11.3 0 typ host generation
0#015#012a=ice-ufrag:84M0GoeLawbPRCtI#015#012a=ice-pwd:0d0+xU+T7a4GeeFSWffXH71m#015#012a=sendrecv#015#012a=mid:audio#015#012a=crypto:0
AES_CM_128_HMAC_SHA1_80 inline:QfUiviqGYSIBnQdS/ZRuYKdBdTF11sjOc107mKS8#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:101
telephone-event/8000#015#012a=ssrc:932705198
cname:/crPhms9UoL3P5CY#015#012a=ssrc:932705198 msid:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012a=ssrc:932705198
mslabel:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012a=ssrc:932705198
label:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012m=video 35740 RTP/SAVPF 96#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:40599 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 35740 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 55064 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 40599 typ host generation 0#015#012a=candidate:3477369669 2 udp
2113937150 87.
Jul 12 12:00:35 siika mediaproxy-ng[15173]: [7cd288942112dd88 - z9hG4bK779cdf1cf94f5904]
Got LOOKUP, but no usable callstreams found
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Error rewriting SDP
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Protocol error in packet from 127.0.0.1:37753:
Error rewriting SDP [d3:sdp2555:v=0#015#012o=- 7784118477498446372 2 IN IP4
127.0.0.1#015#012s=-#015#012t=0 0#015#012a=msid-semantic: WMS
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012m=audio 52768 RTP/SAVPF 0 8 101#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:35156 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 52768 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 54654 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 35156 typ host generation 0#015#012a=candidate:3477369669 2 udp
2113937150 87.95.11.3 41538 typ host generation 0#015#012a=candidate:1403124357 1 tcp
1509957375 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 1 tcp
1509957375 87.95.11.3 0 typ host generation 0#015#012a=candidate:1403124357 2 tcp
1509957374 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 2 tcp
1509957374 87.95.11.3 0 typ host generation
0#015#012a=ice-ufrag:84M0GoeLawbPRCtI#015#012a=ice-pwd:0d0+xU+T7a4GeeFSWffXH71m#015#012a=sendrecv#015#012a=mid:audio#015#012a=crypto:0
AES_CM_128_HMAC_SHA1_80 inline:QfUiviqGYSIBnQdS/ZRuYKdBdTF11sjOc107mKS8#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:101
telephone-event/8000#015#012a=ssrc:932705198
cname:/crPhms9UoL3P5CY#015#012a=ssrc:932705198 msid:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012a=ssrc:932705198
mslabel:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012a=ssrc:932705198
label:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012m=video 35740 RTP/SAVPF 96#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:40599 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 35740 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 55064 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 40599 typ host generation 0#015#012a=candidate:3477369669
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Returning to SIP proxy:
d6:result5:error12:error-reason19:Error rewriting SDPe
Jul 12 12:00:35 siika /usr/sbin/sip-proxy[24258]: ERROR: rtpproxy-ng [rtpproxy.c:1343]:
rtpp_function_call(): proxy replied with error: Error rewriting SDP
12 Jul
12 Jul
4:19 p.m.
New subject: mediaproxy-ng failed to rewrite sdp from jssip ws client
On 07/12/13 05:08, Juha Heinanen wrote:
i tried what happens when i make
rtpproxy_answer("co2sp") call on 200 ok
from jssip ws client. mediaproxy-ng replied with failed to rewrite sdp
error. i don't know if there is something wrong in jssip sdp or if
there is a bug in mediaproxy-ng.
It would help to see the SDP from the offer as well, most like the
problem can be found there. Currently there's a known issue when the
offer SDP contains multiple streams multiplexed on the same RTP port,
i.e. audio and video (and also RTCP) on the same port like Chrome does
it. This isn't trivial to fix in the current code base, but I have a
more severe rewrite planned that will address this issue. Until then,
the only workaround is to disable video.
cheers
5:09 p.m.
New subject: mediaproxy-ng failed to rewrite sdp from jssip ws client
Richard Fuchs writes:
It would help to see the SDP from the offer as well,
most like the
problem can be found there. Currently there's a known issue when the
offer SDP contains multiple streams multiplexed on the same RTP port,
i.e. audio and video (and also RTCP) on the same port like Chrome does
it. This isn't trivial to fix in the current code base, but I have a
more severe rewrite planned that will address this issue. Until then,
the only workaround is to disable video.
below is both offer and answer.
-- juha
Jul 12 12:00:28 siika mediaproxy-ng[15173]: Got valid command from 127.0.0.1:57610: offer
- { "sdp": "v=0#015#012o=- 2436967815 958369258 IN IP4
87.95.11.3#015#012s=-#015#012c=IN IP4 87.95.11.3#015#012t=0 0#015#012a=tool:baresip
0.4.4#015#012m=audio 10696 RTP/AVP 96 97 8 0 101#015#012b=AS:125#015#012a=rtpmap:96
speex/16000#015#012a=fmtp:96 mode="7";vbr=off;cng=on#015#012a=rtpmap:97
speex/8000#015#012a=fmtp:97 mode="7";vbr=off;cng=on#015#012a=rtpmap:8
PCMA/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101
telephone-event/8000#015#012a=fmtp:101
0-15#015#012a=sendrecv#015#012a=label:1#015#012a=ptime:20#015#012m=video 10230 RTP/AVP
96#015#012b=AS:875#015#012a=rtpmap:96 VP8/90000#015#012a=fmtp:96
max-fs=3600#015#012a=sendrecv#015#012a=label:2#015#012a=framerate:25#015#012a=rtcp-fb:*
nack pli#015#012a=content:main#015#012", "replace": [
"session-connection", "origin" ], "transport-protocol":
"RTP/SAVPF", "call-id": "7cd288942112dd88",
"via-branch": "z9hG4bK779cdf1cf94f5904", "received-from": [
"IP4", "192.98.102.10" ], "from-tag":
"fd239c4fb4109af0", "command": "offer" }
Jul 12 12:00:28 siika mediaproxy-ng[15173]: [7cd288942112dd88] Creating new call
Jul 12 12:00:28 siika mediaproxy-ng[15173]: [7cd288942112dd88 - z9hG4bK779cdf1cf94f5904]
Opened ports 50292..50293 for RTP
Jul 12 12:00:28 siika mediaproxy-ng[15173]: [7cd288942112dd88 - z9hG4bK779cdf1cf94f5904]
Opened ports 50294..50295 for RTP
Jul 12 12:00:28 siika mediaproxy-ng[15173]: [7cd288942112dd88 - z9hG4bK779cdf1cf94f5904]
Opened ports 50296..50297 for RTP
Jul 12 12:00:28 siika mediaproxy-ng[15173]: [7cd288942112dd88 - z9hG4bK779cdf1cf94f5904]
Opened ports 50298..50299 for RTP
Jul 12 12:00:28 siika mediaproxy-ng[15173]: Returning to SIP proxy:
d3:sdp1206:v=0#015#012o=- 2436967815 958369258 IN IP4 192.98.102.10#015#012s=-#015#012c=IN
IP4 192.98.102.10#015#012t=0 0#015#012a=tool:baresip
0.4.4#015#012a=ice-lite#015#012m=audio 50292 RTP/SAVPF 96 97 8 0
101#015#012b=AS:125#015#012a=rtpmap:96 speex/16000#015#012a=fmtp:96
mode="7";vbr=off;cng=on#015#012a=rtpmap:97 speex/8000#015#012a=fmtp:97
mode="7";vbr=off;cng=on#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101
0-15#015#012a=sendrecv#015#012a=label:1#015#012a=ptime:20#015#012a=rtcp:50293#015#012a=crypto:0
AES_CM_128_HMAC_SHA1_80
inline:pB9CbIZPIZRxOIXbZUiHJ4WBYnnA7s3L+/Qjl5EQ#015#012a=ice-ufrag:uvlKhss8#015#012a=ice-pwd:adr3Q012NPZxkjTZzQZ4V8EqEXaT#015#012a=candidate:MKCGbUwuWxN9u6o2
1 UDP 2130706432 192.98.102.10 50292 typ host#015#012a=candidate:MKCGbUwuWxN9u6o2 2 UDP
2130706431 192.98.102.10 50293 typ host#015#012m=video 50296 RTP/SAVPF
96#015#012b=AS:875#015#012a=rtpmap:96 VP8/90000#015#012a=fmtp:96
max-fs=3600#015#012a=sendrecv#015#012a=label:2#015#012a=framerate:25#015#012a=rtcp-fb:*
nack pli#015#012a=content:main#015#012a=rtcp:50297#015#012a=crypto:0
AES_CM_128_HMAC_SHA1_80
inline:oYAC65r9uo5d0grkbwfNhcWkaE53P/rgqLZgRqE5#015#012a=ice-ufrag:fvtf2fGB#015#012a=ice-pwd:S5bwfy8Wd3vRxUu3eedXAiQQLj3O#015#012a=candidate:MKCGbUwuWxN9u6o2
1 UDP 2130706432 192.98.102.10 50296 typ host#015#012a=candidate:MKCGbUwuWxN9u6o2 2 UDP
2130706431 192.98.102.10 50297 typ host#015#0126:result2:oke
Jul 12 12:00:28 siika /usr/sbin/sip-proxy[24264]: INFO: ===== set t_on_branch_failure
Jul 12 12:00:28 siika /usr/sbin/sip-proxy[24264]: INFO: Routing INVITE
<sip:9vule5f7@fqc0p8bqqo9n.invalid;transport=ws> to contact via
<sip:192.98.102.10:58526;transport=WS>
Jul 12 12:00:33 siika mediaproxy-ng[15173]: Successful STUN binding request on port 50292
from 87.95.11.3:54654
Jul 12 12:00:33 siika mediaproxy-ng[15173]: Successful STUN binding request on port 50293
from 87.95.11.3:41538
Jul 12 12:00:33 siika mediaproxy-ng[15173]: Successful STUN binding request on port 50296
from 87.95.11.3:55064
Jul 12 12:00:33 siika mediaproxy-ng[15173]: Successful STUN binding request on port 50292
from 87.95.11.3:54654
Jul 12 12:00:33 siika mediaproxy-ng[15173]: Successful STUN binding request on port 50293
from 87.95.11.3:41538
...
Jul 12 12:00:35 siika /usr/sbin/sip-proxy[24258]: INFO: ===== making
rtpproxy_answer(co2sp)
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Got valid command from 127.0.0.1:37753: answer
- { "sdp": "v=0#015#012o=- 7784118477498446372 2 IN IP4
127.0.0.1#015#012s=-#015#012t=0 0#015#012a=msid-semantic: WMS
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012m=audio 52768 RTP/SAVPF 0 8 101#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:35156 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 52768 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 54654 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 35156 typ host generation 0#015#012a=candidate:3477369669 2 udp
2113937150 87.95.11.3 41538 typ host generation 0#015#012a=candidate:1403124357 1 tcp
1509957375 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 1 tcp
1509957375 87.95.11.3 0 typ host generation 0#015#012a=candidate:1403124357 2 tcp
1509957374 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 2 tcp
1509957374 87.95.11.3 0 typ host generation
0#015#012a=ice-ufrag:84M0GoeLawbPRCtI#015#012a=ice-pwd:0d0+xU+T7a4GeeFSWffXH71m#015#012a=sendrecv#015#012a=mid:audio#015#012a=crypto:0
AES_CM_128_HMAC_SHA1_80 inline:QfUiviqGYSIBnQdS/ZRuYKdBdTF11sjOc107mKS8#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:101
telephone-event/8000#015#012a=ssrc:932705198
cname:/crPhms9UoL3P5CY#015#012a=ssrc:932705198 msid:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012a=ssrc:932705198
mslabel:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012a=ssrc:932705198
label:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012m=video 35740 RTP/SAVPF 96#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:40599 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 35740 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 55064 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 40599 typ host generation 0#015#012a=candidate:3477369669 2 udp
2113937150 87.
Jul 12 12:00:35 siika mediaproxy-ng[15173]: [7cd288942112dd88 - z9hG4bK779cdf1cf94f5904]
Got LOOKUP, but no usable callstreams found
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Error rewriting SDP
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Protocol error in packet from 127.0.0.1:37753:
Error rewriting SDP [d3:sdp2555:v=0#015#012o=- 7784118477498446372 2 IN IP4
127.0.0.1#015#012s=-#015#012t=0 0#015#012a=msid-semantic: WMS
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012m=audio 52768 RTP/SAVPF 0 8 101#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:35156 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 52768 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 54654 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 35156 typ host generation 0#015#012a=candidate:3477369669 2 udp
2113937150 87.95.11.3 41538 typ host generation 0#015#012a=candidate:1403124357 1 tcp
1509957375 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 1 tcp
1509957375 87.95.11.3 0 typ host generation 0#015#012a=candidate:1403124357 2 tcp
1509957374 192.98.102.10 0 typ host generation 0#015#012a=candidate:2177339317 2 tcp
1509957374 87.95.11.3 0 typ host generation
0#015#012a=ice-ufrag:84M0GoeLawbPRCtI#015#012a=ice-pwd:0d0+xU+T7a4GeeFSWffXH71m#015#012a=sendrecv#015#012a=mid:audio#015#012a=crypto:0
AES_CM_128_HMAC_SHA1_80 inline:QfUiviqGYSIBnQdS/ZRuYKdBdTF11sjOc107mKS8#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:101
telephone-event/8000#015#012a=ssrc:932705198
cname:/crPhms9UoL3P5CY#015#012a=ssrc:932705198 msid:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b
Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012a=ssrc:932705198
mslabel:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1b#015#012a=ssrc:932705198
label:Eu5Sypk7W9nqcEJTwC2L8NseDJ5errAYzo1ba0#015#012m=video 35740 RTP/SAVPF 96#015#012c=IN
IP4 192.98.102.10#015#012a=rtcp:40599 IN IP4 192.98.102.10#015#012a=candidate:488769141 1
udp 2113937151 192.98.102.10 35740 typ host generation 0#015#012a=candidate:3477369669 1
udp 2113937151 87.95.11.3 55064 typ host generation 0#015#012a=candidate:488769141 2 udp
2113937150 192.98.102.10 40599 typ host generation 0#015#012a=candidate:3477369669
Jul 12 12:00:35 siika mediaproxy-ng[15173]: Returning to SIP proxy:
d6:result5:error12:error-reason19:Error rewriting SDPe
Jul 12 12:00:35 siika /usr/sbin/sip-proxy[24258]: ERROR: rtpproxy-ng [rtpproxy.c:1343]:
rtpp_function_call(): proxy replied with error: Error rewriting SDP
5:19 p.m.
New subject: mediaproxy-ng failed to rewrite sdp from jssip ws client
On 07/12/13 09:09, Juha Heinanen wrote:
Richard Fuchs writes:
I think the problem is that the offer doesn't contain a=rtcp (i.e. RTCP
is on standard RTP+1 port), but the answer did and had it running on
different ports (not RTP+1). Just like the multiplexing case, this isn't
properly handled by mediaproxy-ng yet, but will be once I get the
rewrite of the stream/port handling in.
cheers
It would help to see the SDP from the offer as
well, most like the
problem can be found there. Currently there's a known issue when the
offer SDP contains multiple streams multiplexed on the same RTP port,
i.e. audio and video (and also RTCP) on the same port like Chrome does
it. This isn't trivial to fix in the current code base, but I have a
more severe rewrite planned that will address this issue. Until then,
the only workaround is to disable video.
below is both offer and answer.
4096
days inactive
4096
days old
3 comments
2 participants
participants (2)
-
Juha Heinanen -
Richard Fuchs