[asterisk-bugs] [Asterisk 0016753]: IAX2 Reject Not Shown in Debug

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16753 
====================================================================== 
Reported By:                leobrown
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16753
Category:                   Channels/chan_iax2
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-02 12:25 CST
Last Modified:              2010-02-02 15:08 CST
====================================================================== 
Summary:                    IAX2 Reject Not Shown in Debug
Description: 
Hi,

There's an issue I'm seeing whereby a system who has user, peer, and
register with a remote system is REJECTing inbound calls though they are
properly matched in the dialplan.

Although I have not found a reason for the reject, I think the bigger
issue is perhaps that Asterisk seems to be unaware itself of sending the
REJECT message. The system originating the call with `iax set debug on`
shows the REJECT message coming, but the client machine only sees the NEW
and ACK messages. I have verified using packet analysers that the packets
on the receiving system are shown as HANGUP, NEW, REJECT, ACK, HANGUP,
where the REJECT is the only packet it is sending, and the others are from
the originating side.

Also strange that it believes it is sending a retry packet, when `tcpdump`
again shows that this is not the case, and the time taken does not
necessarily indicate retry.

My testing been in the last two hours using /branches/1.6.2 and
tags/1.6.2.1-rc1, which both exhibit the same issue.

Cheers,
Leo
====================================================================== 

---------------------------------------------------------------------- 
 (0117564) lmadsen (administrator) - 2010-02-02 15:08
 https://issues.asterisk.org/view.php?id=16753#c117564 
---------------------------------------------------------------------- 
This could be a configuration problem to do with the rejectcalltoken setup,
but if this REJECT is happening and is the cause of the issue, then there
likely should be some sort of WARNING message that pops up. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-02 15:08 lmadsen        Note Added: 0117564                          
2010-02-02 15:08 lmadsen        Status                   new => feedback     
======================================================================