[asterisk-bugs] [Asterisk 0016159]: Calltoken and Realtime

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16159 
====================================================================== 
Reported By:                thom4fun
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16159
Category:                   Channels/chan_iax2
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.8 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-31 05:51 CDT
Last Modified:              2009-11-05 09:35 CST
====================================================================== 
Summary:                    Calltoken and Realtime
Description: 
We update to 1.6.1.8

The option 
calltokenoptional=0.0.0.0/0.0.0.0 
is running fine in flat file but will be ignored in realtime static.

The option 
requirecalltoken=no
in Realtime dynamic is running fine for register the iax client but make a
call
will be rejected, because calltoken is required.

Are there any way to get the old client to work where the IAX.Conf is
stored in realtime static and the clients are stored in Realtime dynamic?

regards
Thomas
====================================================================== 

---------------------------------------------------------------------- 
 (0113194) lmadsen (administrator) - 2009-11-05 09:35
 https://issues.asterisk.org/view.php?id=16159#c113194 
---------------------------------------------------------------------- 
The only work around I can see is going back to 1.6.1.6 where you say
you're not experiencing the issue. I don't see how the security fix that is
in 1.6.1.8 could actually cause this though... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-05 09:35 lmadsen        Note Added: 0113194                          
======================================================================