Inbound\Outbound PRI Rejected

[ithelpdeskthane]

Hello Everyone,

We are using VG2921 HA gateway. Since past few days, one of a PRI is been reflected as rejected in CUCM(10.5). Service Provider is saying that there is nothing wrong from their end .We reinserted the cable to  the port then too  it is amber in colour.

When took the console of VG through putty & executed the command #show isdn status then layer one is showing Deactivated & layer 2 is showing TEI_Assigned for the port on which that PRI is terminated.

Please Help.

Regards,

Vimal

[Deepak Mehta]

Hi Vimal,

I can tell you service provider does say this most of the times and in the end it turns out be their end. Few things you can check..

Make sure from the demarc to VG GW if there are patch panels et you check each end properly. 

You can loop the pri port and ask service provider if they see that on their end. 

Also TX / RX mismatch at provider end can also cause this.

[Ritesh Desai]

ithelpdeskthane,

deepak mehta suggested is also right. most of the times SP says the same.

But confirm how much old PRI is, if more than 7-8years old then from SP end they need to make PRI as E1. In Asia we support E1 signalling. If you have spare PRI which is not so older then insert the new PRI in configured port. Check the isdn status then. I came with similar scenario. PRI was much older when techical guy disclosed PRI was older 7-8 years.

Make sure the E1 configuration is correct.

Change the e1 ISDN switch type as primary-qsig

regards,

Ritesh Desai

rate helpfull posts.

[Deepak Rawat]

layer one is showing Deactivated

This means there is some physical connectivity issues, check the cable maybe try replacing it. T1/EI Port as well where the cable is connecting, make sure it is not faulty.

Regards

Deepak

[Bill Mungaven]

As Deepak Rawat stated, this sounds like a layer 1 problem. If possible, can you swap a known working PRI into the port to see if the circuit comes up (multiframe established)? If the port comes up, the VG hardware is good. If the rejected circuit is moved to the known working port and stays down (TEI assigned), the problem is from the connector back to the provider. This still points to a possible layer 1 issue. It's possible the circuit from the provider could be fine up to the network interface unit (NIU) on the customer premise side (their side of the circuit) with the problem being from the NIU to the VG (layer 1). I've run into this more than once. The provider can loop up the circuit fine but the problem was in the cabling from the NIU to the router.

If a known working circuit is plugged into the rejected VG port and stays down, the port or its configuration could be the problem.

This link has some useful information on T1/E1 testing with loopbacks: http://www.cisco.com/c/en/us/support/docs/voice/device-signaling/116492-trouble-t1e1-00.html

Bill