There are two VG200 Media Gateway Control Protocol (MGCP) gateways with two different Cisco IOS Software versions. One VG200 works fine, the other does not. The Cisco CallManager is 3.3.2 spH, with Public Switched Telephone Network (PSTN) connections through Foreign Exchange Station (FXS) ports on the VG200 series.
When dialing a route pattern through the non-functional VG200, the failure is dead air. Adding a number sign (#) at the end of the dialing string to eliminate interdigit timeout has no effect.
To eliminate the Cisco IOS Software version issues, the non-functional VG200 is changed to the same version of code as the functional VG200. However, this has no effect. Every route pattern fails with dead air and no feedback is given.
Cisco CallManager traces show that the route patterns do not match and are presented to the gateway. The gateway receives the MGCP packets and processes them.
This situation is caused by bad hardware, specifically a bad connection in the PSTN block. There is no problem with either VG200 in operation or configuration.
For more information about the MGCP gateway, refer to these documents:
I'd like to figure out if it's possible to get CER to acknowledge the existence of a VG320 as an analog phone. In our environment we have alarms and dialers that rely on analog lines provided by gateways that call 911. The problem is that because all emer...
From CSR compatibility matrix I do not see ATA 186 since version 10.5, but I understand is supported on ver 10,x 11.1 & 12.0.My question is ATA 186 is supported on CUCM ver 12.5?If so, do you have a link to validate it? Thanks in advancedEnrique
I have a UCCE v12.5 environment and am looking at the Call_Type_Interval table (CTI) trying to understand some of the fields that customer is reporting on.A question was raised as to why the "CallsOfferred" field doesn't match (or is lower) than the "Rout...