android - 为什么 asterisk 不能正常使用 android sip 客户端？-6ren

android - 为什么 asterisk 不能正常使用 android sip 客户端？

转载作者：太空狗更新时间：2023-10-29 12:49:13

Asterisk = 1.8.11.0

安卓= 2.3/4.0.3

Android Sip client=原生Android sip client/sipdemo

当我使用 zoiper/xlite 从我的电脑调用 android(原生 android sip 客户端)时，我现在可以听到双方的音频，但是当我从 android 调用 pc(zoiper/xlite)时，我在 android 上听不到任何声音。另一方面，我已经在 elastix(也使用 asterisk 1.8.11.0)上测试了这个场景，音频没有问题。电脑(zoiper)ip 192.168.15.27安卓ip 192.168.15.71 Asterisk 服务器ip 192.168.15.118

从 android 调用 zoiper 时进行 Sip 调试。

<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK5996b0d9;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as05233e7d
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 14151c2d29c039983aa449b56ce419e0@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '14151c2d29c039983aa449b56ce419e0@192.168.15.118:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.15.71:45616 --->
OPTIONS sip:192.168.15.118 SIP/2.0
Call-ID: 5f7229b44e43a9e0eeaccabafd9a1e4f@192.168.15.71
CSeq: 7757 OPTIONS
From: "211" <sip:211@192.168.15.118>;tag=1758376458
To: "211" <sip:211@192.168.15.118>
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK6c57f04e92e9e34153367ca0e6e29675353134;rport
Max-Forwards: 70
User-Agent: SIPAUA/0.1.001
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
Looking for s in default (domain 192.168.15.118)

<--- Transmitting (NAT) to 192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK6c57f04e92e9e34153367ca0e6e29675353134;received=192.168.15.71;rport=45616
From: "211" <sip:211@192.168.15.118>;tag=1758376458
To: "211" <sip:211@192.168.15.118>;tag=as6a8e1b47
Call-ID: 5f7229b44e43a9e0eeaccabafd9a1e4f@192.168.15.71
CSeq: 7757 OPTIONS
Server: Asterisk PBX 1.8.11.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.15.118:5060>
Accept: application/sdp
Content-Length: 0


<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK1ecea84c;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as167765df
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 5f4d210800aa07065fd35fba215e9783@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '5f4d210800aa07065fd35fba215e9783@192.168.15.118:5060' Method: OPTIONS
Really destroying SIP dialog '5e5f98ad4818911a86d4b438d054e39f@192.168.15.71' Method: OPTIONS
Reliably Transmitting (NAT) to 192.168.15.71:45616:
OPTIONS sip:211@192.168.15.71:45616;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK15f7593b;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as53340ecf
To: <sip:211@192.168.15.71:45616;transport=udp>
Contact: <sip:asterisk@192.168.15.118:5060>
Call-ID: 3c9da88024211f4b2ad1f3af2b2acd73@192.168.15.118:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.11.0
Date: Sat, 12 Jan 2013 19:44:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---

<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK15f7593b;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as53340ecf
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 3c9da88024211f4b2ad1f3af2b2acd73@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '3c9da88024211f4b2ad1f3af2b2acd73@192.168.15.118:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.15.71:45616 --->
BYE sip:215@192.168.15.118:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bKad00f5add2a1f2e940a91e9a3f827b26353134
CSeq: 5511 BYE
From: "211" <sip:211@192.168.15.118>;tag=2465683119
To: <sip:215@192.168.15.118>;tag=as573c52b3
Call-ID: d188757cd6c044783fd413d11f8a982f@192.168.15.71
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY,INFO,PUBLISH
Supported: replaces,timer
Max-Forwards: 70
Content-Length: 0

<------------->
--- (10 headers 0 lines) ---
Sending to 192.168.15.71:45616 (NAT)
Scheduling destruction of SIP dialog 'd188757cd6c044783fd413d11f8a982f@192.168.15.71' in 6400 ms (Method: BYE)

