[asterisk-bugs] [JIRA] (ASTERISK-23613) PJSIP no response to in dialog OPTIONS message
yaron nahum (JIRA)
noreply at issues.asterisk.org
Thu Apr 10 08:57:18 CDT 2014
yaron nahum created ASTERISK-23613:
--------------------------------------
Summary: PJSIP no response to in dialog OPTIONS message
Key: ASTERISK-23613
URL: https://issues.asterisk.org/jira/browse/ASTERISK-23613
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: Resources/res_pjsip
Affects Versions: 12.1.0, 12.2.0
Environment: CentOS release 5.4 (Final)
Reporter: yaron nahum
I have an Asterisk 12 with PJSIP configured working againt a Comverse (NetCentrex) Switch. The Comverse switch sends periodically Session Keep-Alive every 200 seconds using OPTIONS method.
The asterisk is not responding to the Keep alive therefore the call is disconnected.
Below is the debug taken from the server:
##############################3
[Apr 10 16:16:40] DEBUG[13801] pjsip: sip_endpoint.c Processing incoming message: Request msg OPTIONS/cseq=2 (rdata0xa5b03b4)
[Apr 10 16:16:40] VERBOSE[13801] res_pjsip_logger.c: <--- Received SIP request (393 bytes) from UDP:172.16.60.160:5080 --->
OPTIONS sip:172.16.60.160:5061;transport=UDP SIP/2.0^M
Via: SIP/2.0/UDP 172.16.60.160:5080^M
From: <sip:39919002;cpc=ordinary at 172.16.60.160:5080;user=phone>;tag=1^M
To: <sip:039988120 at 172.16.60.160:5060>;tag=9d105b31-3396-4aa5-afe3-c519ee8b5db2^M
Call-ID: 1-17908 at 172.16.60.160^M
Cseq: 2 OPTIONS^M
Contact: sip:39919002 at 172.16.60.160:5080^M
Max-Forwards: 60^M
Subject: Simulator^M
Content-Length: 0^M
^M
[Apr 10 16:16:40] DEBUG[17772] pjsip: sip_endpoint.c Distributing rdata to modules: Request msg OPTIONS/cseq=2 (rdata0xb411493c)
[Apr 10 16:16:40] DEBUG[17772] pjsip: dlg0xb4111eb4 .Received Request msg OPTIONS/cseq=2 (rdata0xb411493c)
[Apr 10 16:16:40] DEBUG[17772] pjsip: tsx0xb7d74764 ...Transaction created for Request msg OPTIONS/cseq=2 (rdata0xb411493c)
[Apr 10 16:16:40] DEBUG[17772] pjsip: tsx0xb7d74764 ..Incoming Request msg OPTIONS/cseq=2 (rdata0xb411493c) in state Null
[Apr 10 16:16:40] DEBUG[17772] pjsip: tsx0xb7d74764 ...State changed from Null to Trying, event=RX_MSG
[Apr 10 16:16:40] DEBUG[17772] pjsip: dlg0xb4111eb4 ....Transaction tsx0xb7d74764 state changed to Trying
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: Function session_inv_on_tsx_state_changed called on event TSX_STATE
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: The state change pertains to the session with sipp
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: The inv session does NOT have an invite_tsx
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: The transaction involved in this state change is 0xb7d74764
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: The current transaction state is Trying
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: The transaction state change event is RX_MSG
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: The current inv state is CONFIRMED
[Apr 10 16:16:40] DEBUG[17772] res_pjsip_session.c: Method is OPTIONS
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list