Pri from xo 1

[punchtool]

Has anyone had issues with provisioning from xo on pri circuits.

 

[merlinman]

I had a problem that they were able to resolve with a LEADING ZERO, that is, they were sending me 4 digits, like 0123, 0124 and so on. And they had to do something special to fix it.

If that's your problem, I have this documented from them.

 

[punchtool]

My range does begin with zero. Information would be great.

 

[punchtool]

More info is that the circuit works but it drops every 1 to 1 1/2hrs for a second. If seen this before if it was not provisioned correctly, but they claim it is like all carriers like to say.

 

[merlinman]

Check to make sure that your "D" channel is not part of the POOL.

I'd be willing to bet that it is.

 

[punchtool]

Already checked not a member

 

[merlinman]

OK, first off, make sure you do not have a 517M15 DS1 card and any type of 016 modules.

Now, the info from XO on the leading zero stuff (Watered Down a bit):

"The DMS does not work very well with 4E and 5E protocol variants. A problem we have become aware of is generating a setup message with 0 being the leading digit in the called number. A way around this that I have found and tested in a lab environment is to manually adjust the TON (type of number) being sent with the called number. By creating a customized PRI profile to send the TON as “unknown” no digits will be removed by the peripheral the trunks are built on."[/color blue]

The above was sent to me by an XO engineer during the time we were having trouble.

He was able to implement fixes to his translations that took care of the problem.

Lot's 'O luck!

 

[punchtool]

Worked well thanks a lot