[asterisk-bugs] [JIRA] (ASTERISK-27682) PJSIP outbound-publish, ETag and Event: dialog

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242240#comment-242240 ] 

Richard Mudgett commented on ASTERISK-27682:
--------------------------------------------

Yes.  Asterisk v14 no longer receives bug fixes as of 2017-09-26 per the linked page \[1].  What you are reporting is not a security issue so it will never be fixed in v14.

\[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

> PJSIP outbound-publish, ETag and Event: dialog
> ----------------------------------------------
>
>                 Key: ASTERISK-27682
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27682
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 14.7.5
>            Reporter: Cyrille Demaret
>              Labels: pjsip
>
> Asterisk is sending a PUBLISH with a "early" state with a SIP-If-Match for an already terminated dialog. According to the RFC 4235, this shouldn't happens.
> Asterisk send :
> PUBLISH sip:201 at 192.168.100.37 SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.37:5080;rport;branch=z9hG4bKPj4f9c19eb-26d8-4bb1-8f00-e69723a61082
> From: sip:201 at mydomain.com;tag=a560e088-9e8a-49f2-a9b1-4a0ec31340bf
> To: sip:201 at mydomain.com
> Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183
> CSeq: 10697 PUBLISH
> Event: dialog
> Expires: 180
> Max-Forwards: 70
> User-Agent: Asterisk PBX 14.6.0
> Content-Type: application/dialog-info+xml
> Content-Length: 247
> <?xml version="1.0" encoding="UTF-8"?> early
> The presence server replies :
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.100.37:5080;rport=5080;branch=z9hG4bKPj4f9c19eb-26d8-4bb1-8f00-e69723a61082;received=192.168.100.37
> From: sip:201 at mydomain.com;tag=a560e088-9e8a-49f2-a9b1-4a0ec31340bf
> To: sip:201 at mydomain.com;tag=b596189c6de9c38f624fd84638f43be6-ff39
> Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183
> CSeq: 10697 PUBLISH
> Expires: 180
> SIP-ETag: a.1518775074.19863.16.0
> Server: kamailio (5.0.5 (x86_64/linux))
> Content-Length: 0
> When the call is done, Asterisk send another PUBLISH telling that the call is terminated :
> PUBLISH sip:201 at 192.168.100.37 SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.37:5080;rport;branch=z9hG4bKPja93efb01-a518-445e-9e9b-f6f97ab8c752
> From: sip:201 at mydomain.com;tag=165fb3b2-ec0e-4786-889f-eb194ad456ce
> To: sip:201 at mydomain.com
> Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183
> CSeq: 10698 PUBLISH
> Event: dialog
> SIP-If-Match: a.1518775074.19863.16.0
> Expires: 180
> Max-Forwards: 70
> User-Agent: Asterisk PBX 14.6.0
> Content-Type: application/dialog-info+xml
> Content-Length: 230
> <?xml version="1.0" encoding="UTF-8"?> terminated
> The presence server replies :
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.100.37:5080;rport=5080;branch=z9hG4bKPja93efb01-a518-445e-9e9b-f6f97ab8c752;received=192.168.100.37
> From: sip:201 at mydomain.com;tag=165fb3b2-ec0e-4786-889f-eb194ad456ce
> To: sip:201 at mydomain.com;tag=b596189c6de9c38f624fd84638f43be6-48b4
> Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183
> CSeq: 10698 PUBLISH
> Expires: 180
> SIP-ETag: a.1518775074.19873.18.1
> Server: kamailio (5.0.5 (x86_64/linux))
> Content-Length: 0
> If a new call is made before the expiration, Asterisk reuse the same ETag:
> PUBLISH sip:201 at 192.168.100.37 SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.37:5080;rport;branch=z9hG4bKPj9d13bb82-31d9-48db-9672-bd4b6b4f22f0
> From: sip:201 at mydomain.com;tag=33e6b028-0444-4b3a-8bc2-4a987a291528
> To: sip:201 at mydomain.com
> Call-ID: 5adcf0a0-f138-44d6-8c56-eaf7c3b3b183
> CSeq: 10699 PUBLISH
> Event: dialog
> SIP-If-Match: a.1518775074.19873.18.1
> Expires: 180
> Max-Forwards: 70
> User-Agent: Asterisk PBX 14.6.0
> Content-Type: application/dialog-info+xml
> Content-Length: 247
> <?xml version="1.0" encoding="UTF-8"?> early



--
This message was sent by Atlassian JIRA
(v6.2#6252)