Can call outbound, but not inbound.

chmorin · October 2010

I am configuring my first production gateway from scratch. Until now I had not ever experienced an actual PSTN connection. I'm running into an issue I know I should be able to fix... but I'm going to go ahead and make a dummy out of myself and look for advice.

Basically I configured the gateway for MGCP and got the PRI D-Channel up, and one of the numbers in the DID range (that we are testing with) can make calls outbound. However, it can not receive calls inbound.

This is for local AND PSTN calls. Both of which are different problems (I think).

The local one is the one I'm punching myself in the face for, I should know why it can't route the calls. As of right now, it looks like the CCM is not aware of how to route the call ("Your call cannot be completed at dialed."). With call manager express, I would assume it is a dial peer problem. With CCM... I'm not sure where to begin. I have looked through RG's, RL's, Partitions, translation patterns, I'm seriously killing myself here.

For the outside calls going in, I get the following on the gateway:

*Oct  7 13:43:54.508: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8  callref = 0x052B
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Facility i = 0x9F8B0100A10F02010406072A8648CE1500040A0100
                Protocol Profile =  Networking Extensions
                0xA10F02010406072A8648CE1500040A0100
                Component = Invoke component
                        Invoke Id = 4
                        Operation = InformationFollowing (calling_name)
                                Name information in subsequent FACILITY message
        Calling Party Number i = 0x2181, '281-------'
                Plan:ISDN, Type:National
        Called Party Number i = 0x80, '9---'
                Plan:Unknown, Type:Unknown
*Oct  7 13:43:54.556: ISDN Se0/0/0:23 Q931: RX <- FACILITY pd = 8  callref = 0x052B
        Facility i = 0x9F8B0100A117020105020100800F535052494E472020202020202C5458
                Protocol Profile =  Networking Extensions
                0xA117020105020100800F535052494E472020202020202C5458
                Component = Invoke component
                        Invoke Id = 5
                        Operation = CallingName
                                Name Presentation Allowed Extended
                                Name = SPRING      ,TX
*Oct  7 13:43:54.568: ISDN Se0/0/0:23 Q931: TX -> SETUP_ACK pd = 8  callref = 0x852B
        Channel ID i = 0xA98381
                Exclusive, Channel 1
*Oct  7 13:43:54.604: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8  callref = 0x052B
        Cause i = 0x80E10D - Message type not implemented
        Call State i = 0x06
*Oct  7 13:43:54.620: ISDN Se0/0/0:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x852B
        Cause i = 0x80E5 - Message not compatible with call state
*Oct  7 13:43:54.700: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x052B
*Oct  7 13:43:54.720: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x852Bun all
All possible debugging has been turned off

I added the '-'s, if that was not obvious. The noteable thing in it, IMO, is Cause i = 0x80E10D - Message type not implemented.

My only hunch is that I have the PRI mis-configured with the wrong settings. 80 means its the gateways error, E1 means "The receiving equipment receives an unrecognized message, because either the message type is invalid, or the equipment does not support the message type. A problem with the remote configuration or with the local D-channel causes this issue." Ref: Understanding debug isdn q931 Disconnect Cause Codes [ISDN, CAS] - Cisco Systems

IS the PRI Interface info (Like if its NI2 or not) something I need to ask the PSTN provider to provide me?

I don't suppose anyone can toss me a bone?

chmorin · October 2010

Well I answered my own question with the outbound to inbound issue. I had the PRI mis-configured as the wrong type. Fixed that. Still working on the local issue.

chmorin · October 2010

Bang-Zoom-Wow. I knew it was something stupid.

I didn't add the new PT to the other CSS, and vice versa. So of course the call will fail. DOE!

Got it now, hopefully this can help someone.

pitviper · October 2010

Looks like you just needed to white-board it a bit

As for the physical circuit config - You usually get something from the ISP – here’s an example of ONE Com’s “cut sheet”:

Voice Circuit ID: xxxxxxxxxx

PRI – 23 B Channels

New DIDs;
xxx-xxx-1500-1599

Digital Configuration:
CO Direction – Two Way
Hunt Sequence – Ascending (1-23 Inbound – 23-1 Outbound)
NI2 Signaling
B8ZS
ESF
Digits out from CO – 4

chmorin · October 2010

pitviper wrote: »

Looks like you just needed to white-board it a bit

I am about to go and do that, actually. I am new to the network and it is a fairly large scale to ingest, especially for me being so new to the information. A representation of it will help tremendously.

Thanks for the help though.

Jollycork · October 2010

chmorin wrote: »

I am about to go and do that, actually. I am new to the network and it is a fairly large scale to ingest, especially for me being so new to the information. A representation of it will help tremendously.

Thanks for the help though.

Well, least you got yours to work,

I'm still struggling with inbound from POTS that isn't DID, to AA and no matter what Call Handler I create in Unity, can't get the AA to answer. I can get the inbound to ring an extension [CM] and then Unity picks up voice mail, but AA, nah just rings. CME is a lot easier than CCM + Unity:)

Well have to edit this:

got the AA to finally answer was the wrong DN # in CM to Unity [doh!] but now the directory handler doesn't work if it isn't one thing it's another...

Can call outbound, but not inbound.

Comments