[asterisk-bugs] [JIRA] (ASTERISK-24855) NOTIFY with sips
Richard Mudgett (JIRA)
noreply at issues.asterisk.org
Mon Mar 9 11:19:35 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-24855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Mudgett updated ASTERISK-24855:
---------------------------------------
Description:
NOTIFY with TLS send wrong protocol schema in routing headers.
sip:sips
{noformat}
----------------------------------------
-- 2015-03-08 20:30:19 - Received from ASTERISK_PUB_IP:5061 at 192.168.88.254:5069
NOTIFY sips:10102 at 192.168.88.254:5069 SIP/2.0
Via: SIP/2.0/TLS ASTERISK_PUB_IP:5061;branch=z9hG4bK5a08186f;rport
Max-Forwards: 70
Route: <sips:10102 at 192.168.88.254:5069>
From: "capbxsrv01" <sip:capbxsrv01 at ASTERISK_PUB_IP>;tag=as6f8f9fea
To: <sip:sips:10102 at 192.168.88.254:5069>;tag=d92d0bcee3
Contact: <sip:capbxsrv01 at ASTERISK_PUB_IP:5061;transport=TLS>
Call-ID: 35667ff0c4c88d84
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX(11.15.1)
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 105
Messages-Waiting: yes
Message-Account: sip:*97 at ASTERISK_PUB_IP;transport=TLS
Voice-Message: 24/4 (0/0)
----------------------------------------
-- 2015-03-08 20:30:19 - Sent to ASTERISK_PUB_IP:5061 from 192.168.88.254:5069
SIP/2.0 200 OK
Via: SIP/2.0/TLS ASTERISK_PUB_IP:5061;branch=z9hG4bK5a08186f;rport=5061;received=ASTERISK_PUB_IP
From: "capbxsrv01" <sip:capbxsrv01 at ASTERISK_PUB_IP>;tag=as6f8f9fea
To: <sip:sips:10102 at 192.168.88.254:5069>;tag=d92d0bcee3
Call-ID: 35667ff0c4c88d84
CSeq: 102 NOTIFY
Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE
Server: Media5-fone/4.1.6.3283 Android/5.0.1
Supported: eventlist, replaces, timer
Content-Length: 0
{noformat}
was:
NOTIFY with TLS send wrong protocol schema in routing headers.
sip:sips
----------------------------------------
-- 2015-03-08 20:30:19 - Received from ASTERISK_PUB_IP:5061 at 192.168.88.254:5069
NOTIFY sips:10102 at 192.168.88.254:5069 SIP/2.0
Via: SIP/2.0/TLS ASTERISK_PUB_IP:5061;branch=z9hG4bK5a08186f;rport
Max-Forwards: 70
Route: <sips:10102 at 192.168.88.254:5069>
From: "capbxsrv01" <sip:capbxsrv01 at ASTERISK_PUB_IP>;tag=as6f8f9fea
To: <sip:sips:10102 at 192.168.88.254:5069>;tag=d92d0bcee3
Contact: <sip:capbxsrv01 at ASTERISK_PUB_IP:5061;transport=TLS>
Call-ID: 35667ff0c4c88d84
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX(11.15.1)
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 105
Messages-Waiting: yes
Message-Account: sip:*97 at ASTERISK_PUB_IP;transport=TLS
Voice-Message: 24/4 (0/0)
----------------------------------------
-- 2015-03-08 20:30:19 - Sent to ASTERISK_PUB_IP:5061 from 192.168.88.254:5069
SIP/2.0 200 OK
Via: SIP/2.0/TLS ASTERISK_PUB_IP:5061;branch=z9hG4bK5a08186f;rport=5061;received=ASTERISK_PUB_IP
From: "capbxsrv01" <sip:capbxsrv01 at ASTERISK_PUB_IP>;tag=as6f8f9fea
To: <sip:sips:10102 at 192.168.88.254:5069>;tag=d92d0bcee3
Call-ID: 35667ff0c4c88d84
CSeq: 102 NOTIFY
Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE
Server: Media5-fone/4.1.6.3283 Android/5.0.1
Supported: eventlist, replaces, timer
Content-Length: 0
> NOTIFY with sips
> ----------------
>
> Key: ASTERISK-24855
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24855
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/Subscriptions, Channels/chan_sip/TCP-TLS
> Affects Versions: 11.15.1, 12.8.1
> Environment: Linux canlpbx02. 2.6.32-431.el6.x86_64
> Reporter: Slava Bendersky
> Severity: Critical
>
> NOTIFY with TLS send wrong protocol schema in routing headers.
> sip:sips
> {noformat}
> ----------------------------------------
> -- 2015-03-08 20:30:19 - Received from ASTERISK_PUB_IP:5061 at 192.168.88.254:5069
> NOTIFY sips:10102 at 192.168.88.254:5069 SIP/2.0
> Via: SIP/2.0/TLS ASTERISK_PUB_IP:5061;branch=z9hG4bK5a08186f;rport
> Max-Forwards: 70
> Route: <sips:10102 at 192.168.88.254:5069>
> From: "capbxsrv01" <sip:capbxsrv01 at ASTERISK_PUB_IP>;tag=as6f8f9fea
> To: <sip:sips:10102 at 192.168.88.254:5069>;tag=d92d0bcee3
> Contact: <sip:capbxsrv01 at ASTERISK_PUB_IP:5061;transport=TLS>
> Call-ID: 35667ff0c4c88d84
> CSeq: 102 NOTIFY
> User-Agent: Asterisk PBX(11.15.1)
> Event: message-summary
> Content-Type: application/simple-message-summary
> Subscription-State: active
> Content-Length: 105
> Messages-Waiting: yes
> Message-Account: sip:*97 at ASTERISK_PUB_IP;transport=TLS
> Voice-Message: 24/4 (0/0)
> ----------------------------------------
> -- 2015-03-08 20:30:19 - Sent to ASTERISK_PUB_IP:5061 from 192.168.88.254:5069
> SIP/2.0 200 OK
> Via: SIP/2.0/TLS ASTERISK_PUB_IP:5061;branch=z9hG4bK5a08186f;rport=5061;received=ASTERISK_PUB_IP
> From: "capbxsrv01" <sip:capbxsrv01 at ASTERISK_PUB_IP>;tag=as6f8f9fea
> To: <sip:sips:10102 at 192.168.88.254:5069>;tag=d92d0bcee3
> Call-ID: 35667ff0c4c88d84
> CSeq: 102 NOTIFY
> Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE
> Server: Media5-fone/4.1.6.3283 Android/5.0.1
> Supported: eventlist, replaces, timer
> Content-Length: 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list