Search results for query: *

We have a definity site networked with a legend via a pt to pt T1. The definity has a PRI provisioned from a local provider. Outside calls originating from the legend are routed over the pt to pt T1 to the definity onto the PRI. Outside calls originating from the definity are sending the...

ken1713 >I'm not sure if this will work but look in the legend >under lines/trunks, PRI, Number to send, and select >option from there. we did do this and have tried all of the options, still no luck.

franke, when calls are made from extensions on the legend to the extensions on the definity the persons name and 4 digit shows up on the display. Can i email you the 'pri' report so that you might see exactly how the t1 is configured. i did go back and look at the t1 configuration. it is setup...

We have a very similar setup and problem. Was there a solution to this?

franke, I just talked with our service provider. The point to point t1 is not an isdn pri. I don't know if that will make a difference. However, how would I go about check for digit manipulation of the legend.

I forgot to mention that the calls with extensions beginning with '54' or '55' originating from the Definity the appropriate number is being sent. However, calls from extensions beginning with '54' originating from the Legend are showing up with just the 4 digit extension.

Thanks for the response. We are sort of new at this. But, in isdn public-unkown-numbering we have entries for extensions that begin with '54', '55', etc. Originating calls from these extensions are sending out the appropriate number (CPN). Example appears below: Ext Ext Trk CPN...

We have networked a Definity and a Merlin Legend via a point to point PRI. Everything seems to be working fine. However, we are only getting the 4 digit extension being passed on outbound calls. This is causing some problems in that the calls from the Legend are showing up as unavailable or...