Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

VIC-2BRI not sending Calling-ID

Hi, i´ve the problem on my 1760 that calling out the ISDN-line from a fxs-port attached analog phone there is no Calling-ID presented in the call setup of the router bri-interface. I verified that with deb isdn q931. Using a VOIP-dial-peer it is presented.

I used IOSes 12.3(6);12.3(4)T3;12.3(7)T. All the same.

The miracle is that in the headquarter there is a 3640, also with the same isdn-vic which presents the calling-id and i can´t see a difference in the commands of the voice-ports and dial-peers. The headqarter-router is a 3640 with with 12.3(4)T and Call-manager express with IP-Phones and ATA-Box, no FXS in the router. This is the only difference I see. The 1760 has local FX-S ports, the 3640 has IP-Phones and ATA-Box.

I tried a couple of commands like no caller-id block or no clid strip and so on, but nothing worked. Also show-commands show up that there is no call-blocking configured anyhow.

Following a excerpt of the configuration:

*************************************************

voice-card 2

!

voice-card 3

!

isdn switch-type basic-net3

!

!

voice call send-alert

!

voice service pots

!

voice service voip

!

!

interface BRI2/0

no ip address

isdn switch-type basic-net3

isdn incoming-voice voice

isdn answer1 <replaced>

isdn answer2 <replaced>

!

!

control-plane

!

!

voice-port 2/0

compand-type a-law

cptone DE

!

voice-port 3/0

cptone DE

timeouts interdigit 2

caller-id enable

!

voice-port 3/1

cptone DE

timeouts interdigit 2

caller-id enable

!

dial-peer voice <replaced> pots

destination-pattern <replaced>

port 3/1

!

dial-peer voice 20 pots

destination-pattern .T

direct-inward-dial

port 2/0

!

dial-peer voice <replaced> pots

destination-pattern <replaced>

port 3/0

!

gateway

!

*********************************************

Does anybody have an idea?

thanks in advance

Horst

3 REPLIES
New Member

Re: VIC-2BRI not sending Calling-ID

Here is additionally a debug output from "debug translation detail" and "debug isdn q931". Although there is no translation rule aplied it shows that there originaly was a caller-id which magicaly is not used by the isdn bri:

***************************************************

*Mar 3 11:57:39.604: xrule_checking

*Mar 3 11:57:39.604: xrule_checking calling 4010920, called 8009114

*Mar 3 11:57:39.608: xrule_checking peer_tag 20, direction 2, protocol 0

*Mar 3 11:57:39.608: xrule_checking Return rc = -5

*Mar 3 11:57:39.616: ISDN BR2/0 Q931: Applying typeplan for sw-type 0x1 is 0x0

0x0, Called num 8009114

*Mar 3 11:57:39.616: ISDN BR2/0 Q931: TX -> SETUP pd = 8 callref = 0x14

Bearer Capability i = 0x8090A3

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x81

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

Called Party Number i = 0x80, '8009114'

Plan:Unknown, Type:Unknown

*Mar 3 11:57:39.852: ISDN BR1/0 Q931: RX <- SETUP_ACK pd = 8 callref = 0x94

Channel ID i = 0x89

*Mar 3 11:57:39.852: ISDN BR2/0 Q931: RX <- SETUP_ACK pd = 8 callref = 0x94

Channel ID i = 0x89

*Mar 3 11:57:40.766: ISDN BR1/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x94

*Mar 3 11:57:40.766: ISDN BR2/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x94

*Mar 3 11:57:41.074: ISDN BR1/0 Q931: RX <- ALERTING pd = 8 callref = 0x94

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

*Mar 3 11:57:41.074: ISDN BR2/0 Q931: RX <- ALERTING pd = 8 callref = 0x94

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

*Mar 3 11:57:53.915: ISDN BR2/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x14

Cause i = 0x8090 - Normal call clearing

*Mar 3 11:57:54.031: ISDN BR1/0 Q931: RX <- RELEASE pd = 8 callref = 0x94

*Mar 3 11:57:54.031: ISDN BR2/0 Q931: RX <- RELEASE pd = 8 callref = 0x94

*Mar 3 11:57:54.039: ISDN BR2/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x14

!*****************************************************

New Member

Re: VIC-2BRI not sending Calling-ID

Just mor debugs ...

Following output is generated from "debug isdn events detail" it shows that for any reason the router believes this is a private call. By the way the problem exists only by calling from a locally attached FXS port through ISDN. Calling from a VOIP Dialpeer the Calling-number is correctlx displayed!

****************************************************

*Mar 7 18:30:23.665: ISDN BR2/0 EVENTd: isdn_get_guid: Got Guid 34BCADED817BRec

eived pdata len 0x3F data:1C 39 9E 1 0 3 67 74 64 0 0 0 2E 49 41 4D 2C D A 47 43

49 2C 33 34 62 63 61 64 65 64 33 31 33 30 31 31 64 36 38 31 37 62 38 38 33 30 3

4 37 39 64 63 36 35 64 D A D A 1E 2 81 83

*Mar 7 18:30:23.669: ISDN BR2/0 EVENTd: process_bri_call: No name in GTD

*Mar 7 18:30:23.669: ISDN BR2/0 EVENTd: pak_private_number: Calling Number IE i

s being stripped

*Mar 7 18:30:23.669: ISDN BR2/0 EVENTd: calltrkr_setup_received: isdn_info=2204

005392l, call_id=0x8067 ORIGINATE

*Mar 7 18:30:23.669: ISDN BR2/0 EVENTd: calltrkr_setup_received: calltracker di

sabled

*********************************************

please can anybody help me out, I need the calling-number for sective charging!

sincerly

Horst Wagner

New Member

Re: VIC-2BRI not sending Calling-ID

As ever I had to find the solution by myself.

The solution is to configure "station-id number NNN"

on the Voice-Port of the FXS- Module and everything works fine.

In the documentation is written that this parameter only is useful for onnet-calls. So to me it looks furthermore like a bug and I found a workaround.

bye

Horst

111
Views
0
Helpful
3
Replies
CreatePlease to create content