<--- Transmitting (NAT) to 192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bKad00f5add2a1f2e940a91e9a3f827b26353134;received=192.168.15.71;rport=45616
From: "211" <sip:211@192.168.15.118>;tag=2465683119
To: <sip:215@192.168.15.118>;tag=as573c52b3
Call-ID: d188757cd6c044783fd413d11f8a982f@192.168.15.71
CSeq: 5511 BYE
Server: Asterisk PBX 1.8.11.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '0d06690561757f98637241394cc8dbba@192.168.15.118:5060' in 6400 ms (Method: INVITE)
set_destination: Parsing <sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP> for address/port to send to
set_destination: set destination to 115.167.21.82:5060
Reliably Transmitting (NAT) to 192.168.15.27:5060:
BYE sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK1500d2f6;rport
Max-Forwards: 70
From: "device" <sip:211@192.168.15.118>;tag=as404f0eb0
To: <sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP>;tag=96055240
Call-ID: 0d06690561757f98637241394cc8dbba@192.168.15.118:5060
CSeq: 103 BYE
User-Agent: Asterisk PBX 1.8.11.0
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0
---
== Spawn extension (incoming-calls-wildcard, 215, 1) exited non-zero on 'SIP/211-00000008'
Retransmitting #1 (NAT) to 192.168.15.27:5060:
BYE sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK1500d2f6;rport
Max-Forwards: 70
From: "device" <sip:211@192.168.15.118>;tag=as404f0eb0
To: <sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP>;tag=96055240
Call-ID: 0d06690561757f98637241394cc8dbba@192.168.15.118:5060
CSeq: 103 BYE
User-Agent: Asterisk PBX 1.8.11.0
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0
---
<--- SIP read from UDP:192.168.15.27:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK1500d2f6;rport=5060
Contact: <sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP>
To: <sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP>;tag=96055240
From: "device"<sip:211@192.168.15.118>;tag=as404f0eb0
Call-ID: 0d06690561757f98637241394cc8dbba@192.168.15.118:5060
CSeq: 103 BYE
User-Agent: Zoiper for Windows 2.39 r16838
Content-Length: 0
<------------->
-- (9 headers 0 lines) ---
Really destroying SIP dialog '0d06690561757f98637241394cc8dbba@192.168.15.118:5060' Method: INVITE

<--- SIP read from UDP:192.168.15.27:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK1500d2f6;rport=5060
Contact: <sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP>
To: <sip:215@115.167.21.82:5060;rinstance=49cb21467969bef8;transport=UDP>;tag=96055240
From: "device"<sip:211@192.168.15.118>;tag=as404f0eb0
Call-ID: 0d06690561757f98637241394cc8dbba@192.168.15.118:5060
CSeq: 103 BYE
User-Agent: Zoiper for Windows 2.39 r16838
Content-Length: 0

<------------->
-- (9 headers 0 lines) ---
Reliably Transmitting (NAT) to 192.168.15.71:45616:
OPTIONS sip:211@192.168.15.71:45616;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK30d9d70f;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as4f0724aa
To: <sip:211@192.168.15.71:45616;transport=udp>
Contact: <sip:asterisk@192.168.15.118:5060>
Call-ID: 05f27bf10f0a0759637b90252dc4366a@192.168.15.118:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.11.0
Date: Sat, 12 Jan 2013 19:44:37 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---

<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK30d9d70f;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as4f0724aa
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 05f27bf10f0a0759637b90252dc4366a@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '05f27bf10f0a0759637b90252dc4366a@192.168.15.118:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.15.71:45616 --->
OPTIONS sip:192.168.15.118 SIP/2.0
Call-ID: a5a311df861221d42844a8c485d4fee8@192.168.15.71
CSeq: 5815 OPTIONS
From: "211" <sip:211@192.168.15.118>;tag=3109248316
To: "211" <sip:211@192.168.15.118>
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK1e09e6f6c30b4b74ddc93c590abd3383353134;rport
Max-Forwards: 70
User-Agent: SIPAUA/0.1.001
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
Looking for s in default (domain 192.168.15.118)

