Long distance problem!

[chipig]

Hi,

We have a long distance problem with one of our phones.
If we try to dial a long distance, it rings a couple of time and stop.

Any ideas what it could be.
I know that this phone has a different class of service but I don't see where the problem is.

 

[chipig]

I'm not using LCR.Look:

200>A126:NONE-
200>A127:NONE-
200>A128:NONE-
200>A129:NONE-

The ringback problem is only happening with long distance done to one particular carrier which provides IP phones.

My carrier do not know what the problem is.
I have contacted the destination carrier.
I'll post back when I find the problem.

 

[pingram3541]

The numbering plan lookup is backwards...

try 200>9:???

if it is A126-A129 you are using LCR tables. Then test using direct trunk access.

You can assign a direct access code...

200>A110:110 (110 = route 10)

(where the access code is *110 to access route 10 or whatever your PRI route is)

Then test the route bypassing LCR by dialing *110+number directly. This will ensure that LCR isn't doing anything to the dialing string that is sent to the d-channel.


-Phil Ingram

http://www.tell-a-tek.com/

{All-You-Can-Eat Telecom and IT Buffet}

 

[chipig]

Oh, sorry about that...I've should have looked more carefully.I guess I use LCR after all.

thanx a lot for your help, it's great.

Ok, so I just tested it and I still have the same problem.
I've dialed the long distance number directly after getting the direct trunk access.

200>9:A126-
200>A114:114-

Is there anything else I can test besides LCR?

 

[pingram3541]

Ok, let's look at what we have narrowed down.

1 - The issue does not happen on other trunk card/types in the same phone system - i.e. 4COT card w/ analog pots line

2 - The problem only happens to certain LD numbers, not all, but the same results with those numbers

3 - The problem only happens on the PRI circuit

4 - The problem happens regardless of LCR patterns - eliminates lcr programming

Taking all this into consideration, this is starting to not even sound PRI related but more like carrier translations.

Does the problem occur always on the same numbers? Meaning is it wishy/washy or does it happen every time on particular numbers that do this?

What area codes are they? Is it always the same area code(s)?

Is the pots line carrier the same as the PRI carrier?

Can the carrier send a tech and place these calls from the building dmarc using a tester unit and see if the ringback problem persists? If so, they need to address it and this proves its not your pbx.

-Phil Ingram

http://www.tell-a-tek.com/

{All-You-Can-Eat Telecom and IT Buffet}

 

[chipig]

Yes, we did pretty much all we can do from our side.

To answer your questions:

Does the problem occur always on the same numbers? Yes,

I have found more phone numbers with this problem and they all belong to the same carrier. I know because a lot of these numbers are relative’s.

What area codes are they? Is it always the same area code(s)? Yes,

It's always the same area code which is 418.

Is the pots line carrier the same as the PRI carrier? Yes

We have one carrier for all our lines.

I have contacted our carrier and the destination carrier.
I'm waiting for a response from the destination carrier because our carrier don't think there is anything wrong with the lines.

I hope they come up with something because I'm drawing blank.

 

[pingram3541]

Ok, just remember that if you can get the carrier tech to try dialing a 418 number from the circuit DMARC using a tester and they have the same ringback issue, they should be obligated to figure out what the problem is.

-Phil Ingram

http://www.tell-a-tek.com/

{All-You-Can-Eat Telecom and IT Buffet}