Mark Engelhardt
2007-Feb-28 17:14 UTC
[asterisk-users] Help Needed: Can't make "local" calls on a brand new PRI
Hello,
I just installed a PRI and when I make a local (seven digit) call, I
get Code 28 back from the telco, (I believe code 28 means "Invalid
Number") and I hear a fast busy on the phone.
Here is the output:
-- Executing Dial("SIP/marke-17b1", "ZAP/G1/4967171")
in new stack
-- Requested transfer capability: 0x00 - SPEECH
-- Called G1/4967171
-- Zap/23-1 is proceeding passing it to SIP/marke-17b1
-- PROGRESS with cause code 28 received
-- Zap/23-1 is making progress passing it to SIP/marke-17b1
As you can see, asterisk is reporting 4967171 as the dialed number
(which is valid)
When I dial long distance, everything works fine.
Here is the output from long distance...
-- Executing Set("SIP/marke-80f8", "CALLERID(all)=Small Dog
Electronics<8005116277>") in new stack
-- Executing Dial("SIP/marke-80f8",
"ZAP/G1/17077510895") in new
stack
-- Requested transfer capability: 0x00 - SPEECH
-- Called G1/17077510895
-- Zap/23-1 is proceeding passing it to SIP/marke-80f8
-- Zap/23-1 is ringing
If I just send the full 18024967171 to the telco, I get a voice from
the telco saying it is not necessary to dial 1 or the area code when
calling this number.
So the questions: Is there anyway to further verify that asterisk is
not sending any extra digits or filler digits to the telco on the PRI?
If the problem is not in asterisk or zaptel, what do I say to the
Telco to get them to believe the problem is on their end?
We are running:
Asterisk 1.2.6
Zaptel 1.2.14
TE110P Card
Mark Engelhardt
Zack Odell
2007-Feb-28 17:29 UTC
[asterisk-users] Help Needed: Can't make "local" calls on a brandnew PRI
On Wed, 28 Feb 2007 19:13:55 -0500, Mark Engelhardt <marke@intuitiveengineering.com> wrote:> Hello, > > I just installed a PRI and when I make a local (seven digit) call, I > get Code 28 back from the telco, (I believe code 28 means "Invalid > Number") and I hear a fast busy on the phone. > > Here is the output: > -- Executing Dial("SIP/marke-17b1", "ZAP/G1/4967171") in new stack > -- Requested transfer capability: 0x00 - SPEECH > -- Called G1/4967171 > -- Zap/23-1 is proceeding passing it to SIP/marke-17b1 > -- PROGRESS with cause code 28 received > -- Zap/23-1 is making progress passing it to SIP/marke-17b1 > > As you can see, asterisk is reporting 4967171 as the dialed number > (which is valid) > > When I dial long distance, everything works fine. > > Here is the output from long distance... > > -- Executing Set("SIP/marke-80f8", "CALLERID(all)=Small Dog > Electronics<8005116277>") in new stack > -- Executing Dial("SIP/marke-80f8", "ZAP/G1/17077510895") in new > stack > -- Requested transfer capability: 0x00 - SPEECH > -- Called G1/17077510895 > -- Zap/23-1 is proceeding passing it to SIP/marke-80f8 > -- Zap/23-1 is ringing > > If I just send the full 18024967171 to the telco, I get a voice from > the telco saying it is not necessary to dial 1 or the area code when > calling this number. > > So the questions: Is there anyway to further verify that asterisk is > not sending any extra digits or filler digits to the telco on the PRI? > If the problem is not in asterisk or zaptel, what do I say to the > Telco to get them to believe the problem is on their end? > > We are running: > Asterisk 1.2.6 > Zaptel 1.2.14 > TE110P Card > > Mark Engelhardt > > > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-usersWhat are the contents of extensions.conf?
Nic Bellamy
2007-Feb-28 17:51 UTC
[asterisk-users] Help Needed: Can't make "local" calls on a brand new PRI
Mark Engelhardt wrote:> I just installed a PRI and when I make a local (seven digit) call, I > get Code 28 back from the telco, (I believe code 28 means "Invalid > Number") and I hear a fast busy on the phone. > > Here is the output: > -- Executing Dial("SIP/marke-17b1", "ZAP/G1/4967171") in new stack > -- Requested transfer capability: 0x00 - SPEECH > -- Called G1/4967171 > -- Zap/23-1 is proceeding passing it to SIP/marke-17b1 > -- PROGRESS with cause code 28 received > -- Zap/23-1 is making progress passing it to SIP/marke-17b1 > > As you can see, asterisk is reporting 4967171 as the dialed number > (which is valid)Cause code 28 means "Invalid Number Format", and, if you're sure the number is correct, is often a case of you sending the wrong Type Of Number (TON) when setting up the call. Take a look at your pridialplan setting in zapata.conf - try "unknown" first, then other options until you find what works. A very very handy list I keep close to hand: http://www.quintum.com/support/xplatform/network/Q931_Disconnect_Cause_Code_List.pdf Cheers, Nic. -- Nic Bellamy, Head Of Engineering, Vadacom Ltd - http://www.vadacom.co.nz/
Alejandro Kauffmann
2007-Feb-28 18:57 UTC
[asterisk-users] Help Needed: Can't make "local" calls on abrandnewPRI
> > So the questions: Is there anyway to further verify that > asterisk is > not sending any extra digits or filler digits to the telco on > the PRI? If the problem is not in asterisk or zaptel, what do > I say to the > Telco to get them to believe the problem is on their end? >At the console type pri intense debug span 1 (or whatever your span number is) then place the call and check the output. Play with the pridialplan parameter in zapata.conf. The default is national, try unknown first. Once you're done, pri no debug span 1 to turn debugging off.
Andrew Latham
2007-Mar-02 07:14 UTC
[asterisk-users] Help Needed: Can't make "local" calls on a brand new PRI
Telco Switching could be waiting for a ten digit number. I know that Sprint and some others expect ten digit local calls.... On 2/28/07, Mark Engelhardt <marke@intuitiveengineering.com> wrote:> Hello, > > I just installed a PRI and when I make a local (seven digit) call, I > get Code 28 back from the telco, (I believe code 28 means "Invalid > Number") and I hear a fast busy on the phone. > > Here is the output: > -- Executing Dial("SIP/marke-17b1", "ZAP/G1/4967171") in new stack > -- Requested transfer capability: 0x00 - SPEECH > -- Called G1/4967171 > -- Zap/23-1 is proceeding passing it to SIP/marke-17b1 > -- PROGRESS with cause code 28 received > -- Zap/23-1 is making progress passing it to SIP/marke-17b1 > > As you can see, asterisk is reporting 4967171 as the dialed number > (which is valid) > > When I dial long distance, everything works fine. > > Here is the output from long distance... > > -- Executing Set("SIP/marke-80f8", "CALLERID(all)=Small Dog > Electronics<8005116277>") in new stack > -- Executing Dial("SIP/marke-80f8", "ZAP/G1/17077510895") in new > stack > -- Requested transfer capability: 0x00 - SPEECH > -- Called G1/17077510895 > -- Zap/23-1 is proceeding passing it to SIP/marke-80f8 > -- Zap/23-1 is ringing > > If I just send the full 18024967171 to the telco, I get a voice from > the telco saying it is not necessary to dial 1 or the area code when > calling this number. > > So the questions: Is there anyway to further verify that asterisk is > not sending any extra digits or filler digits to the telco on the PRI? > If the problem is not in asterisk or zaptel, what do I say to the > Telco to get them to believe the problem is on their end? > > We are running: > Asterisk 1.2.6 > Zaptel 1.2.14 > TE110P Card > > Mark Engelhardt > > > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- --- Andrew Latham - AKA: LATHAMA (lay-th-ham-eh) lathama@lathama.com - lathama@gmail.com If any of the above are down we have bigger problems than my email! Hind sight is most always 20/20 or better. ---