fax connected to fxs get's busy tone

jeroenhermans · ‎07-02-2008

Hi,

We have a remote site with a 2811 running 12.4(13r)T

There are 4 BRI ports and 2 FXS ports.

I have a fax connected to fxs 0/1/0

The dial-peers are configured like this :

dial-peer voice 7575 pots

destination-pattern 7575

port 0/1/0

The voice-port has the default configuration :

voice-port 0/1/0

!

voice-port 0/1/1

!

I can see when calling the fax number from a mobile phone that the BRI port becomes active

and the fxs goes to ringing :

CHSOSANyonISR#show voice port summary

IN OUT

PORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC

============== == ============ ===== ==== ======== ======== ==

0/1/0 -- fxs-ls up up on-hook ringing y

0/1/1 -- fxs-ls up dorm on-hook idle y

0/2/0 1 bri-voice up dorm none none y

0/2/0 2 bri-voice up dorm none none y

0/2/1 1 bri-voice up dorm none none y

0/2/1 2 bri-voice up dorm none none y

0/3/0 1 bri-voice up dorm none none y

0/3/0 2 bri-voice up dorm none none y

0/3/1 1 bri-voice up up none none y

0/3/1 2 bri-voice up dorm none none y

50/0/1 1 efxs up up on-hook idle y

50/0/2 1 efxs up up on-hook idle y

50/0/3 1 efxs up up on-hook idle y

50/0/4 1 efxs up up on-hook idle y

50/0/5 1 efxs up up on-hook idle y

50/0/6 1 efxs up up on-hook idle y

However, I get a busy tone directly after this.

Any help will be much appreciated.

Rgds,

Jeroen

paolo bevilacqua · ‎07-03-2008

Hi, you need to take a trace with "debug isdn q931" and "term mon" to debug this.

jeroenhermans · ‎07-03-2008

Hi,

Thanks for your reply. I noticed that when I call the number, I first get a second dal tone for about 10 seconds and then I get the busy tone. This is the output of the debug :

001083: *Jul 3 12:17:51.571 PCTime: ISDN BR0/2/0 Q931: RX <- SETUP pd = 8 callref = 0x01

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 = 0x00A3, N/A

Plan:Unknown, Type:Unknown

Called Party Number i = 0x81, '75'

Plan:ISDN, Type:Unknown

001084: *Jul 3 12:17:51.599 PCTime: ISDN BR0/2/0 Q931: TX -> CALL_PROC pd = 8 callref = 0x81

Channel ID i = 0x89

Exclusive, B1

001085: *Jul 3 12:17:51.615 PCTime: ISDN BR0/2/0 Q931: TX -> PROGRESS pd = 8 callref = 0x81

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

001086: *Jul 3 12:17:52.511 PCTime: ISDN BR0/2/0 Q931: TX -> CONNECT pd = 8 callref = 0x81

Channel ID i = 0x89

Exclusive, B1

Progress Ind i = 0x8182 - Destination address is non-ISDN

001087: *Jul 3 12:17:52.587 PCTime: ISDN BR0/2/0 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x01

001088: *Jul 3 12:17:52.591 PCTime: %ISDN-6-CONNECT: Interface BRI0/2/0:1 is now connected to N/A N/A

001089: *Jul 3 12:17:58.591 PCTime: %ISDN-6-CONNECT: Interface BRI0/2/0:1 is now connected to N/A N/A

001090: *Jul 3 12:18:07.539 PCTime: ISDN BR0/2/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x01

Cause i = 0x8090 - Normal call clearing

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

001091: *Jul 3 12:18:07.543 PCTime: %ISDN-6-DISCONNECT: Interface BRI0/2/0:1 disconnected from unknown , call lasted 14 seconds

001092: *Jul 3 12:18:07.563 PCTime: ISDN BR0/2/0 Q931: TX -> RELEASE pd = 8 callref = 0x81

001093: *Jul 3 12:18:07.623 PCTime: ISDN BR0/2/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x01

I presume the port does not know what to do with the call.

Thanks for your help,

Jeroen

paolo bevilacqua · ‎07-03-2008

Hi, destination-pattern should be 75 as this is the number you're receiving.

Also check that you have configured;

network-clock-participate wic 2

network-clock-select 1 bri 0/2/0

network-clock-select 2 bri 0/2/1

If still problems collect "debug vpm signal" together with "isdn q931".

jeroenhermans · ‎07-03-2008

Hi,

But I'm translating this number to make it a 4 digit number 7575 as you can see in the output of the show call active voice (when I'm placing a call to the number) :

Strange thing is I have 3 call-legs (see attached output)?

Thanks,

Jeroen

paolo bevilacqua · ‎07-03-2008

Hi, the translation cannot be checked from the debug you sent. Anyway, you still need to network-clock commands.

It is known that sometime calls remain hanging (never fixed bugs). The only solution is to reload router as they are non-cleanable.

jeroenhermans · ‎07-03-2008

Hi,

Please find attached the trace with the Voice Port Module signaling debugging is on

Also, I have 2 wic's with each 2 bri's, do I need to network clock command for both?

Thanks,

Jeroen

paolo bevilacqua · ‎07-03-2008

For this trace the disconnection came from remote party. Was it taken with the network-clock commands in place? And yes you need them exactly as I've referenced above.

hassan_oudeh · ‎11-02-2008

Hi....

Im wondering if you have solved this issue, as im having a very similar case !!

please advice !!

regards,