Long Distance Numbers being altered !?
Submitted by borillion_star on Fri, 12/05/2008 - 12:47pm.
I have a strange issue where long distance numbers are being altered to our area code :|
Ex.
I dial 185822033##
The Reports show that 185822033## was dialed
In reality the call was made locally :(
Im at a loss to explain whats happening.
Some how the area code is getting chopped of the number
obviously the calls go through but not to the right place.
Thanks for your help guys,
Bob
 
I'm running into the exact
Fri, 12/05/2008 - 2:16pm
I'm running into the exact same problem.
I most cases, every time I try to dial long distance, the number gets altered to my area code. Even more peculiar, there was one case where one number with a 212 area code would not work, but a different number with a 212 area code -did- work. There doesn't seem to be any rhyme or reason as to why it's happening. The only consistency seems to be that it changes long distance numbers to my area code.
Ex:
1 (402) 123-4567 gets dialed by me.
402-1234 is what actually gets dialed, even though the phone screen shows the first number as what gets dialed.
Nothing I do seems to correct this problem. I tried altering the "dial rules" in both the Trunks section and the Outbound Routes section. No effect.
Any help would be greatly appreciated!
-Geoffrey
 
Without seeing your dialing
Fri, 12/05/2008 - 5:11pm
Without seeing your dialing patterns its not possible to say what you have wrong. I seriously doubt this is a bug or everyone would have the same issue.
 
Dialing Patterns
Fri, 12/05/2008 - 7:51pm
How about including the Dialing Patterns for the potentially affected Trunks and Outbound Routes from (Free)PBX.
 
Here are mine since the
Thu, 12/18/2008 - 3:11pm
Here are mine since the other guy didnt include his:
311
411
911
011.
1800NXXXXXX
1866NXXXXXX
1877NXXXXXX
1888NXXXXXX
1NXXNXXXXXX
NXXNXXXXXX
NXXXXXX
 
If you are
Thu, 12/18/2008 - 10:38pm
If you are using analog trunk the try to put "w" in outbound prefix of the trunk section. It adds some delay because analog lines are not always ready...That should fix it..
Thanks
Nemo
 
Sorry for the delay, Here
Fri, 12/19/2008 - 12:23pm
Sorry for the delay, Here are mine as well.
011.
1800NXXXXXX
1866NXXXXXX
1877NXXXXXX
1888NXXXXXX
1NXXNXXXXXX
1XXXXXXXXXX
NXXNXXXXXX
NXXXXXX
I'm not sure if I'm using a digital or analog trunk. Right now we're using 'Trunk ZAP/g0'
-Geoffrey
 
Member Since:
2008-12-05