[asterisk-bugs] [JIRA] (ASTERISK-26490) res_pjsip: Channel driver sometimes sends 481 Call/Transaction Does Not Exist
Juris Breicis (JIRA)
noreply at issues.asterisk.org
Thu Nov 3 03:14:10 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juris Breicis updated ASTERISK-26490:
-------------------------------------
Attachment: PJPROJECT-trace-03112016.txt
Attached is log who has 4 identically initiated and processed calls; 3 of them terminate as expected, but the last one raises 481 Call/Transaction Does not Exist.
The log includes extended debug output from bundled pjproject.
The pjsip configuration is the same as in original posting, except for different context name for these two trunks.
> res_pjsip: Channel driver sometimes sends 481 Call/Transaction Does Not Exist
> -----------------------------------------------------------------------------
>
> Key: ASTERISK-26490
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26490
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: pjproject/pjsip, Resources/res_pjsip
> Affects Versions: 13.11.2
> Environment: Linux 4.4.19-1-pve #1 SMP x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Juris Breicis
> Assignee: Unassigned
> Attachments: 2_mss_smex_capture.log.pcap, asterisk_log.txt, extensions.conf, extensions.conf, MSS_SIP_TRACE_ISSUES.txt, PJPROJECT-trace-03112016.txt, pjsip.conf
>
>
> In this particular setup asterisk 13.11.2 [10.40.6.100] is connected to NSN MSS through SIP trunk [212.210.2.2:5060]. The calls are received and routed back through the same trunk. Randomly the PJSIP will reply 481 Call/Transaction Does Not Exist to the trunk's CANCEL request of ongoing call in Ringing state. And sometimes (for no apparent reason) it just processes CANCEL request as expected.
> I have attached console dump with:
> core set debug 10
> core set verbose 10
> pjsip set logging on
> and corresponding sections of pjsip.conf and extensions.conf
> Please note although it looks like internal network 10.X.X.X is communicating through nat with public one 212.X.X.X - the routers are configured so, that this communication happens without NAT directly machine to machine.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list