In the process of turning up a new pri. Zttool indicates the T1 is ready with no alarms. asterisk*CLI> pri show span 1 Primary D-channel: 24 Status: Provisioned, Down, Active Switchtype: National ISDN Type: CPE Window Length: 0/7 Sentrej: 0 SolicitFbit: 0 Retrans: 0 Busy: 0 Overlap Dial: 0 T200 Timer: 1000 T203 Timer: 10000 T305 Timer: 30000 T308 Timer: 4000 T313 Timer: 4000 N200 Counter: 3 What does the "Down" mean in the above status line?
On December 8, 2004 10:56 am, Rich Adamson wrote:> Status: Provisioned, Down, Active> What does the "Down" mean in the above status line?It means that your D channel isn't up, this is normal if * isn't running (or the telco hasn't turned up the D channel yet) -A.
< Cause (len= 5) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: User (0) < Ext: 1 Cause: Info. element nonexist or not implemented (99), class = Looks like the switch on the telco end might be confused about the number pattern; try adding: pridialplan=unknown to zapata.conf in your channel definition, this can cause the switch to do a brute force match of the number pattern. Also try dialing local first, if that works then it is definitely because the telco is not liking what Asterisk is presenting to it for a number pattern. hth
>I don't really understand why do many people set their pridialplan. The >text "PRI Dialplan: Only RARELY used for PRI." in zapata.conf.sample is >not there to just take up space in the file.Some telco's do, some telco's don't. The text "Rarely used for PRI" is IMO a location-centric and carrier-centric statement. As another poster suggested, PRI's are picky, and some carriers are super-picky so it's always best to dot your i's and cross your t's when dealing with PRI. At worst, it will be ignored by the switch.
>Is there something different that I "should" be dialing?On my pri, I have dialplan=national. It is from Allstream/AT&T co-lo with Telus which pretty much behaves the same as most US carriers. We don't dial international, so it's not an issue for us. If I dial XXX-XXX-XXXX with local area code, the call proceeds. If I dial XXX-XXX-XXXX with non-local area code I get "This is a long distance number...". If I dial 1-XXX-XXX-XXXX the call proceeds. This is all expected behavior. Here's a PRI debug dialing LD with a 1:> Called Number (len=14) [ Ext: 1 TON: National Number (2) NPI:ISDN/Telephony Numbering Plan (E.164/E.163) (1) '1XXXXXXXXXX' ] <--number deleted to protect the innocent -- Called g0/1XXXXXXXXXX <--number deleted to protect the innocent < Protocol Discriminator: Q.931 (8) len=10 < Call Ref: len= 2 (reference 32786/0x8012) (Terminator) < Message type: CALL PROCEEDING (2) So this works as expected for me. In your case, you are probably going to have to get your telco involved and explain the situation that you want to pass the LD dial string as 1-XXX-XXX-XXXX and see if they will allow that; it should be a software change on their end. hth