[asterisk-bugs] [JIRA] (ASTERISK-28299) 481 Call/Transaction Does Not Exist on receiving MESSAGE event

Joshua C. Colp (JIRA) noreply at issues.asterisk.org
Mon Feb 25 08:29:47 CST 2019


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

Joshua C. Colp commented on ASTERISK-28299:
-------------------------------------------

I believe this is a bug in the remote side. A SIP transaction consists of a request, and then responses. The following is a transaction:

{noformat}
<--- Received SIP request (456 bytes) from UDP:10.0.0.1:5060 --->
MESSAGE sip:s at 10.75.22.8:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.1:5060;branch=z9hG4bK51d6d4da;rport
Max-Forwards: 70
From: "5555551212" <sip:5555551212 at itsp.example.com>;tag=as6c34cb69
To: <sip:s at 10.75.22.8:5060>
Contact: <sip:5555551212 at 10.0.0.1:5060>
Call-ID: 3e9735b4313e58f90b4b61c82f392c2e at 10.0.0.1:5060
CSeq: 102 MESSAGE
User-Agent: itsp.example.com
X-SMS-To: 5551234567
Content-Type: text/plain;charset=UTF-8
Content-Length: 1

test message
<--- Transmitting SIP response (515 bytes) to UDP:10.0.0.1:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.0.0.1:5060;rport=5060;received=10.0.0.1;branch=z9hG4bK51d6d4da
Call-ID: 3e9735b4313e58f90b4b61c82f392c2e at 10.0.0.1:5060
From: "5555551212" <sip:5555551212 at itsp.example.com>;tag=as6c34cb69
To: <sip:s at 10.75.22.8>;tag=z9hG4bK51d6d4da
CSeq: 102 MESSAGE
WWW-Authenticate: Digest realm="asterisk",nonce="1550441754/[redacted]",opaque="2c504a1035f74a1d",algorithm=md5,qop="auth"
Server: Asterisk PBX 13.25.0
Content-Length:  0
{noformat}

Since a 401 was sent, the transaction was completed.

The remote side then attempts to resend the MESSAGE with the same call id and within the same transaction. The code then bounces it back as there is no dialog and the transaction is over - you can't send another request using it. What should happen is that the MESSAGE with authentication details should not have a To tag. This would start a new transaction.

> 481 Call/Transaction Does Not Exist on receiving MESSAGE event
> --------------------------------------------------------------
>
>                 Key: ASTERISK-28299
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28299
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_messaging
>    Affects Versions: 13.25.0
>            Reporter: Brian J. Murrell
>            Severity: Minor
>
> When my ITSP tries to send a (SIP SIMPLE) MESSAGE event to my Asterisk machine, Asterisk responds with {{SIP/2.0 481 Call/Transaction Does Not Exist}} which doesn't really make any sense to me for a single/one-off event like a MESSAGE event.  MESSAGE events don't seem to involve "transactions" which must exist.
> My ITSP configuration:
> {noformat}
> [trunk]
> type=registration
> transport=transport-udp
> outbound_auth=trunk-auth
> server_uri=sip:itsp.example.com
> client_uri=sip:userid at itsp.example.com
> [trunk-auth]
> type=auth
> auth_type=userpass
> password=********
> username=userid
> [trunk-endpoint](!)
> type=endpoint
> transport=transport-udp
> context=from-trunk
> message_context=messages
> disallow=all
> allow=ulaw
> from_user=userid
> outbound_auth=trunk-auth
> auth=trunk-auth
> send_pai=yes
> [trunk-aor](!)
> type=aor
> qualify_frequency=15
> [trunk-foo](trunk-endpoint)
> aors=trunk-foo
> [trunk-foo](trunk-aor)
> contact=sip:userid at itsp.example.com:5060
> [trunk-foo]
> type=identify
> endpoint=trunk-foo
> match=itsp.example.com
> {noformat}
> The SIP conversation when the ITSP is trying to send the MESSAGE:
> {noformat}
> <--- Received SIP request (456 bytes) from UDP:10.0.0.1:5060 --->
> MESSAGE sip:s at 10.75.22.8:5060 SIP/2.0
> Via: SIP/2.0/UDP 10.0.0.1:5060;branch=z9hG4bK51d6d4da;rport
> Max-Forwards: 70
> From: "5555551212" <sip:5555551212 at itsp.example.com>;tag=as6c34cb69
> To: <sip:s at 10.75.22.8:5060>
> Contact: <sip:5555551212 at 10.0.0.1:5060>
> Call-ID: 3e9735b4313e58f90b4b61c82f392c2e at 10.0.0.1:5060
> CSeq: 102 MESSAGE
> User-Agent: itsp.example.com
> X-SMS-To: 5551234567
> Content-Type: text/plain;charset=UTF-8
> Content-Length: 1
> test message
> <--- Transmitting SIP response (515 bytes) to UDP:10.0.0.1:5060 --->
> SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 10.0.0.1:5060;rport=5060;received=10.0.0.1;branch=z9hG4bK51d6d4da
> Call-ID: 3e9735b4313e58f90b4b61c82f392c2e at 10.0.0.1:5060
> From: "5555551212" <sip:5555551212 at itsp.example.com>;tag=as6c34cb69
> To: <sip:s at 10.75.22.8>;tag=z9hG4bK51d6d4da
> CSeq: 102 MESSAGE
> WWW-Authenticate: Digest realm="asterisk",nonce="1550441754/[redacted]",opaque="2c504a1035f74a1d",algorithm=md5,qop="auth"
> Server: Asterisk PBX 13.25.0
> Content-Length:  0
> <--- Received SIP request (707 bytes) from UDP:10.0.0.1:5060 --->
> MESSAGE sip:s at 10.75.22.8:5060 SIP/2.0
> Via: SIP/2.0/UDP 10.0.0.1:5060;branch=z9hG4bK516e2ba7;rport
> Max-Forwards: 70
> From: "5555551212" <sip:5555551212 at itsp.example.com>;tag=as6c34cb69
> To: <sip:s at 10.75.22.8:5060>;tag=z9hG4bK51d6d4da
> Call-ID: 3e9735b4313e58f90b4b61c82f392c2e at 10.0.0.1:5060
> CSeq: 103 MESSAGE
> User-Agent: itsp.example.com
> Proxy-Authorization: Digest username="userid", realm="asterisk", algorithm=MD5, uri="sip:s at 172.1.2.3:5060", nonce="1550441754/[redacted]", response="[redacted]", opaque="2c504a1035f74a1d", qop=auth, cnonce="544772bb", nc=00000002
> X-SMS-To: 5551234567
> Content-Type: text/plain;charset=UTF-8
> Content-Length: 1
> c
> <--- Transmitting SIP response (388 bytes) to UDP:10.0.0.1:5060 --->
> SIP/2.0 481 Call/Transaction Does Not Exist
> Via: SIP/2.0/UDP 10.0.0.1:5060;rport=5060;received=10.0.0.1;branch=z9hG4bK516e2ba7
> Call-ID: 3e9735b4313e58f90b4b61c82f392c2e at 10.0.0.1:5060
> From: "5555551212" <sip:5555551212 at itsp.example.com>;tag=as6c34cb69
> To: <sip:s at 10.75.22.8>;tag=z9hG4bK51d6d4da
> CSeq: 103 MESSAGE
> Server: Asterisk PBX 13.25.0
> Content-Length:  0
> {noformat}



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



More information about the asterisk-bugs mailing list