<--- Transmitting (NAT) to 192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK1e09e6f6c30b4b74ddc93c590abd3383353134;received=192.168.15.71;rport=45616
From: "211" <sip:211@192.168.15.118>;tag=3109248316
To: "211" <sip:211@192.168.15.118>;tag=as51223faf
Call-ID: a5a311df861221d42844a8c485d4fee8@192.168.15.71
CSeq: 5815 OPTIONS
Server: Asterisk PBX 1.8.11.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.15.118:5060>
Accept: application/sdp
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog 'a5a311df861221d42844a8c485d4fee8@192.168.15.71' in 32000 ms (Method: OPTIONS)
Reliably Transmitting (NAT) to 192.168.15.71:45616:
OPTIONS sip:211@192.168.15.71:45616;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK1f8e44dc;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as7a9a1ea3
To: <sip:211@192.168.15.71:45616;transport=udp>
Contact: <sip:asterisk@192.168.15.118:5060>
Call-ID: 7ebcafc7159379fd047075a85c424588@192.168.15.118:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.11.0
Date: Sat, 12 Jan 2013 19:44:41 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---

<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK1f8e44dc;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as7a9a1ea3
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 7ebcafc7159379fd047075a85c424588@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '7ebcafc7159379fd047075a85c424588@192.168.15.118:5060' Method: OPTIONS
Really destroying SIP dialog 'd188757cd6c044783fd413d11f8a982f@192.168.15.71' Method: BYE
Really destroying SIP dialog 'a81e6a5f591141abd73f9dad478a6b56@192.168.15.71' Method: OPTIONS
Reliably Transmitting (NAT) to 192.168.15.71:45616:
OPTIONS sip:211@192.168.15.71:45616;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK017f2b0a;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as5367b37c
To: <sip:211@192.168.15.71:45616;transport=udp>
Contact: <sip:asterisk@192.168.15.118:5060>
Call-ID: 1f5a66a10c6dc1e4126a681d2001b173@192.168.15.118:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.11.0
Date: Sat, 12 Jan 2013 19:44:44 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

---
<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK017f2b0a;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as5367b37c
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 1f5a66a10c6dc1e4126a681d2001b173@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '1f5a66a10c6dc1e4126a681d2001b173@192.168.15.118:5060' Method: OPTIONS

从pc(zoiper)调用android时

<--- SIP read from UDP:192.168.15.71:45616 --->
BYE sip:215@192.168.15.118:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bKe2f448b90c482342407298e309be5aed353134
CSeq: 1 BYE
From: <sip:211@192.168.15.71:45616;transport=udp>;tag=4162167884
To: "device" <sip:215@192.168.15.118>;tag=as5805dc66
Call-ID: 2732e4564ce8534c5765a456045a9960@192.168.15.118:5060
Max-Forwards: 70
Content-Length: 0

<------------->
--- (8 headers 0 lines) ---
Sending to 192.168.15.71:45616 (NAT)
Scheduling destruction of SIP dialog '2732e4564ce8534c5765a456045a9960@192.168.15.118:5060' in 8576 ms (Method: BYE)

<--- Transmitting (NAT) to 192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bKe2f448b90c482342407298e309be5aed353134;received=192.168.15.71;rport=45616
From: <sip:211@192.168.15.71:45616;transport=udp>;tag=4162167884
To: "device" <sip:215@192.168.15.118>;tag=as5805dc66
Call-ID: 2732e4564ce8534c5765a456045a9960@192.168.15.118:5060
CSeq: 1 BYE
Server: Asterisk PBX 1.8.11.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


