atcomsystems.ca/forum
Posted By: jc2it Replacing POTS lines with Grandstream + SIP - 12/08/23 11:44 PM
We have replaced our five POTS lines in a hunt group with a connection to a Grandstream with SIP trunks. It works much of the time.

One of the issues is when we dial 9 to get the next available outside line in the Hunt group and then dial the 10 digit number or 11 digit number if it is long distance, it gives a recorded error "Please Try Again". When we reported this to the Grandstream technician they said it sends a '101' to the Grandstream instead of the 10 or 11 digit number.

Why? How do I troubleshoot this? What would a '101' mean to a POTS line in a hunt group?

Thanks!
Posted By: C5Z Re: Replacing POTS lines with Grandstream + SIP - 12/09/23 01:17 PM
Of course I would test this at the Grandstream with just a butt set to rule out the phone system.
Do you have 5 call paths available on the SIP account?
The only thing the Toshiba sends on an analog line is the DTMF tones for the dialed phone number. If you are using a 9, that means that the Toshiba will wait for you to dial before it will try to seize the line and send the DTMF tones for the dialed phone number.

Do you have direct access to the lines? Maybe you can try dialing directly without LCR. If you don't have line keys on the phones then just use the code #7001 for line 1. You could have something in the digit modifications that could be adding numbers. Maybe they used to use 10-10 code for long-distance dialing or something on the old POTS. If you bypass LCR then the PBX won't modify the dialing digits. If you can call using the #7001 code but not LCR (9), then I bet you have an issue with dialing digit modifications

As mentioned, if I was there, or another telephone tech, I would try dialing from my own butt set, or listen in on the line to make sure the PBX is sending out the correct number of digits.
Thanks for the tips guys! I will try to get onsite later this week and look at this.
Originally Posted by newtecky
Maybe you can try dialing directly without LCR.

Well that was the culprit. Someone had enabled LCR to dial 1010802 before any call that we dialed '9'. Disabling it worked. The '101' that the Grandstream engineer was seeing is what was throwing me. My guess is 1010802 is a long distance provider of some kind.
Originally Posted by jc2it
My guess is 1010802 is a long distance provider of some kind.
The code assignment 0802 belongs to Electric Lightwave.
That would make sense they were our carrier at most locations for a long time. Thanks!
That would also mean that the Grandstream doesn't honor a 1010802 to force the routing of the call over a specific long distance carrier. Doesn't that seem odd?

Its fixed now but why wouldn't you just drop all PIC codes instead of generate an error?
Originally Posted by jc2it
That would also mean that the Grandstream doesn't honor a 1010802 to force the routing of the call over a specific long distance carrier. Doesn't that seem odd?

Its fixed now but why wouldn't you just drop all PIC codes instead of generate an error?

It is hard to say, but likely they didn't account for 10-10 codes in the dialing plan. My Yealink phone used to send 11 when I tried to dial any extension that started with 11 (ie.. ext 112). The dial plan didn't account for anything starting with 11.
© Sundance Business VOIP Telephone Help