Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1134
Views
0
Helpful
7
Replies

incoming calls problem

miroslavpetkovic
Level 1
Level 1

‎06-11-2009 02:58 AM - edited ‎03-15-2019 06:28 PM

Hi,

I have a problem with incoming calls over router 2821 with

Cisco Unified Communications Manager Express Version 7.0(0).

Outgoing calls work fine.

ISDN BRI line is connected with router over Intracom modem (NT) and VIC2 - BRI-NT/TE card (TE) - European standard.

I want to route incoming calls to local 101 which is successfuly registrated with CME.

When I call 0113984.... number of ISDN line, layer 1 is up:

ISDN BRI0/1/0 interface

dsl 4, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 94, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 4 CCBs = 0

The Free Channel Mask: 0x80000003

but call doesn't match incoming dial-peer.

Could you check, if I made any mistake in configuration.

Best regards,

Miroslav Petkovic

Labels:
Preview file
6 KB
0 Helpful
7 Replies 7

miroslavpetkovic
Level 1
Level 1

‎06-11-2009 03:59 AM

This log is maybe helpful:

debug isdn q931

*Jun 11 11:58:21.338: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8 callref = 0x61

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Exclusive, B1

Calling Party Number i = 0x2183, '631035948'

Plan:ISDN, Type:National

Calling Party Number i = 0x2183, '631035948'

Plan:ISDN, Type:National

Called Party Number i = 0x81, '4760'

Plan:ISDN, Type:Unknown

DatatekCME#BAD FRAME()BAD FRAME()

DatatekCME#

*Jun 11 11:58:33.262: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 76 changed to down

DatatekCME#

*Jun 11 11:58:33.262: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

0 Helpful

miroslavpetkovic
Level 1
Level 1
In response to miroslavpetkovic

‎06-11-2009 06:00 AM

This is log when I unsuccessfuly tried to make incoming call (ISDN number 0113984760).

0 Helpful

jbarcena
Level 9
Level 9
In response to miroslavpetkovic

‎06-11-2009 07:35 AM

The problem is that you are receiving 4760 from the PSTN and you do not have a dial-peer for that number. You only have the following:

dial-peer voice 11 pots

description Calls from PSTN

incoming called-number 101

port 0/1/0

!

dial-peer voice 1000 pots

destination-pattern 9T

port 0/1/0

None of this dial-peers match the 4760, you could either change the dial-peer 11 to this:

dial-peer voice 11 pots

description Calls from PSTN

incoming called-number .

port 0/1/0

direct-inward-dial

Or create some other dial-peers to match other digits.

If that doesn't work, take a 'debug voice ccapi inout' and upload it to the post.

HTH

//Jorge

0 Helpful

miroslavpetkovic
Level 1
Level 1
In response to jbarcena

‎06-11-2009 10:38 PM

Hi,

I changed dial-peer 11 in:

dial-peer voice 11 pots

description Calls from PSTN

incoming called-number .

port 0/1/0

direct-inward-dial

and registered local 4760.

But I didn't have ouput from debug voice ccapi inout, only:

---------------------------------------

DatatekCME#debug voice ccapi inout

voip ccapi inout debugging is on

DatatekCME#

*Jun 12 06:29:24.361: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up

DatatekCME#

*Jun 12 06:29:24.397: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 114 changed to up

DatatekCME#

*Jun 12 06:29:36.393: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 114 changed to down

DatatekCME#

*Jun 12 06:30:02.961: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to down

DatatekCME#

---------------------------------------

New version of configuration is in attachment.

BR,

Miroslav Petkovic

Preview file
6 KB
0 Helpful

miroslavpetkovic
Level 1
Level 1
In response to miroslavpetkovic

‎06-12-2009 02:27 AM

Hi,

This is debug isdn q931 command output during an outgoing call, which is successfull:

------------------------------------------------------------------------------------------------

DatatekCME#undebug all

All possible debugging has been turned off

DatatekCME#debug isdn q931

debug isdn q931 is ON.

DatatekCME#

*Jun 12 07:10:33.317: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x 0 0x0, Calling num 101

*Jun 12 07:10:33.321: ISDN BR0/1/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inact ive

*Jun 12 07:10:33.373: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up

*Jun 12 07:10:33.585: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 111 c hanged to up

DatatekCME#

*Jun 12 07:10:33.585: ISDN BR0/1/0 Q931: Sending SETUP callref = 0x0011 callID = 0x8013 switch = basic-net3 interface = User

*Jun 12 07:10:33.585: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x11

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x81

Preferred, B1

Progress Ind i = 0x8183 - Origination address is non-ISDN

Calling Party Number i = 0x0080, '101'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '0631035948'

