Hi - Thanks for the fast response!> Try changing your dial statment to use a group instead such as > Dial(Zap/g2/3055551212)Same result: Spawn extension (from-sip, 000, 1) exited non-zero on 'SIP/2000-8dca' -- Executing Dial("SIP/2000-a4f1", "Zap/g1/19142246402") in new stack Dec 14 22:11:09 NOTICE[1506]: app_dial.c:800 dial_exec: Unable to create channel of type 'Zap' (cause 0) == Everyone is busy/congested at this time -- Executing Congestion("SIP/2000-a4f1", "") in new stack == Spawn extension (from-sip, 19142246402, 2) exited non-zero on 'SIP/2000-a4f1'> Also what does the console diasplay when you dial into the asterisk > server.Nothing, even with extreme verbosity and pri debugging on.> What is the reslt of: > > pri show span 1pri 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 The "Status" has me concerned - "Provisioned, Down, Active". Is that "Down" normal? Thanks, Noah> > > Date: Tue, 14 Dec 2004 21:27:11 -0500 > From: Noah Miller <noah@rosecompanies.com> > Subject: - Only Busy and > Congestion > To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users@lists.digium.com> > Message-ID: <D366A001-4E40-11D9-B619-000393971C6E@rosecompanies.com> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi - > > We're moving up in the world to a PRI (Verizon), and I'm having some > problems with it. I'm new to this PRI thing, though, so maybe I've > just screwed up a simple config detail. I've got a TE410P on a Dell > PE1600SC (ServerWorks Chipset). The card itself has a green light for > the PRI, and Zttool shows Span1 as "OK". All I'm getting when I call > into any of the pri lines, though, is a slow busy. I can't see > anything from the asterisk end - it looks as though I'm not calling. > When I call out, I just get a fast busy congestion tone, and asterisk > says all the channels are busy: > > *CLI> pri debug span 1 > Enabled debugging on span 1 > -- Executing Dial("SIP/2000-28df", "Zap/2/19142246402") in new > stack Dec 14 21:01:52 NOTICE[1437]: app_dial.c:800 dial_exec: Unable > to create channel of type 'Zap' (cause 0) > == Everyone is busy/congested at this time > -- Executing Congestion("SIP/2000-28df", "") in new stack > == Spawn extension (from-sip, 19142246402, 2) exited non-zero on > 'SIP/2000-28df' > > Here are my configs for the TE410P: > zaptel.conf: > span=1,1,0,esf,b8zs > bchan=1-23 > dchan=24 > > zapata.conf: > switchtype = national > context = incoming > signalling = pri_cpe > group = 1 > channel => 1-23 > > Have I screwed up the config, or do I need to bug Verizon? > > Thanks, > Noah >
Noah Miller wrote:> The "Status" has me concerned - "Provisioned, Down, Active". Is that > "Down" normal?Sounds like Verizon has not turned up your PRI yet, even though the loop is up. They have to tell their switch to actually start talking to yours :-)
> > pri show span 1 > > pri show span 1 > Primary D-channel: 24 > Status: Provisioned, Down, ActiveThe "Down" indicates the d-chan is down. Call Verizon and have them activate it. (Its not uncommon for telco's to deactivate the d-chan when a circuit hasn't been fully turned up. It reduces the number of alarms they have to deal with.)> zapata.conf: > switchtype = national > context = incoming > signalling = pri_cpe > group = 1 > channel => 1-23In the above for US-based PRI's, you'll want to add: pridialplan=unknown echocancel=yes echotraining=yes ; try =800 if there is still echo with =yes echocancelwhenbridged=yes The pridialplan= statement essentially tells the Verizon switch what type of dialplan you expect to use. 'unknown' allows you to send 7 digits, 1+ 10 digits, etc. 'national' restricts international long distance, while 'international' imposes other restrictions. The added zapata.conf parameters are not the cause for your d-chan being down, however after that issue is resolved you'll bump into these parameters. After the above items are resolved and things are closer to working, you'll need to know how many digits (if any) Verizon is going to be sending to you for inbound calls. If you asked them to provide DID numbers, then the number of digits received will become important for you to define extensions.conf entries associated with your context=incoming statement above. If they send you 4 digits, then use extension.conf test entries like: [incoming] include => valid-did include => invalid-did [valid-did] exten => 1234,1,Goto(local-extns,1234,1) exten => 1235,1,Goto(local-extns,1235,1) [invalid-did] exten => _.,1,Answer exten => _.,2,Wait(1) exten => _.,3,Playback(the-number-u-dialed) exten => _.,4,Playback(not-yet-assigned) exten => _.,5,Wait(2) exten => _.,6,Hangup If Verizon is not sending any digits to you on inbound calls, then for testing simply use something like: [incoming] exten => s,1,Wait(1) exten => s,2,Answer exten => s,3,whatever-you-want-to-do-with-this-call You will also want to talk to a Verizon switch tech about how to handle outbound CallerID. E.g., do you want to send CallerIDNum to Verizon matching each originating DID number, or, map all outbound calls to a single CallerIDNum? They will also set a common CallerIDName for all outbound calls, but probably won't allow you to send the name to them. Rich
> > > pri show span 1 > > > > pri show span 1 > > Primary D-channel: 24 > > Status: Provisioned, Down, Active > > The "Down" indicates the d-chan is down. Call Verizon and have them > activate it. (Its not uncommon for telco's to deactivate the d-chan > when a circuit hasn't been fully turned up. It reduces the number of > alarms they have to deal with.)Aha! That would make sense. We ordered the PRI a while back for a new office space, but construction was delayed, and it has been sitting idle for more than a month.> > zapata.conf: > > switchtype = national > > context = incoming > > signalling = pri_cpe > > group = 1 > > channel => 1-23 > > In the above for US-based PRI's, you'll want to add: > pridialplan=unknown > echocancel=yes > echotraining=yes ; try =800 if there is still echo with =yes > echocancelwhenbridged=yes > > The pridialplan= statement essentially tells the Verizon switch > what type of dialplan you expect to use. 'unknown' allows you to > send 7 digits, 1+ 10 digits, etc. 'national' restricts international > long distance, while 'international' imposes other restrictions. > The added zapata.conf parameters are not the cause for your d-chan > being down, however after that issue is resolved you'll bump into > these parameters. > > After the above items are resolved and things are closer to working, > you'll need to know how many digits (if any) Verizon is going to be > sending to you for inbound calls. If you asked them to provide DID > numbers, then the number of digits received will become important > for you to define extensions.conf entries associated with your > context=incoming statement above. If they send you 4 digits, then > use extension.conf test entries like: > [incoming] > include => valid-did > include => invalid-did > > [valid-did] > exten => 1234,1,Goto(local-extns,1234,1) > exten => 1235,1,Goto(local-extns,1235,1) > > [invalid-did] > exten => _.,1,Answer > exten => _.,2,Wait(1) > exten => _.,3,Playback(the-number-u-dialed) > exten => _.,4,Playback(not-yet-assigned) > exten => _.,5,Wait(2) > exten => _.,6,Hangup > > You will also want to talk to a Verizon switch tech about how to > handle outbound CallerID. E.g., do you want to send CallerIDNum to > Verizon matching each originating DID number, or, map all outbound > calls to a single CallerIDNum? They will also set a common > CallerIDName for all outbound calls, but probably won't allow you > to send the name to them.Wow, a wealth of information! Thanks, Rich, for all the dialplan and echo cancel stuff. I certainly would not have thought to cover invalid DID'd or outbound CallerID! This will save me a GREAT deal of time (which is suddenly a huge premium for me). Thanks, Noah -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20041215/bf64d0fd/attachment.htm
Hello, Any chance of development team make more drings?I googled and found out that only 3 drings can be configured.I have at least 6 different rings in my lines.In my setup is a good feature since I can know whos coming from the world and whos coming from inside the PBX,without having to separate my zap channels in groups. Thanks
Rafael Pazetto wrote:>Hello, > >Any chance of development team make more drings?I googled and found out >that only 3 drings can be configured.I have at least 6 different rings >in my lines.In my setup is a good feature since I can know whos coming >from the world and whos coming from inside the PBX,without having to >separate my zap channels in groups. > >Thanks > >Maybe we could ring the caller ID in Morse code :-) Steve
Hahaha in no way caller id works here,the feed simply gives me an Input/Output Error. Was the question THAT stupid? Tnx anyway On Wed, 2004-12-15 at 13:30, Steve Underwood wrote:> Rafael Pazetto wrote: > > >Hello, > > > >Any chance of development team make more drings?I googled and found out > >that only 3 drings can be configured.I have at least 6 different rings > >in my lines.In my setup is a good feature since I can know whos coming > >from the world and whos coming from inside the PBX,without having to > >separate my zap channels in groups. > > > >Thanks > > > > > Maybe we could ring the caller ID in Morse code :-) > > Steve > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
> >Any chance of development team make more drings?I googled and found out > >that only 3 drings can be configured.I have at least 6 different rings > >in my lines.In my setup is a good feature since I can know whos coming > >from the world and whos coming from inside the PBX,without having to > >separate my zap channels in groups. > > > >Thanks > > > > > Maybe we could ring the caller ID in Morse code :-) >- .... .- -. -.- ... (You knew someone would have to do it. :) Rich
... --- .-. .-. -.-- 0_o On Wed, 2004-12-15 at 14:16, Rich Adamson wrote:> > >Any chance of development team make more drings?I googled and found out > > >that only 3 drings can be configured.I have at least 6 different rings > > >in my lines.In my setup is a good feature since I can know whos coming > > >from the world and whos coming from inside the PBX,without having to > > >separate my zap channels in groups. > > > > > >Thanks > > > > > > > > Maybe we could ring the caller ID in Morse code :-) > > > > - .... .- -. -.- ... > > (You knew someone would have to do it. :) > > Rich > > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users