<------------>
== Spawn extension (incoming-calls-wildcard, 211, 1) exited non-zero on 'SIP/215-0000000a'
Scheduling destruction of SIP dialog 'MDhhMTg1YjllYTUwZThlMmNiZTQwYTMzODYyZmEzNjk.' in 6400 ms (Method: ACK)
set_destination: Parsing <sip:215@115.167.21.82:5060;transport=UDP> for address/port to send to
set_destination: set destination to 115.167.21.82:5060
Reliably Transmitting (NAT) to 192.168.15.27:5060:
BYE sip:215@115.167.21.82:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK498da08b;rport
Max-Forwards: 70
From: <sip:211@192.168.15.118;transport=UDP>;tag=as10377813
To: <sip:215@192.168.15.118;transport=UDP>;tag=50312112
Call-ID: MDhhMTg1YjllYTUwZThlMmNiZTQwYTMzODYyZmEzNjk.
CSeq: 102 BYE
User-Agent: Asterisk PBX 1.8.11.0
Proxy-Authorization: Digest username="215", realm="asterisk", algorithm=MD5, uri="sip:192.168.15.118", nonce="", response="c897390cc8e4f674d7e9cd1efa7319a6"
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0


---
Retransmitting #1 (NAT) to 192.168.15.27:5060:
BYE sip:215@115.167.21.82:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK498da08b;rport
Max-Forwards: 70
From: <sip:211@192.168.15.118;transport=UDP>;tag=as10377813
To: <sip:215@192.168.15.118;transport=UDP>;tag=50312112
Call-ID: MDhhMTg1YjllYTUwZThlMmNiZTQwYTMzODYyZmEzNjk.
CSeq: 102 BYE
User-Agent: Asterisk PBX 1.8.11.0
Proxy-Authorization: Digest username="215", realm="asterisk", algorithm=MD5, uri="sip:192.168.15.118", nonce="", response="c897390cc8e4f674d7e9cd1efa7319a6"
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0


---

<--- SIP read from UDP:192.168.15.27:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK498da08b;rport=5060
Contact: <sip:215@115.167.21.82:5060;transport=UDP>
To: <sip:215@192.168.15.118;transport=UDP>;tag=50312112
From: <sip:211@192.168.15.118;transport=UDP>;tag=as10377813
Call-ID: MDhhMTg1YjllYTUwZThlMmNiZTQwYTMzODYyZmEzNjk.
CSeq: 102 BYE
User-Agent: Zoiper for Windows 2.39 r16838
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
SIP Response message for INCOMING dialog BYE arrived
Really destroying SIP dialog 'MDhhMTg1YjllYTUwZThlMmNiZTQwYTMzODYyZmEzNjk.' Method: ACK

<--- SIP read from UDP:192.168.15.27:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK498da08b;rport=5060
Contact: <sip:215@115.167.21.82:5060;transport=UDP>
To: <sip:215@192.168.15.118;transport=UDP>;tag=50312112
From: <sip:211@192.168.15.118;transport=UDP>;tag=as10377813
Call-ID: MDhhMTg1YjllYTUwZThlMmNiZTQwYTMzODYyZmEzNjk.
CSeq: 102 BYE
User-Agent: Zoiper for Windows 2.39 r16838
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
Reliably Transmitting (NAT) to 192.168.15.71:45616:
OPTIONS sip:211@192.168.15.71:45616;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK01e7e47d;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as73902c1e
To: <sip:211@192.168.15.71:45616;transport=udp>
Contact: <sip:asterisk@192.168.15.118:5060>
Call-ID: 7b77192d5d07c4bf5d0a82ab2c11c3c1@192.168.15.118:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.11.0
Date: Sat, 12 Jan 2013 19:54:09 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---

<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK01e7e47d;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as73902c1e
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 7b77192d5d07c4bf5d0a82ab2c11c3c1@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '7b77192d5d07c4bf5d0a82ab2c11c3c1@192.168.15.118:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.15.71:45616 --->
OPTIONS sip:192.168.15.118 SIP/2.0
Call-ID: c51761a244f0dc9639f87a5cf9af1b3f@192.168.15.71
CSeq: 9273 OPTIONS
From: "211" <sip:211@192.168.15.118>;tag=740019322
To: "211" <sip:211@192.168.15.118>
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK5ac51b5cca5ad84320fc342692fdbb2d353134;rport
Max-Forwards: 70
User-Agent: SIPAUA/0.1.001
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
Looking for s in default (domain 192.168.15.118)

<--- Transmitting (NAT) to 192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK5ac51b5cca5ad84320fc342692fdbb2d353134;received=192.168.15.71;rport=45616
From: "211" <sip:211@192.168.15.118>;tag=740019322
To: "211" <sip:211@192.168.15.118>;tag=as1bed6ef2
Call-ID: c51761a244f0dc9639f87a5cf9af1b3f@192.168.15.71
CSeq: 9273 OPTIONS
Server: Asterisk PBX 1.8.11.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.15.118:5060>
Accept: application/sdp
Content-Length: 0

<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK3c24b1cb;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as54c6581a
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 7742af6c24e3e9a33efa0ba73051a29e@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '7742af6c24e3e9a33efa0ba73051a29e@192.168.15.118:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.15.71:45616 --->
OPTIONS sip:192.168.15.118 SIP/2.0
Call-ID: 18347a0db6841423591b08250847a1e0@192.168.15.71
CSeq: 3824 OPTIONS
From: "211" <sip:211@192.168.15.118>;tag=841349553
To: "211" <sip:211@192.168.15.118>
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK79bb575a5d0f832291b861987849d9a2353134;rport
Max-Forwards: 70
User-Agent: SIPAUA/0.1.001
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
Looking for s in default (domain 192.168.15.118)


<------------->
--- (9 headers 0 lines) ---
Looking for s in default (domain 192.168.15.118)

<--- Transmitting (NAT) to 192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.71:45616;branch=z9hG4bK40d81d1686d23c9133e52f4180c2accb353134;received=192.168.15.71;rport=45616
From: "211" <sip:211@192.168.15.118>;tag=4017391219
To: "211" <sip:211@192.168.15.118>;tag=as52fe1845
Call-ID: 09809b7ed9a68b7f270f33f1d8de13dc@192.168.15.71
CSeq: 4619 OPTIONS
Server: Asterisk PBX 1.8.11.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.15.118:5060>
Accept: application/sdp
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '09809b7ed9a68b7f270f33f1d8de13dc@192.168.15.71' in 32000 ms (Method: OPTIONS)
Reliably Transmitting (NAT) to 192.168.15.71:45616:
OPTIONS sip:211@192.168.15.71:45616;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK13b8cca8;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as6e6638f8
To: <sip:211@192.168.15.71:45616;transport=udp>
Contact: <sip:asterisk@192.168.15.118:5060>
Call-ID: 76f6f373769041c3462ebb676641f1b7@192.168.15.118:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.11.0
Date: Sat, 12 Jan 2013 19:54:31 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


---

<--- SIP read from UDP:192.168.15.71:45616 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK13b8cca8;rport=5060;received=192.168.15.118
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as6e6638f8
To: <sip:211@192.168.15.71:45616;transport=udp>
Call-ID: 76f6f373769041c3462ebb676641f1b7@192.168.15.118:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Really destroying SIP dialog '76f6f373769041c3462ebb676641f1b7@192.168.15.118:5060' Method: OPTIONS
Really destroying SIP dialog '9eeee094f46eec920ac462e291314bde@192.168.15.71' Method: OPTIONS
Reliably Transmitting (NAT) to 192.168.15.71:45616:
OPTIONS sip:211@192.168.15.71:45616;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.15.118:5060;branch=z9hG4bK47a8a134;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.15.118>;tag=as76426de6
To: <sip:211@192.168.15.71:45616;transport=udp>
Contact: <sip:asterisk@192.168.15.118:5060>
Call-ID: 3a98a25b41dc3b3e699ee4383669e984@192.168.15.118:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 1.8.11.0
Date: Sat, 12 Jan 2013 19:54:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

我在本地网络 (LAN) 上使用 Asterisk ....

我在 extensions.conf 中的拨号方案是:

[incoming-calls-wildcard]

exten => _2XX,hint,(SIP/${EXTEN},,120)

exten => _2XX,1,Dial(SIP/${EXTEN},,120)

exten => _2XX,n,Hangup

我的 sip 帐号是:

[215]

deny=0.0.0.0/0.0.0.0

secret=very123

dtmfmode=rfc2833

canreinvite=no

context=incoming-calls-wildcard

host=dynamic

type=friend

nat=yes

port=5060

qualify=yes

callgroup=

pickupgroup=

dial=SIP/215

mailbox=215@device

permit=0.0.0.0/0.0.0.0

callerid=device <215>

callcounter=yes

faxdetect=no

最佳答案

感谢论坛里的每一位期待...我已经解决了问题...“xlite/zoiper”和“android native sip”客户端这两个设备使用不同的默认音频编解码器。

xlite 的默认编解码器是 BroadVoice-32

zoiper 的默认编解码器是 GSM

android 的默认编解码器是 G.711 uLaw

因为这些设备在相互通信时应该使用相同的编解码器。在我的场景中，这些设备使用不同的编解码器，这导致单向音频(从 android 调用 xlite/zoiper 时)。在 sip.conf 中创建 SIP 帐户时，我们可以按照以下方式强制两个通信客户端使用相同的音频编解码器。

[211]
deny=0.0.0.0/0.0.0.0
secret=123456
dtmfmode=rfc2833
canreinvite=no
context=incoming-calls-wildcard
host=dynamic
nat=yes
type=friend
port=5060
qualify=yes
callgroup=
pickupgroup=
permit=0.0.0.0/0.0.0.0
callcounter=yes
faxdetect=no
disallow=all    (disable default audio codec)
allow=ulaw   (allow uLaw audio codec)



[215]
deny=0.0.0.0/0.0.0.0
secret=123456
dtmfmode=rfc2833
canreinvite=no
context=incoming-calls-wildcard
host=dynamic
nat=no
type=friend
port=5060
qualify=yes
callgroup=
pickupgroup=
permit=0.0.0.0/0.0.0.0
callcounter=yes
faxdetect=no
disallow=all    (disable default audio codec)
allow=ulaw   (allow uLaw audio codec)

我们还可以通过在客户端选择相同的音频编解码器来在客户端配置音频编解码器设置。

关于android - 为什么 asterisk 不能正常使用 android sip 客户端？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/14300979/

文章推荐： android - 缺少 JDBC 驱动程序 oracle 10g android 4.x

文章推荐： java - 将 LibGDX 与 Android 首选项一起使用

文章推荐： git - 将 Git 提交差异发送到 Gist 文件

asterisk - 有没有办法在安装时指定 Asterisk 目录或从源代码中指定男性 Asterisk ？
我的 asterisk 安装(1.8.12.0，mac osx 10.8.2)有这些默认目录: * Directories ------------- Configuration file:
asterisk - Asterisk :无法连接到远程 Asterisk (是否存在/var/run/asterisk.ctl？)
Closed. This question does not meet Stack Overflow guidelines。它当前不接受答案。想改善这个问题吗？更新问题，以便将其作为on-topic
asterisk - Asterisk 拨号计划中的多行注释
我知道 Asterisk 拨号计划中的单行注释是“;”例如 ;exten => s,1,Playback(project/eligibility_points_msc) 但是拨号方案中的多行注释是用
asterisk - 有没有办法在没有电话的情况下从终端测试 Asterisk
我已经安装了 asterisk 我想测试我是否能够登录。我有 Go GoGrid。当我设置IP时，我得到的分机和密码无法到达服务器。我能够ssh进入机器。有没有办法从控制台测试 asterisk 正
asterisk - Asterisk 服务器中的问题
我尝试通过手机输入出生日期 11211971，但 IVR(交互式语音应答)输入为 11121197。请告诉任何人此问题的根本原因是什么这是我的代码 exten => s,n,Read(dateof
ubuntu - 尝试使用 Asterisk 13.16 在 Ubuntu 16.04 上安装 freepbx 14 - 错误 : can't communicate with asterisk, asterisk appears being running as asterisk
由于我没有收到来自 freepbx 社区的确认邮件，我不得不在这里发布我的问题。正如标题所说，我正在尝试安装 freepbx。错误信息是:错误!与 Asterisk 通信时出错。确保 Asteris
asterisk - 预测拨号 : Asterisk-Jitsi
我想为一个项目开发一个预测拨号模块。我有一个非常关键的疑问，实际的预测拨号过程应该在哪里运行？它不应该在 Asterisk 服务器上运行吗？如果是这样，请您指导我获取对我的开发过程有帮助的文档。谢谢
asterisk - 无法播放 Asterisk 中保留的音乐
在我的拨号方案中，保持音乐在早些时候工作但现在不工作。我的 musiconhold.conf ; ; Music on Hold -- Sample Configuration ; [old-
asterisk - 如何使用负载平衡和 Asterisk 配置kamailio服务器？
已关闭。此问题不符合Stack Overflow guidelines 。目前不接受答案。这个问题似乎不是关于 a specific programming problem, a software
asterisk - 如何将 Asterisk 调用的通话持续时间插入到我自己的数据库中？
我有自己的数据库来记录 Asterisk 中的调用。我需要将每次通话的通话持续时间插入表中。我怎样才能做到这一点？我可以在我的拨号方案中执行此操作吗？最佳答案您没有提供太多有关您想要使用的数据库后
asterisk - 如何检查 Asterisk 中继的状态
因此，如果我键入 sip show peers，我会得到一个表，告诉我中继的状态是“OK”，但我认为它不会测试验证是否有效。有没有办法测试中继线是否正常以及调用是否可以通过？最佳答案您可以通过检查
asterisk - 如何上传 Asterisk 中的声音文件？
我已经创建了一个 Asterisk 服务器。我能够从一个拨号器向另一个拨号器调用电话并且它工作正常。当两个拨号器之间建立连接时，我需要播放一个语音脚本，由 Asterisk 提供。我需要在 Aste
asterisk - 如何在 Asterisk 中调用上下文并返回主上下文？
这是我的 Asterisk 拨号计划: [main-context] exten => s,1,Gosub(subcontext,s,1) exten => s,n,NoOp(End Main) [s
asterisk - LAN 的简单 Asterisk 设置
我一直在来回尝试想要找到一种通过 LAN/WiFi 轻松通信的方法，通过 LAN 网络调用电话会很棒，所以我尝试了几次 Asterisk 并迷失了方向，我似乎无法让它工作，我购买的电子书支持我购买 D
asterisk - Asterisk 中的 channel 名称
我正在使用 Asterisk 11。当我试图呼出时，我在获取 channel 名称时遇到了问题。通常，当被叫方拿起他/她的电话时，我可以得到 channel 名称。但是现在，我想在拨出后立即获取 ch
asterisk - 在 Asterisk 服务器和Polycom Soundstation上启用高清语音
Closed. This question does not meet Stack Overflow guidelines。它当前不接受答案。想改善这个问题吗？更新问题，以使为on-topic。 2
asterisk - PHPAGI/Cepstral/Asterisk - 许可证问题
我正在 PHPAGI 中为 Asterisk 编写 IVR 脚本，并尝试使用 Cepstral 进行 TTS。尽管我已经获得了该产品的许可，但当我调用 $agi->swift() 时，在我的文本被“读
asterisk - Asterisk 中的自定义 IVR 操作
有人可以给我指出一个方向、示例代码或在线资源来完成以下任务吗: 要求:我想编写一个简单的 IVR 菜单选项来运行脚本(Bash 或 Python)。例如，给 Asterisk 机器打电话并请求重新启动
asterisk - Asterisk 中的直接媒体和直接 RTP 设置
我想在我使用的 Asterisk 中设置直接点对点媒体设置 directrtpsetup=yes 我也想在不重新邀请的情况下实现它。所以我使用了这个参数。在 sip.conf 中写到它不需要重新邀请就
php - Asterisk -哪个 Asterisk PHP库？
Closed. This question does not meet Stack Overflow guidelines。它当前不接受答案。想改善这个问题吗？更新问题，以便将其作为on-topic

太空狗

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

android - 为什么 asterisk 不能正常使用 android sip 客户端？