Summary:	ASTERISK-14552: chan_dahdi parser assigns channel 1 to wrong context
Reporter:	Karl Fife (karlfife)	Labels:
Date Opened:	2009-07-28 17:54:30	Date Closed:	2011-06-07 14:07:23
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_dahdi
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Based on the config below, Channels 1-23 are properly assigned to the context inbound-pri, and Channels 25-47 are assigned to the context outbound-pri. As expected. [trunkgroups] ; We do not do NFAS at this time [channels] echocancel = yes switchtype = national context = outbound-pri signalling = pri_net group = 2 channel => 25-47 context = inbound-pri signalling = pri_cpe group = 1 channel => 1-23 HOWEVER when I simply reverse the order of the channels on the last few lines like so: [trunkgroups] ; We do not do NFAS at this time [channels] echocancel = yes switchtype = national ;This A part (4 lines) was swapped with the B part context = inbound-pri signalling = pri_cpe group = 1 channel => 1-23 ;This B part (4 lines) was swapped with the A part context = outbound-pri signalling = pri_net group = 2 channel => 25-47 UNEXPECTED: Channels 1 is unexpectedly assigned to the context outbound-pri Channels 2-23 are 'properly' assigned to the context inbound-pri Channels 25-47 are 'properly' assigned to the context outbound-pri This is not a dahdi reload problem.  Even a complete system reboot returns these results ****** ADDITIONAL INFORMATION ****** Reproduced problem as follows: Reversed order of channel parameters as noted in description >unload chan_dandi.so >load chan_dandi.so dahdi show channels pseudo            outbound-pri  ...      1            outbound-pri  ...      2            inbound-pri   ...      3            inbound-pri   ...      4            inbound-pri   ... REVERTED to original order of channel parameters as noted in description >unload chan_dandi.so >load chan_dandi.so dahdi show channels pseudo            inbound-pri  ...      1            inbound-pri  ...      2            inbound-pri  ...      3            inbound-pri  ...      4            inbound-pri  ... ...
Comments:	By: Jason Parker (jparker) 2009-07-31 15:43:36 Hmm..  Do you by chance have a users.conf that might be specifying channel 1?  Also, what version(s) of Asterisk does this happen with? By: Karl Fife (karlfife) 2009-08-25 18:52:06 Indeed. I removed the parameter dahdichan=1 from the users.conf.  Afterward the configuration was no longer dependent upon the order as outlined in the original description.   The paramter made its way into users.conf by way of the examples in the users.conf sample file.  Should I conclude from your observation that this is not a defect?  I'm fairly new to Zap/Dahdi.   The Asterisk version is 1.6.0.13, Dahdi 2.2.0.2.   Thanks By: Jason Parker (jparker) 2009-08-26 13:23:28 I don't think there's anything we need to do here.  For this to have happened, the example would have had to have been uncommented by the user.