When configuring a T1 gateway using MGCP, we have the PRI configured as a PRI NI2. This is in preperation for exchanging caller name display from the carrier. In the meantime, according to the debug isdn q931, the vg200 is sending a full 10-digits to the telco, but the Telco is saying that they are only seeing 7 digits. This is causing a problem in that the customer wants to have as the calling id to be the extension of the phone that is making the call and not the main number. Telco says that if they do not see 10 digits, they only will send the main number. I have a troubleticket open with Telco, but I am wondering what the effects of changing the "Calling Party IE number type" and "Calling Numbering Plan"? I have looked high and low for an explaination of what these parameters do and have found nothing. Does anyone know? ... View more

Have a VG200 running 12.2.11T with MGCP talking to Call Manager 3.2.2c. Problem that I am seeing is that looking at debug isdn q931 I see that we are "sending" a 10digit calling number, but the Telco NOC is saying that they are only seeing the last 7 digits. On Call Manager, for the gateway we have all the defaults for the gateway line definition dial plan and type of "Call Manager". in the debig it is showing the type and number are Unknown. Is this what is causing the problem? What options would change this? Thanks. The following is a snippet from the debug: 5w2d: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x01DA Bearer Capability i = 0x8090A2 Standard = CCITT Transer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98397 Exclusive, Channel 23 Progress Ind i = 0x8083 - Origination address is non-ISDN Display i = 'Ralph Scorza' Calling Party Number i = 0x0080, '5188624766' Plan:Unknown, Type:Unknown Called Party Number i = 0xA1, '13153868561' Plan:ISDN, Type:National 5w2d: ISDN Se1/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x81DA Channel ID i = 0xA98397 Exclusive, Channel 23 5w2d: ISDN Se1/0:23 Q931: RX <- ALERTING pd = 8 callref = 0x81DA Progress Ind i = 0x8088 - In-band info or appropriate now available 5w2d: ISDN Se1/0:23 Q931: RX <- CONNECT pd = 8 callref = 0x81DA 5w2d: ISDN Se1/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x01DA ... View more

I have just installed all of the products in the ITEM release on a dedicated server and I am trying to add phones to be managed by VHM. I am running into a problem in that every time I try to add a phone that is registered in Call Manager 3.2.2c, I get a "Failed to create phone object" as the status. It does not seem to matter whether I use a seed file or try to add them one at a time. I have checked the snmp community strings and they seem to be fine. I have also installed the IP Phone Information add-on and it can see the CallManager and all of the phones just fine. Is there a trick that is not in the documentation? Or have I hit a bug? ... View more

I thought that I had read everything to get this working but I am at a stone wall. Have an existing 8850 with SMR-3CT3 card and AUSM-8 cards. The previous people had configured the first two T3 cards and they are all working fine. We are now starting into the thrid T3 and nothing is working. The example I am trying to get to work is Channel 16 on the T3.3, I want to cross to line card 11 line 8. At which point I want to take three ATM PVC's and send one to the first router card, the second to the second router card in the 8850, and the third to an outbound AUSM-8T card for voice to a 3810. Same as all of the rest. But it just does not seem to come up and the dspcons indicates that the connection FAILED. I have followed the cookbooks as far as I can, but I have not seen this specifically walked through. Any pointers will be greatly appreciated For what it is worth, we are running 1.1.32 on the PMX cards, but do not tell me to upgrade at this time. Telco indicates that the connection is coming in clean to the T3. ... View more

Customer has a problem in that the end user will miss a call. When they look at the missed call menu, it will show a 10 digit number. If the end user then wants to be able to just hit redial to call the person back. One concultant told them that the only way to make this work is to have a ton of route patterns to match the different area codes so as to then manipulate the number to prepend a 1 before forwarding it to the gateway. Will the following work instead. Build a route pattern of 10 x's that will then prepend the 1 and send it on its way. Any thoughts? Will it work and what is the down side? ... View more