sip.SessionDescriptionHandler | SessionDescriptionHandler.setDescription failed - InvalidAccessError: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: The m= section with mid='0' is invalid. RTCP-MUX is not enabled when it is required. #575
Comments
|
phone.js:2763 Failed to answer call InvalidAccessError: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote offer sdp: The m= section with mid='0' is invalid. RTCP-MUX is not enabled when it is required. |
|
iam using asterisk 13 iam ertcp_mux define in sip.conf but same issue. |
|
Can you send the sip trace of the inbound INVITE. This error is saying that Asterisk is not setting rtcp-mux enabled, but it's required. On the Browser side, you could also try set Line 1994 in 3390278 |
|
When iam do the its answer and hangup.
…On Thu, 5 Dec 2024 at 1:13 AM, Conrad de Wet ***@***.***> wrote:
Can you send the sip trace of the inbound INVITE.
This error is saying that Asterisk is not setting rtcp-mux enabled, but
it's required. On the Browser side, you could also try set rtcpMuxPolicy
to "negotiate" - this would have to be in the source code, as there isn't a
flag for this.
https://github.com/InnovateAsterisk/Browser-Phone/blob/33902782876259957b18f9ca71f811ae0f29b6b3/Phone/phone.js#L1994
—
Reply to this email directly, view it on GitHub
<#575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AY7W2XSRWJBDQKJCHPUYA3D2D5LMXAVCNFSM6AAAAABTA2TF2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGQYDSOJWGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
|
|
geeting the error. |
|
|
|
<--- SIP read from WS:156.67.25.89:61344 ---> v=0 <--- Reliably Transmitting (NAT) to 156.67.25.89:61344 ---> <------------> <--- SIP read from WS:156.67.25.89:61344 ---> <-------------> <--- SIP read from WS:156.67.25.89:61344 ---> v=0 <--- Transmitting (NAT) to 156.67.25.89:61344 ---> <------------> v=0 <--- SIP read from WS:156.67.25.89:61489 ---> <-------------> <--- SIP read from WS:156.67.25.89:61489 ---> <-------------> <--- Transmitting (NAT) to 156.67.25.89:61344 ---> <------------> <--- SIP read from WS:156.67.25.89:61489 ---> <-------------> <--- Transmitting (NAT) to 156.67.25.89:61344 ---> <------------> <--- Reliably Transmitting (NAT) to 156.67.25.89:61344 ---> <------------> <--- SIP read from WS:156.67.25.89:61344 ---> <-------------> [Dec 5 02:18:04] ERROR[5777]: chan_sip.c:4269 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data [Dec 5 02:18:04] ERROR[5777]: chan_sip.c:4269 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data |
|
Here (from above) the invite does not contain a=rtcp-mux |
|
How to fix this any idea.
…On Thu, 5 Dec 2024 at 2:39 AM, Conrad de Wet ***@***.***> wrote:
Here (from above) the invite does not contain a=rtcp-mux
INVITE ***@***.***;transport=wss SIP/2.0
Via: SIP/2.0/WS myserverip:0;branch=z9hG4bK12180a62;rport
Max-Forwards: 70
From: "saurabh" ***@***.***:0;tag=as68407512
To: ***@***.***;transport=wss
Contact: ***@***.***:0;transport=WS
Call-ID: ***@***.***:0
CSeq: 102 INVITE
User-Agent: Asterisk
Date: Wed, 04 Dec 2024 20:47:57 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 1012
v=0
o=root 1220080796 1220080796 IN IP4 myserverip
s=Asterisk PBX certified/13.13-cert9
c=IN IP4 myserverip
t=0 0
m=audio 19620 RTP/SAVPF 107 0 101
a=rtpmap:107 opus/48000/2
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=maxptime:60
a=ice-ufrag:08a67c8b6098f43477a82b0a59d69b1e
a=ice-pwd:2086d394302f944123226a5b78902125
a=candidate:Hac3f40c 1 UDP 2130706431 10.195.244.12 19620 typ host
a=candidate:Hac1c82b9 1 UDP 2130706431 172.28.130.185 19620 typ host
a=candidate:S673825ea 1 UDP 1694498815 myserverip 19620 typ srflx raddr 10.195.244.12 rport 19620
a=candidate:Hac3f40c 2 UDP 2130706430 10.195.244.12 19621 typ host
a=candidate:Hac1c82b9 2 UDP 2130706430 172.28.130.185 19621 typ host
a=candidate:S673825ea 2 UDP 1694498814 myserverip 19621 typ srflx raddr 10.195.244.12 rport 19621
a=connection:new
a=setup:actpass
a=fingerprint:SHA-256 94:54:E3:26:17:20:14:6B:94:71:83:0B:21:6C:24:B3:45:E4:91:EF:24:E7:2F:B6:FA:4D:EA:DA:1B:D5:BC:9A
a=sendrecv
``
The asterisk server is not applying the rtcp-mux config
—
Reply to this email directly, view it on GitHub
<#575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AY7W2XQ4M4UHEWKQXIMORQT2D5VPZAVCNFSM6AAAAABTA2TF2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGU3DMMBVGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
0
o=- 7201341312360866036 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE 0
a=extmap-allow-mixed
a=msid-semantic: WMS b24b3874-6650-45ae-8a81-83f4461c977f
m=audio 62192 UDP/TLS/RTP/SAVPF 111 63 9 0 8 13 110 126
c=IN IP4 45.118.166.200
a=rtcp:9 IN IP4 0.0.0.0
a=candidate:3004991840 1 udp 212226022310.8.0.4 62190 typ host generation 0
network-id 3 network-cost 50
a=candidate:4086786002 1 udp 2122194687192.168.56.1 62191 typ host
generation 0 network-id 1
a=candidate:4179499770 1 udp 2122129151192.168.1.6 62192 typ host
generation 0 network-id 2 network-cost 10
a=candidate:3697792272 1 udp 168592153545.118.166.200 62192 typ srflx raddr
192.168.1.6 rport 62192 generation 0 network-id 2 network-cost 10
a=candidate:3453185016 1 tcp 1518280447 10.8.0.4 9 typ host tcptype active
generation 0 network-id 3 network-cost 50
a=candidate:2371388746 1 tcp 1518214911192.168.56.1 9 typ host tcptype
active generation 0 network-id 1
a=candidate:2278684770 1 tcp 1518149375192.168.1.6 9 typ host tcptype
active generation 0 network-id 2 network-cost 10
a=candidate:2272190244 1 udp 1686052607156.67.25.89 62190 typ srflx raddr
10.8.0.4 rport 62190 generation 0 network-id 3 network-cost 50
a=ice-ufrag:O3WQ
a=ice-pwd:UeOZrOAqZYBim6pkUc5afzQ4
a=ice-options:trickle
a=fingerprint:sha-256
41:88:1F:1D:B0:02:8C:18:82:78:D7:52:32:E1:C8:68:C3:DD:16:B0:0C:F5:2A:14:C6:84:4F:1E:CA:98:94:CC
a=setup:actpass
a=mid:0
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:3
http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
a=sendrecv
a=msid:b24b3874-6650-45ae-8a81-83f4461c977f
e8b98860-069d-4337-b07b-60769ed11d42
a=rtcp-mux
a=rtcp-rsize
a=rtpmap:111 opus/48000/2
a=rtcp-fb:111 transport-cc
a=fmtp:111 minptime=10;useinbandfec=1
a=rtpmap:63 red/48000/2
a=fmtp:63 111/111
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:13 CN/8000
a=rtpmap:110 telephone-event/48000
a=rtpmap:126 telephone-event/8000
a=ssrc:2920066302 cname:TrMGT/5JDzsVb1FJ
a=ssrc:2920066302 msid:b24b3874-6650-45ae-8a81-83f4461c977f
e8b98860-069d-4337-b07b-60769ed11d42
a=rtcp-mux
Its pass the above please chdck previous full log
On Thu, 5 Dec 2024 at 2:40 AM, Saurabh singh Bhakuni ***@***.***>
wrote:
… How to fix this any idea.
On Thu, 5 Dec 2024 at 2:39 AM, Conrad de Wet ***@***.***>
wrote:
> Here (from above) the invite does not contain a=rtcp-mux
>
> INVITE ***@***.***;transport=wss SIP/2.0
> Via: SIP/2.0/WS myserverip:0;branch=z9hG4bK12180a62;rport
> Max-Forwards: 70
> From: "saurabh" ***@***.***:0;tag=as68407512
> To: ***@***.***;transport=wss
> Contact: ***@***.***:0;transport=WS
> Call-ID: ***@***.***:0
> CSeq: 102 INVITE
> User-Agent: Asterisk
> Date: Wed, 04 Dec 2024 20:47:57 GMT
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
> Supported: replaces, timer
> Content-Type: application/sdp
> Content-Length: 1012
>
> v=0
> o=root 1220080796 1220080796 IN IP4 myserverip
> s=Asterisk PBX certified/13.13-cert9
> c=IN IP4 myserverip
> t=0 0
> m=audio 19620 RTP/SAVPF 107 0 101
> a=rtpmap:107 opus/48000/2
> a=rtpmap:0 PCMU/8000
> a=rtpmap:101 telephone-event/8000
> a=fmtp:101 0-16
> a=maxptime:60
> a=ice-ufrag:08a67c8b6098f43477a82b0a59d69b1e
> a=ice-pwd:2086d394302f944123226a5b78902125
> a=candidate:Hac3f40c 1 UDP 2130706431 10.195.244.12 19620 typ host
> a=candidate:Hac1c82b9 1 UDP 2130706431 172.28.130.185 19620 typ host
> a=candidate:S673825ea 1 UDP 1694498815 myserverip 19620 typ srflx raddr 10.195.244.12 rport 19620
> a=candidate:Hac3f40c 2 UDP 2130706430 10.195.244.12 19621 typ host
> a=candidate:Hac1c82b9 2 UDP 2130706430 172.28.130.185 19621 typ host
> a=candidate:S673825ea 2 UDP 1694498814 myserverip 19621 typ srflx raddr 10.195.244.12 rport 19621
> a=connection:new
> a=setup:actpass
> a=fingerprint:SHA-256 94:54:E3:26:17:20:14:6B:94:71:83:0B:21:6C:24:B3:45:E4:91:EF:24:E7:2F:B6:FA:4D:EA:DA:1B:D5:BC:9A
> a=sendrecv
> ``
>
> The asterisk server is not applying the rtcp-mux config
>
> —
> Reply to this email directly, view it on GitHub
> <#575 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AY7W2XQ4M4UHEWKQXIMORQT2D5VPZAVCNFSM6AAAAABTA2TF2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGU3DMMBVGI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
or double check the config, for example: https://github.com/InnovateAsterisk/Browser-Phone/blob/master/config/sip.conf |
Yes, this was the invite session from the browser to the server. |
|
Can you share the code where i did actually the line is commented.
…On Thu, 5 Dec 2024 at 2:47 AM, Conrad de Wet ***@***.***> wrote:
you could also try set rtcpMuxPolicy to "negotiate" - this would have to
be in the source code, as there isn't a flag for this.
or double check the config, for example:
https://github.com/InnovateAsterisk/Browser-Phone/blob/master/config/sip.conf
[webrtc](!)
transport=wss
allow=opus,ulaw,vp9,vp8,h264
encryption=yes
avpf=yes
force_avp=yes
icesupport=yes
rtcp_mux=yes
dtlsenable=yes
dtlsverify=fingerprint
dtlscertfile=/home/pi/certs/raspberrypi.pem
dtlscafile=/home/pi/ca/InnovateAsterisk-Root-CA.crt
dtlssetup=actpass
—
Reply to this email directly, view it on GitHub
<#575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AY7W2XSAV3FTVJ3EUK7TCTD2D5WPZAVCNFSM6AAAAABTA2TF2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGU3TSNZXGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Line no 194 is commented
On Thu, 5 Dec 2024 at 2:49 AM, Saurabh singh Bhakuni ***@***.***>
wrote:
… Can you share the code where i did actually the line is commented.
On Thu, 5 Dec 2024 at 2:47 AM, Conrad de Wet ***@***.***>
wrote:
> you could also try set rtcpMuxPolicy to "negotiate" - this would have to
> be in the source code, as there isn't a flag for this.
>
> or double check the config, for example:
>
>
> https://github.com/InnovateAsterisk/Browser-Phone/blob/master/config/sip.conf
>
> [webrtc](!)
> transport=wss
> allow=opus,ulaw,vp9,vp8,h264
> encryption=yes
> avpf=yes
> force_avp=yes
> icesupport=yes
> rtcp_mux=yes
> dtlsenable=yes
> dtlsverify=fingerprint
> dtlscertfile=/home/pi/certs/raspberrypi.pem
> dtlscafile=/home/pi/ca/InnovateAsterisk-Root-CA.crt
> dtlssetup=actpass
>
> —
> Reply to this email directly, view it on GitHub
> <#575 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AY7W2XSAV3FTVJ3EUK7TCTD2D5WPZAVCNFSM6AAAAABTA2TF2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGU3TSNZXGQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Line no 1994 is commented
On Thu, 5 Dec 2024 at 2:52 AM, Saurabh singh Bhakuni ***@***.***>
wrote:
… Line no 194 is commented
On Thu, 5 Dec 2024 at 2:49 AM, Saurabh singh Bhakuni ***@***.***>
wrote:
> Can you share the code where i did actually the line is commented.
>
> On Thu, 5 Dec 2024 at 2:47 AM, Conrad de Wet ***@***.***>
> wrote:
>
>> you could also try set rtcpMuxPolicy to "negotiate" - this would have to
>> be in the source code, as there isn't a flag for this.
>>
>> or double check the config, for example:
>>
>>
>> https://github.com/InnovateAsterisk/Browser-Phone/blob/master/config/sip.conf
>>
>> [webrtc](!)
>> transport=wss
>> allow=opus,ulaw,vp9,vp8,h264
>> encryption=yes
>> avpf=yes
>> force_avp=yes
>> icesupport=yes
>> rtcp_mux=yes
>> dtlsenable=yes
>> dtlsverify=fingerprint
>> dtlscertfile=/home/pi/certs/raspberrypi.pem
>> dtlscafile=/home/pi/ca/InnovateAsterisk-Root-CA.crt
>> dtlssetup=actpass
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#575 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/AY7W2XSAV3FTVJ3EUK7TCTD2D5WPZAVCNFSM6AAAAABTA2TF2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGU3TSNZXGQ>
>> .
>> You are receiving this because you authored the thread.Message ID:
>> ***@***.***>
>>
>
|
|
Before you jump into the code, check that Asterisk is setup correctly first. To be clear the issue as with the B-side endpoint (200)... although 200 DID seems mapped to "User5" |
sip.SessionDescriptionHandler | SessionDescriptionHandler.setDescription failed - InvalidAccessError: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: The m= section with mid='0' is invalid. RTCP-MUX is not enabled when it is required.
The text was updated successfully, but these errors were encountered: