【问题标题】:Why is the SIP ACK sent from our PBX not received by Twilio?为什么 Twilio 没有收到从我们的 PBX 发送的 SIP ACK?
【发布时间】:2022-11-11 03:25:31
【问题描述】:

我们通过 Twilio 的呼出电话都在 32 秒后掉线(呼入电话很好)。我们从 Twilio 收到的错误是错误 32022“未收到来自您的 SIP 端点的确认”。我一直在阅读教程和 RFC,但我确实错过了一些东西。

调用是加密的 TLS。 SIP ALG 已在我们的网关路由器中禁用,我们的 Grandstream PBX 已配置为 NAT。

任何帮助表示赞赏!

这是 200 OK 和永远不会到达的 ACK:

<--- Received SIP response (1177 bytes) from TLS:54.172.60.2:5061 ---> 
SIP/2.0 200 OK
CSeq: 2218 INVITE
Call-ID: b9e1de31-ce44-4d34-b63b-4c8636e151bf
From: <sip:+13049487110@XXXX>;tag=814fce4e-a1dc-49c7-a917-59496ad182a7
To: <sip:+15132607811@xxxx.pstn.twilio.com>;tag=84858964_c3356d0b_d52c7a82-314f-4be6-88f4-e73110bdbdd8
Via: SIP/2.0/TLS 74.195.14.236:5061;received=74.195.14.236;rport=52191;branch=z9hG4bKPj42ac7abe-f4b7-40dc-a314-8c6a90584481;alias
Record-Route: <sip:54.172.60.2:5060;r2=on;lr;twnat=sip:74.195.14.236:52191>
Record-Route: <sip:54.172.60.2:5061;transport=tls;r2=on;lr;twnat=sip:74.195.14.236:52191>
Server: Twilio
Contact: <sip:172.25.75.195:5060>
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY
Content-Type: application/sdp
X-Twilio-CallSid: CAb39a1e013e6ad6c03bd5bd2827612646
X-Twilio-TlsPolicy: TLSv1.0+
Content-Length: 362

v=0
o=root 1866335776 1866335776 IN IP4 172.   ...


<--- Transmitting SIP request (1010 bytes) to TLS:54.172.60.2:5061 ---> 
ACK sip:54.172.60.2:5061;transport=TLS SIP/2.0
Via: SIP/2.0/TLS 74.195.14.236:5061;rport;branch=z9hG4bKPj483e2dff-e510-4908-89ee-25ec200a4072;alias
From: <sip:+13049487110@XXXX>;tag=814fce4e-a1dc-49c7-a917-59496ad182a7
To: <sip:+15132607811@xxxx.pstn.twilio.com>;tag=84858964_c3356d0b_d52c7a82-314f-4be6-88f4-e73110bdbdd8
Call-ID: b9e1de31-ce44-4d34-b63b-4c8636e151bf
CSeq: 2218 ACK
Route: <sip:54.172.60.2:5061;transport=tls;lr;r2=on;twnat=sip:74.195.14.236:52191>
Route: <sip:54.172.60.2:5060;lr;r2=on;twnat=sip:74.195.14.236:52191>
...

【问题讨论】:

    标签: twilio sip pjsip pbx


    【解决方案1】:

    ACK 请求的地址不正确:根据 3261 的松散路由,它应该被发送到 Contact URI,但发送到最顶层的路由(从最底层的 Record-Route 构建,ACK 中的路由集似乎是正确的)。更正 ACK 的请求 URI,这应该会有所帮助。

    【讨论】:

    • 谢谢!是的,它需要正确的请求 URI。
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2018-03-27
    • 1970-01-01
    • 1970-01-01
    • 2016-04-10
    相关资源
    最近更新 更多