Summary:ASTERISK-08463: IAX2 configuration parser reverses general and specific parameters when loading users
Reporter:Steven Sokol (ssokol)Labels:
Date Opened:2007-01-01 11:49:42.000-0600Date Closed:2011-06-07 14:08:21
Versions:Frequency of
Environment:Attachments:( 0) chan_iax2.c.patch
Description:When the IAX2 configuration parser loads the users.conf file it pulls a portion of the configuration from the individual user definitions and the remainder from the general section.  In the current version it reverses the parameter when calling both build_user and build_peer, passing the general as the primary and the user-specific config as the alt.

The patch included below fixes this.
Comments:By: Steven Sokol (ssokol) 2007-01-01 21:53:15.000-0600

Please close this out.  Some kind of a short between the keyboard and the chair....

It appears that the order in which the parameters is passed is correct.  The only issue with this: since IAX2 supports multiple contexts, if both the template (general) and the user contain a context, the context value from general becomes the "default context" and the user specific context must be requested by name in the dialstring.

Sorry for the confusion.