Problem with incoming calls on a Cisco 2911

[ov]

Hi

The following debug info has been collected on the issue.

Does anyone have any kind of information to where i can start

looking for the problem?

Any help deeply appreciated.

Best regards

Ole Vik

*Jan 13 12:05:13.598: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0010
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18384
                Preferred, Channel 4
        Calling Party Number i = 0x2183, '91590773'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, '77621600'
                Plan:ISDN, Type:National
*Jan 13 12:05:13.598: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x8010 callID = 0x0010 switch = primary-net5 interface = User
*Jan 13 12:05:13.606: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x8010
        Channel ID i = 0xA98384
                Exclusive, Channel 4
*Jan 13 12:05:14.106: %VOICE_IEC-3-GW: SIP: Internal Error (Socket conn refused): IEC=1.1.186.7.102.1 on callID 95 GUID=3623054E1E4411E08011C471FE759FC8
*Jan 13 12:05:15.610: %VOICE_IEC-3-GW: SIP: Internal Error (Socket conn refused): IEC=1.1.186.7.102.1 on callID 96 GUID=3623054E1E4411E08011C471FE759FC8
*Jan 13 12:05:15.614: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x8010
        Cause i = 0x80A6 - Network out of order
*Jan 13 12:05:15.694: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x0010
*Jan 13 12:05:15.698: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8010

A2-gw#show voice iec description 1.1.186.7.102.1
    IEC Version: 1
    Entity: 1 (Gateway)
    Category: 186 (Signaling socket failure)
    Subsystem: 7 (SIP)
    Error: 102 (Socket conn refused)
    Diagnostic Code: 1

*Jan 13 12:09:31.742: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0011
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18385
                Preferred, Channel 5
        Calling Party Number i = 0x2183, '91590773'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, '77621600'
                Plan:ISDN, Type:National
*Jan 13 12:09:31.742: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x8011 callID = 0x0011 switch = primary-net5 interface = User
*Jan 13 12:09:31.750: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x8011
        Channel ID i = 0xA98385
                Exclusive, Channel 5
*Jan 13 12:09:32.250: %VOICE_IEC-3-GW: SIP: Internal Error (Socket conn refused): IEC=1.1.186.7.102.1 on callID 98 GUID=D000AA4F1E4411E08012C471FE759FC8
*Jan 13 12:09:33.754: %VOICE_IEC-3-GW: SIP: Internal Error (Socket conn refused): IEC=1.1.186.7.102.1 on callID 99 GUID=D000AA4F1E4411E08012C471FE759FC8
*Jan 13 12:09:33.758: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x8011
        Cause i = 0x80A6 - Network out of order
*Jan 13 12:09:33.834: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x0011
*Jan 13 12:09:33.834: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8011

[phooghen]

Does the GW has ip connectivity to the call agent ?

Can you ping the call agent (CUCM) ?

Pierre.

[ov]

Hi and thanks for the quick response

The call agent is reachable, and outgoing calls works fine.

[ov]

Here is the config, with the significant parts.

Fairly simple setup.

[phooghen]

Problem seems to be on the voip dialpeer

dial-peer voice 100 voip
preference 1
destination-pattern ..
session protocol sipv2
session target ipv4:10.160.5.21
dtmf-relay rtp-nte
codec g711alaw
fax-relay ecm disable
fax rate 14400
no vad

Try to change the destination-pattern .. to destination-pattern .T

[Amit Divekar]

Hello,

        Seems like that we are not able to establish connection in the inbound connection, could you please clarify was this an IOS upgrade & was this working before or is this a new install. Is the IOS 15.(2) t

From the disconnect cause code it is clear is that the disconnect is due to non-reachability.

A6

Network out of order

The destination is not reachable because of a network                 malfunction. The condition can last for an extended period. An immediate                 attempt to reconnect will probably fail.

Could you please add a show run/show run of the gateway, please ensure that you remove all the ip as well as password details while posting on public forums.

Please have a look at the following doc for further clarifications

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a0080b3e123.shtml#topic2

Regards,

Amit

[dijohn · Accepted solution]

Could you verfiy the SIP Trunks on the CUCM 10.160.5.22 10.160.5.21

dial-peer voice 100 voip

preference 1

destination-pattern ..

session protocol sipv2

session target ipv4:10.160.5.21

dtmf-relay rtp-nte

codec g711alaw

fax-relay ecm disable

fax rate 14400

no vad

!

dial-peer voice 101 voip

huntstop

preference 2

destination-pattern ..

session protocol sipv2

session target ipv4:10.160.5.22

dtmf-relay rtp-nte

codec g711alaw

fax-relay ecm disable

fax rate 14400

no vad

These are the dial-peers towards the CUCM Right?.

HTH

PS: Rate useful posts

[ov]

I have found the problem, and it was related to udp/tcp incompatibility between the cisco gateway and the manager.

The manager expected incoming tcp packets, while the Cisco gateway transferred SIPv2 udp.  After changing this

setting on the manager, all worked 100%

Since this indeed was related to the SIP trunks, i'll grant the correct answer to the last poster.

Thanks for all your help!

[dijohn]

Thats good news :)...

How did you figure it out? CUCM Traces?

[ov]

Actually no.

Debugging iec on the gateway gave me a hunch;

A2-gw#show voice iec description 1.1.186.7.102.1
    IEC Version: 1
    Entity: 1 (Gateway)
    Category: 186 (Signaling socket failure)
    Subsystem: 7 (SIP)
    Error: 102 (Socket conn refused)
    Diagnostic Code: 1

[lightpath0323]

I had the very same issue and the culprit was that the IP Address in the dial-peer that was going from the gateway to the call manager add the wrong ipv:4 address for Call Manager. Simple issue but always pays to double check the IPs, maybe even change it to a different node.

So it could be a couple of things:

Make sure TCP+UDP is in your security sip profile (the one you've assigned to the SIP trunk in CUCM)
Verify your IP addresses for your dial-peers, make sure they're pointing to the correct device (Re-Verify).