Plan:Unknown, Type:Unknown

DatatekCME#

*Jun 12 07:10:33.813: ISDN BR0/1/0 Q931: RX <- SETUP_ACK pd = 8 callref = 0x91

Channel ID i = 0x89

Exclusive, B1

*Jun 12 07:10:33.917: ISDN BR0/1/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x91

DatatekCME#

*Jun 12 07:10:37.941: ISDN BR0/1/0 Q931: RX <- ALERTING pd = 8 callref = 0x91

Progress Ind i = 0x8288 - In-band info or appropriate now available

DatatekCME#

*Jun 12 07:11:06.537: ISDN BR0/1/0 Q931: RX <- CONNECT pd = 8 callref = 0x91

Date/Time i = 0x09060C090A38

Date (yr-mm-dd) = 09-06-12

Time (hr:mnt:sec) = 09:10:56

*Jun 12 07:11:06.541: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to N/A N/A

DatatekCME#

*Jun 12 07:11:06.541: ISDN BR0/1/0 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x11

DatatekCME#

*Jun 12 07:11:12.541: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to N/A N/A

*Jun 12 07:11:13.033: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x91

Cause i = 0x8090 - Normal call clearing

Progress Ind i = 0x8288 - In-band info or appropriate now available

DatatekCME#

*Jun 12 07:11:13.037: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1 disconnected from unknown , call lasted 6 seconds

DatatekCME#

*Jun 12 07:11:43.137: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x91

Cause i = 0x8090 - Normal call clearing

*Jun 12 07:11:43.141: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x11

*Jun 12 07:11:43.705: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 111 changed to down

DatatekCME#

*Jun 12 07:11:43.705: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

DatatekCME#

*Jun 12 07:11:53.805: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

DatatekCME#

*Jun 12 07:11:53.857: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to down

----------------------------------------------------------------------------------------------

BR,

Miroslav

0 Helpful

miroslavpetkovic
Level 1
Level 1
In response to miroslavpetkovic

‎06-12-2009 02:27 AM

This is debug isdn q931 command output during an incoming call, which is unsuccessfull:

-----------------------------------------------------------------------------------------------

*Jun 12 07:13:50.685: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up

DatatekCME#

*Jun 12 07:13:50.725: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 121 changed to up

DatatekCME#

*Jun 12 07:13:50.797: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8 callref = 0x7A

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Exclusive, B1

Calling Party Number i = 0x2183, '631035948'

Plan:ISDN, Type:National

Calling Party Number i = 0x2183, '631035948'

Plan:ISDN, Type:National

Called Party Number i = 0x81, '4760'

Plan:ISDN, Type:Unknown

DatatekCME#BAD FRAME()BAD FRAME()

DatatekCME#

*Jun 12 07:14:02.721: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 121 changed to down

DatatekCME#

*Jun 12 07:14:02.721: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

DatatekCME#

*Jun 12 07:14:21.205: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x7A

Cause i = 0x8090 - Normal call clearing

*Jun 12 07:14:21.213: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x7A

Cause i = 0x8090 - Normal call clearing

DatatekCME#

*Jun 12 07:14:31.917: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

DatatekCME#

*Jun 12 07:14:31.969: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to down

------------------------------------------------------------------------------------------

BR,

0 Helpful

miroslavpetkovic
Level 1
Level 1
In response to miroslavpetkovic

‎06-12-2009 04:17 AM

Hi

I noticed strange situation.

I changed configuration, and enabed working of both ISDN BRI ports of router. Configuration is same on both ports.

--------------------------------------------------------------

interface BRI0/1/0

no ip address

isdn switch-type basic-net3

isdn incoming-voice voice

!

interface BRI0/1/1

no ip address

isdn switch-type basic-net3

isdn incoming-voice voice

voice-port 0/1/0

compand-type a-law

bearer-cap Speech

!

voice-port 0/1/1

compand-type a-law

bearer-cap Speech

dial-peer voice 11 pots

description Calls from PSTN

incoming called-number .

direct-inward-dial

port 0/1/0

!

dial-peer voice 1000 pots

destination-pattern 9T

port 0/1/0

!

dial-peer voice 12 pots

description Calls from PSTN

incoming called-number .

direct-inward-dial

port 0/1/1

!

dial-peer voice 1001 pots

destination-pattern 9T

port 0/1/1

Incoming calls over port 0/1/1 are working corectly, but over 0/1/0 don't work.

I put in attacment debugs from 0/1/1.

(voip ccapi inout 011.txt, debug isdn q931 011.txt)

What is your opinion about it?

BR,

Miroslav

Preview file
6 KB
0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents