|
10.0.0.7
клиент
10.0.0.1 Communigate
10.0.0.151 Asterisk
Вот что пишет Asterisk:
---
[May 18 17:40:39]
DEBUG[10219] sip/sdp_crypto.c: Accepting crypto tag 1
[May 18 17:40:39] DEBUG[10219] sip/sdp_crypto.c: Crypto line:
a=crypto:1 AES_CM_128_HMAC_SHA1_32
inline:wxXSdusmuDEXY57X6izpcoPWAgjIakCEizBH+Iq9
[May 18 17:40:39] WARNING[10219] chan_sip.c: We are requesting SRTP
for audio, but they responded without it!
---
Лог Communigate
---
17:40:46.288 2
MEDIAPROXY-000161 UDPPROXY-000330 created
17:40:46.288 2 UDPPROXY-000330
[10.0.0.7]:50008:50009 <-> [0.0.0.0]:0:0 by SDP
17:40:46.288 2
MEDIAPROXY-000161 set: [10.0.0.7] <-> [10.0.0.151]
17:40:46.288 2
SIPDATA-018467 out: req [10.0.0.1]:5060 -> udp[10.0.0.151]:5060 INVITE(1354
bytes) sip:911@10.0.0.151
17:40:46.288 5 SIPDATA-018467 out: INVITE
sip:911@10.0.0.151 SIP/2.0
17:40:46.288 5 SIPDATA-018467 out: Via:
SIP/2.0/UDP 10.0.0.1:5060;branch=z9hG4bK1184;rport
17:40:46.288 5
SIPDATA-018467 out: P-Asserted-Identity:
<sip:alex@10.0.0.1>
17:40:46.288 5 SIPDATA-018467 out: Record-Route:
<sip:10.0.0.1:5060;lr>
17:40:46.288 5 SIPDATA-018467 out: Record-Route:
<sip:rev.648.dialog.cgatepro;lr>
17:40:46.288 5 SIPDATA-018467 out:
Max-Forwards: 69
17:40:46.288 5 SIPDATA-018467 out: From:
<sip:alex@10.0.0.1>;tag=483F5CC0-3002-88E3017F
17:40:46.288 5
SIPDATA-018467 out: To: <sip:911@10.0.0.151>
17:40:46.288 5
SIPDATA-018467 out: Call-ID: ximss-34C86D01434FFC503F5F-8046@10.0.0.1.gwout3221
17:40:46.288
5 SIPDATA-018467 out: Contact:
<sip:signode-3002-88E3017F@10.0.0.1>
17:40:46.288 5 SIPDATA-018467 out:
CSeq: 2 INVITE
17:40:46.288 5 SIPDATA-018467 out: Supported:
100rel,timer,replaces,histinfo,precondition
17:40:46.288 5 SIPDATA-018467
out: Session-Expires: 300
17:40:46.288 5 SIPDATA-018467 out: Min-SE:
90
17:40:46.288 5 SIPDATA-018467 out: User-Agent:
CommuniGatePro-callLeg/6.0.5
17:40:46.288 5 SIPDATA-018467 out: Allow:
INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER
17:40:46.288
5 SIPDATA-018467 out: Authorization: Digest
username="pbx-gw",realm="asterisk",nonce="025702d7",uri="sip:911@10.0.0.151",response="ffa87b6554ed1db6bef9c0e57f13f1ba",algorithm=MD5
17:40:46.288
5 SIPDATA-018467 out: Content-Type: application/sdp
17:40:46.288 5
SIPDATA-018467 out: Content-Length: 458
17:40:46.288 5 SIPDATA-018467 out:
17:40:46.288 5 SIPDATA-018467 out: v=0
17:40:46.288 5 SIPDATA-018467 out:
o=CGPLeg003002 3912483609 1956241805 IN IP4 195.22.131.230
17:40:46.288 5
SIPDATA-018467 out: s=-
17:40:46.288 5 SIPDATA-018467 out: c=IN IP4
10.0.0.1
17:40:46.288 5 SIPDATA-018467 out: t=0 0
17:40:46.288 5
SIPDATA-018467 out: a=mediagateway:10.0.0.1:648
17:40:46.288 5 SIPDATA-018467
out: m=audio 48334 RTP/AVP 0 8 101
17:40:46.288 5 SIPDATA-018467 out: c=IN
IP4 10.0.0.1
17:40:46.288 5 SIPDATA-018467 out: a=crypto:1
AES_CM_128_HMAC_SHA1_32
inline:AqOXUQ0UkwU5KJk0kfoCH8PAHZxq2AA6DR5vhCf2
17:40:46.288 5 SIPDATA-018467
out: a=rtpmap:0 PCMU/8000
17:40:46.288 5 SIPDATA-018467 out: a=rtpmap:8
PCMA/8000
17:40:46.288 5 SIPDATA-018467 out: a=rtpmap:101
telephone-event/8000
17:40:46.288 5 SIPDATA-018467 out: a=fmtp:101
0-16,32-49,64-89
17:40:46.288 5 SIPDATA-018467 out:
a=sendrecv
17:40:46.288 5 SIPDATA-018467 out:
a=rtcpping:T:330:16578
17:40:46.288 5 SIPDATA-018467 out:
a=ice-pwd:pp0000330
17:40:46.288 5 SIPDATA-018467 out:
a=ice-ufrag:pt0000330
17:40:46.288 2 SIPDATA-018468 inp: rsp [0.0.0.0]:5060
<- udp[10.0.0.151]:5060 488-INVITE(464 bytes)
17:40:46.288 5
SIPDATA-018468 inp: SIP/2.0 488 Not acceptable here
17:40:46.288 5
SIPDATA-018468 inp: Via: SIP/2.0/UDP
10.0.0.1:5060;branch=z9hG4bK1184;received=10.0.0.1;rport=5060
17:40:46.288 5
SIPDATA-018468 inp: From:
<sip:alex@10.0.0.1>;tag=483F5CC0-3002-88E3017F
17:40:46.288 5
SIPDATA-018468 inp: To:
<sip:911@10.0.0.151>;tag=as3bfb53c7
17:40:46.288 5 SIPDATA-018468 inp:
Call-ID: ximss-34C86D01434FFC503F5F-8046@10.0.0.1.gwout3221
17:40:46.288
5 SIPDATA-018468 inp: CSeq: 2 INVITE
17:40:46.288 5 SIPDATA-018468 inp:
Server: FPBX-2.8.1(1.8.21.0)
17:40:46.288 5 SIPDATA-018468 inp: Allow:
INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO,
PUBLISH
17:40:46.288 5 SIPDATA-018468 inp: Supported: replaces,
timer
17:40:46.288 5 SIPDATA-018468 inp: Content-Length: 0
17:40:46.288 5
SIPDATA-018468 inp:
17:40:46.288 2 SIPDATA-018468 sent to
SIPC-001184
17:40:46.288 2 SIPDATA-018469 out: req [10.0.0.1]:5060 ->
udp[10.0.0.151]:5060 ACK(362 bytes) sip:911@10.0.0.151
17:40:46.288 5
SIPDATA-018469 out: ACK sip:911@10.0.0.151 SIP/2.0
17:40:46.288 5
SIPDATA-018469 out: P-Asserted-Identity:
<sip:alex@10.0.0.1>
17:40:46.288 5 SIPDATA-018469 out: Via: SIP/2.0/UDP
10.0.0.1:5060;branch=z9hG4bK1184;rport
17:40:46.288 5 SIPDATA-018469 out:
Max-Forwards: 69
17:40:46.288 5 SIPDATA-018469 out: From:
<sip:alex@10.0.0.1>;tag=483F5CC0-3002-88E3017F
17:40:46.288 5
SIPDATA-018469 out: To:
<sip:911@10.0.0.151>;tag=as3bfb53c7
17:40:46.288 5 SIPDATA-018469 out:
Call-ID: ximss-34C86D01434FFC503F5F-8046@10.0.0.1.gwout3221
17:40:46.288
5 SIPDATA-018469 out: CSeq: 2 ACK
17:40:46.288 5 SIPDATA-018469 out:
Content-Length: 0
17:40:46.288 5 SIPDATA-018469 out:
17:40:46.288 2
MEDIAPROXY-000161 UDPPROXY-000330 removed
---
Покурив интернет выяснилось, что Asterisk "плохо
реагирует" на AES_CM_128_HMAC_SHA1_32, но нормально переваривает
AES_CM_128_HMAC_SHA1_80
или когда эти
методы идут на выбор, он выбирает то, что может переварить
(AES_CM_128_HMAC_SHA1_80) например:
---
a=crypto:0 AES_CM_128_HMAC_SHA1_32
inline:7xbCvhQwUpfdCPIAk4nzDauvMK3l9sWIGlyLh+/l
a=crypto:1
AES_CM_128_HMAC_SHA1_80 inline:R5CPl/gPmcEQzmjOVUZnhupuuzNf/VNVILwfpKtf
---
Может быть ктонить знает как попросить Communigate или
отсылать AES_CM_128_HMAC_SHA1_80 или оба метода AES_CM_128_HMAC_SHA1_32 и
AES_CM_128_HMAC_SHA1_80
---
(c)ALex
Notebook.jpg
|