02-26-2013 04:36 AM - edited 03-16-2019 03:56 PM
We are unable to process uncoming calls but outgoing works fine.
her eis what we see from debug isdn q931
Bearer Capability i = 0x9090A2
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '5136297000'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '1549'
Plan:Unknown, Type:Unknown
Feb 26 07:47:06.163: ISDN Se0/1/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x8124
Channel ID i = 0xA98381
Exclusive, Channel 1
Feb 26 07:47:06.675: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num 2 126431549
Feb 26 07:47:06.679: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Called num 80 03
Feb 26 07:47:06.679: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0081
Bearer Capability i = 0x9090A2
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '2126431549'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '8003'
Plan:Unknown, Type:Unknown
Redirecting Number i = 0x00008F, '2800'
Plan:Unknown, Type:Unknown
Feb 26 07:47:06.767: ISDN Se0/1/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8081
Channel ID i = 0xA98397
Exclusive, Channel 23
Feb 26 07:47:06.955: ISDN Se0/1/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8081
Cause i = 0x829C - Invalid number format (incomplete number)
Progress Ind i = 0x8288 - In-band info or appropriate now available
Feb 26 07:47:06.963: ISDN Se0/1/0:23 Q931: TX -> PROGRESS pd = 8 callref = 0x8124
Cause i = 0x829C - Invalid number format (incomplete number)
Progress Ind i = 0x8288 - In-band info or appropriate now available
Feb 26 07:47:22.147: ISDN Se0/1/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x0124
Cause i = 0x8A90 - Normal call clearing
Feb 26 07:47:22.147: ISDN Se0/1/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x8124
Feb 26 07:47:22.151: ISDN Se0/1/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0081
Cause i = 0x8A90 - Normal call clearing
Feb 26 07:47:22.175: ISDN Se0/1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0124
Feb 26 07:47:22.179: ISDN Se0/1/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x8081
Feb 26 07:47:22.183: ISDN Se0/1/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0081
Any idea what this means?
02-26-2013 04:56 AM
Seems like extension (or whatever it is) 1549 diverts calls to 8003, via 2800.
So you will have to check and understand yoiur call flow and configuration.
02-26-2013 05:27 AM
Paolo
Thanks for your reply.
This is a cisco call manager express setup.
Does This means that some config item was changed in the gateway?
This is what we have.
voice translation-rule 1
rule 1 /^.*$/ /2126431549/
!
voice translation-rule 2
rule 1 /0865/ /8000/
rule 2 /9605/ /8002/
rule 3 /9626/ /8003/
num-exp 6470 8003
num-exp 6471 8003
num-exp 0865 8003
num-exp 1549 2800
Many but not all the e-phone config items have this
ephone-dn 26 dual-line
number 2800
pickup-group 1
label 2800
description Receptionist
name receptionist
call-forward all 8003
call-forward busy 2802
call-forward noan 8003 timeout 15
no huntstop
02-26-2013 05:30 AM
call-forward all 8003
Recommend you have configuration redone by a reputable consultant, or UC certified Cisco partner.
02-26-2013 06:24 AM
You are translating 1549 to 2800, then 2800 is setup to forward all to 8003, which you did not provide configuration for, perhaps if there is no matching ephone it matches POTS dial peer and sends the call out to PSTN where it fails because that is not a real number.
HTH,
Chris
02-26-2013 07:03 AM
Hi,
the debug isdn q931 shows that the incoming called number are 1549. then it is translated to 2800.
at this stage it matches the ephone-dn 26 which has extension 2800. after that it is forwarded to 8003.
8003 match pots dial-peer and hit the PRI again.
my recommendation to you is check your dial-peers
HTH
Anas
please rate if it is helpful
02-26-2013 07:05 AM
Anas,
How is this different from what said?
Chris
02-26-2013 07:32 AM
The problem ended up being the attached module that controls the auto attendant and VM.
We reset it and we are back in business.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide