Summary:	ASTERISK-13023: NAI not set correctly after small configuration changes
Reporter:	Nico Giefing (nicox)	Labels:
Date Opened:	2008-11-06 08:28:33.000-0600	Date Closed:	2009-03-17 16:19:06
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_dahdi
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) not_working_config.txt ( 1) working_config.txt
Description:	After i have changed on the second dahdi-group the channels, on the third group the NAI parameter was not set correctly on outgoing calls, after this changes, the NAI was always "0" and the leading "00" at the Callerid was sent to the carrier. ****** ADDITIONAL INFORMATION ****** i will attach the working config file and the "bad" config soon
Comments:	By: Leif Madsen (lmadsen) 2008-12-10 10:31:50.000-0600 Acknowledging this issue, and assigning to mattf since nicox mentioned this is related to SS7 functionality... ? By: Matthew Fredrickson (mattf) 2008-12-10 10:42:13.000-0600 Well, I don't see you setting the nai anywhere.  You're using the pridialplan field, which is wrong, since this is SS7.  There's a ss_calling_nai and ss7_called_nai variable when you're using SS7. By: Nico Giefing (nicox) 2008-12-10 10:53:42.000-0600 Okay, i didn't found a parameter like this in any documentation.. if thats the problem its great, but why is it working without these parameters set correctly, a small change and its not working anymore? thanks Nico By: Leif Madsen (lmadsen) 2009-02-02 13:40:02.000-0600 Ping? Just looking for an update here. By: Jason Parker (jparker) 2009-03-17 16:19:05 Closing, as this is a configuration issue as mattf pointed out. These variables are documented in chan_dahdi.conf.sample