[asterisk-bugs] [JIRA] (ASTERISK-23613) Endpoint identification fails when user part of From header SIP-URI contains a tel URI style parameter
yaron nahum (JIRA)
noreply at issues.asterisk.org
Tue Apr 22 04:58:19 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-23613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yaron nahum updated ASTERISK-23613:
-----------------------------------
Status: Waiting for Feedback (was: Waiting for Feedback)
In my case a response is not sent at all. I have tried to remove the cpc=ordinary and it is still not responding to OPTIONS message.
my pjsip.conf is very simple:
[sipp]
type=endpoint
transport=transport-udp
;send_pai=yes
context=from-external
;trust_id_outbound=yes
;trust_id_inbound=yes
;callerid_privacy=allowed
disallow=all
allow=alaw
100rel=required
from_domain=172.16.60.160
;qualify_frequency=10
;outbound_auth=mytrunk_auth
aors=sipp
direct_media_glare_mitigation=none
direct_media=no
;redirect_method=uri_core
; ;A few NAT relevant options that may come in handy.
;force_rport=yes ;It's a good idea to read the configuration help for each
;direct_media=no ;of these options.
;ice_support=yes
;timers_min_se=90
;timers=required
[sipp]
type=aor
;max_contacts=2
contact=sip:172.16.60.160:5080\;user=phone
contact=sip:172.16.10.2:5060
contact=sip:172.16.10.3:5060
;contact=sip:10.25.153.150:5060
;qualify_frequency=10
;default_expiration=10
[sipp]
type=identify
endpoint=sipp
match=10.25.153.150
match=172.16.60.160
match=172.16.10.2
match=172.16.10.3
;OSP
[osp]
type=endpoint
send_pai=yes
transport=transport-udp
context=from-osp
disallow=all
allow=alaw
;100rel=required
;qualify_frequency=10
;outbound_auth=mytrunk_auth
aors=osp
;redirect_method=uri_core
; ;A few NAT relevant options that may come in handy.
;force_rport=yes ;It's a good idea to read the configuration help for each
;direct_media=no ;of these options.
;ice_support=yes
[osp]
type=aor
;max_contacts=2
;contact=sip:172.16.60.160:5080
;contact=sip:10.25.153.150:5060
;qualify_frequency=10
;default_expiration=10
contact=sip:10.9.1.38:5060
contact=sip:10.9.129.38:5060
[osp]
type=identify
endpoint=osp
match=10.9.1.38
match=10.9.129.38
and in my extensions.ael I just do Answer(), Wait(500) and than hangup.
One thing I find very strange is timeout message after the ACK is received. you can see it at the bottom of my response. Can you send me a trace that works - I will try to simulate it here and then try to play with it until it breaks.
[Apr 22 10:56:21] DEBUG[27818] pjsip: sip_endpoint.c Processing incoming message: Request msg ACK/cseq=1 (rdata0xa239e5c)
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The transaction involved in this state change is 0xb58bef9c
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The current transaction state is Completed
[Apr 22 10:56:21] VERBOSE[27818] res_pjsip_logger.c: <--- Received SIP request (373 bytes) from UDP:172.16.60.160:5080 --->
��ACK sip:172.16.60.160:5060;transport=UDP SIP/2.0^M
��Via: SIP/2.0/UDP 10.1.1.1:5060;branch=z9hG4bK-29027-1-4^M
��Max-Forwards: 60^M
��From: "Anonymous" <sip:anonymous at 192.168.225.2>;tag=1^M
��To: <sip:039988120 at 172.16.60.160:5060;user=phone>;tag=b2018fc9-735a-4f8d-9227-ee766b8dee81^M
��Call-ID: 1-29027 at 172.16.60.160^M
��Cseq: 1 ACK^M
��Content-Type: application/sdp^M
��User-Agent: Simulator^M
��^M
��
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The transaction state change event is TX_MSG
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The current inv state is CONNECTING
[Apr 22 10:56:21] DEBUG[27813] pjsip: sip_endpoint.c Distributing rdata to modules: Request msg ACK/cseq=1 (rdata0xa002a7c)
[Apr 22 10:56:21] DEBUG[27813] pjsip: dlg0xb4d80ae4 .Received Request msg ACK/cseq=1 (rdata0xa002a7c)
[Apr 22 10:56:21] DEBUG[27813] pjsip: tsx0xb58bef9c ..Request to terminate transaction
[Apr 22 10:56:21] DEBUG[27813] pjsip: tsx0xb58bef9c ...State changed from Completed to Terminated, event=USER
[Apr 22 10:56:21] DEBUG[27813] pjsip: dlg0xb4d80ae4 ....Transaction tsx0xb58bef9c state changed to Terminated
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: Function session_inv_on_tsx_state_changed called on event TSX_STATE
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The state change pertains to the session with sipp
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The inv session still has an invite_tsx (0xb58bef9c)
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The transaction involved in this state change is 0xb58bef9c
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The current transaction state is Terminated
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The transaction state change event is USER
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The current inv state is CONNECTING
[Apr 22 10:56:21] DEBUG[27813] pjsip: tdta0xb7dfee48 .....Destroying txdata Response msg 200/INVITE/cseq=1 (tdta0xb7dfee48)
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: Function session_inv_on_state_changed called on event RX_MSG
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The state change pertains to the session with sipp
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The inv session does NOT have an invite_tsx
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: There is no transaction involved in this state change
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: The current inv state is CONFIRMED
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: Received request
[Apr 22 10:56:21] DEBUG[27813] res_pjsip_session.c: Method is ACK
[Apr 22 10:56:21] DEBUG[27818] pjsip: tsx0xb58bef9c Timeout timer event kululu
[Apr 22 10:56:21] DEBUG[27818] pjsip: tsx0xb58bef9c .State changed from Terminated to Destroyed, event=TIMER
[Apr 22 10:56:21] DEBUG[27818] pjsip: tdta0xa009798 ..Destroying txdata Response msg 200/INVITE/cseq=1 (tdta0xa009798)
[Apr 22 10:56:21] DEBUG[27818] pjsip: tsx0xb58bef9c Transaction destroyed!
> Endpoint identification fails when user part of From header SIP-URI contains a tel URI style parameter
> ------------------------------------------------------------------------------------------------------
>
> 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
> Assignee: 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:
> {noformat}
> ##############################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
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list