05-04-2011 11:17 AM - edited 03-16-2019 04:48 AM
Guys,
I have an interesting issue that I can't solve. When I call my number using local PSTN format I don't get complete number. I should get xxx8722. Instead of this I am getting xxx872. Thank you guys for your help!
May 4 19:15:55.298 cest: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x1AA2
Bearer Capability i = 0x9090A3
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839A
Exclusive, Channel 26
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, 'N/A'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, 'xxx872'
Plan:ISDN, Type:Subscriber(local)
May 4 19:15:55.298 cest: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x9AA2 callID = 0x0022 switch = primary-net5 interface = User
May 4 19:15:55.306 cest: ISDN Se0/0/0:15 Q931: TX -> SETUP_ACK pd = 8 callref = 0x9AA2
Channel ID i = 0xA9839A
Exclusive, Channel 26
May 4 19:15:55.318 cest: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x9AA2
May 4 19:15:55.334 cest: ISDN Se0/0/0:15 Q931: RX <- INFORMATION pd = 8 callref = 0x1AA2
Called Party Number i = 0xC1, '2'
Plan:ISDN, Type:Subscriber(local)
May 4 19:15:55.334 cest: ISDN **ERROR**: Module-CCPRI Function-CCPCC_CallRoutingIn Error-Unknown event received in message from L3 or Host: 93
May 4 19:15:55.354 cest: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x9AA2
Cause i = 0x8081 - Unallocated/unassigned number
e4r-vg-hbptn01#
May 4 19:15:55.370 cest: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x1AA2
May 4 19:15:55.370 cest: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x9AA2
e4r-vg-hbptn01#
May 4 19:15:57.634 cest: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x9AA1
May 4 19:15:57.662 cest: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x1AA1
My configuration is:
controller E1 0/0/0
pri-group timeslots 1-31
interface Serial0/0/0:15
no ip address
encapsulation hdlc
no logging event link-status
no snmp trap link-status
isdn switch-type primary-net5
isdn overlap-receiving T302 4000
isdn incoming-voice voice
isdn negotiate-bchan
trunk-group tg_voice_pri
no cdp enable
Solved! Go to Solution.
05-05-2011 01:04 AM
Indeed, either you were missing the command "overlap-receiving" or the "dial-peer" isnot set properly.
Pierre.
05-07-2011 04:46 AM
To my knowledge, ampersand is not a valid character in number patterns:
CME(config-dial-peer)# incoming called-number .&
Incorrect format for E.164 Number
regular expression must be of the form ^[][^0-9,A-F#*.?+%()-]*T?(\$)?$
05-04-2011 11:37 AM
Which IOS version are you using ?
05-04-2011 12:07 PM
I don't know. I have already left my work today. I will post it tomorrow.
05-05-2011 12:56 AM
Guys,
could it be this case? http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a00800b48cb.shtml
I am using variable extension range xxx872, but I have xxx8722 as well.
My config after a change would looks like this:
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn overlap-receiving T302 4000
isdn incoming-voice voice
isdn negotiate-bchan
no cdp enable
dial-peer voice 1000 pots
permission orig
description Incoming from PSTN
huntstop
incoming called-number .T
direct-inward-dial
Is it correct?
My IOS is: c2800nm-spservicesk9-mz.124-24.T2.bin
05-05-2011 01:04 AM
Indeed, either you were missing the command "overlap-receiving" or the "dial-peer" isnot set properly.
Pierre.
05-05-2011 08:15 AM
Try updating to something stable, like 15.0(1)M5.
05-05-2011 09:53 AM
Hi,
It works!!!! THANK YOU!!! I have changed it to this:
dial-peer voice 1000 pots
incoming called-number .T
direct-inward-dial
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn overlap-receiving T302 4000
isdn incoming-voice voice
isdn negotiate-bchan
no cdp enable
05-06-2011 02:40 AM
Guys,
Could you please help me? It still does. It sometimes works and sometimes not.Now I am getting xxx72 instead of xxx722. Digit 2 arrives later in ISDN setup. May it be anything wrong with timing?
Thanks.
May 6 10:06:39.659 cest: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x1B4D
Bearer Capability i = 0x9090A3
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839E
Exclusive, Channel 30
Progress Ind i = 0x8083 - Origination address is non-ISDN
Calling Party Number i = 0x00A3, N/A
Plan:Unknown, Type:Unknown
Called Party Number i = 0xC1, 'xxx72'
Plan:ISDN, Type:Subscriber(local)
May 6 10:06:39.663 cest: ISDN Se0/0/0:15 Q931: Received SETUP callref = 0x9B4D callID = 0x00B0 switch = primary-net5 interface = User
May 6 10:06:39.667 cest: ISDN Se0/0/0:15 Q931: TX -> SETUP_ACK pd = 8 callref = 0x9B4D
Channel ID i = 0xA9839E
Exclusive, Channel 30
May 6 10:06:39.683 cest: ISDN Se0/0/0:15 Q931: RX <- INFORMATION pd = 8 callref = 0x1B4D
Called Party Number i = 0xC1, '2'
Plan:ISDN, Type:Subscriber(local)
May 6 10:06:39.687 cest: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x9B4D
May 6 10:06:39.719 cest: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x9B4D
Cause i = 0x8081 - Unallocated/unassigned number
May 6 10:06:39.743 cest: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x1B4D
May 6 10:06:39.743 cest: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x9B4D
05-06-2011 03:56 AM
What is your dial-peer configuration ?
05-06-2011 04:12 AM
We have variable dialing plan. I can receive numbers like xxx87-1, xxx87-11, xxx87-111 from PSTN.
dial-peer voice 3130 pots
permission orig
description Incoming from PSTN
translation-profile incoming tp_PSTN_to_ITN
huntstop
incoming called-number xxx87.T
direct-inward-dial
voice translation-profile tp_PSTN_to_ITN
translate called 3130000
voice translation-rule 3130000
rule 1 /^xxx87\(...$\)/ /2222\10/
rule 2 /^xxx87\(..$\)/ /2222\100/
rule 3 /^xxx87\(.$\)/ /2222\1000/
rule 4 /^xxx87/ /22220000/
dial-peer voice 1250000 voip
permission term
huntstop
destination-pattern [2-7].......$
session protocol sipv2
session target ipv4:x.x.x.x
dtmf-relay rtp-nte
05-06-2011 06:36 AM
You cannot have overlapping entries with overlap-receiving.
As soon a matching DP is matched, the call is sent to CM without wating for further digits.
But you can have for example, xxx871 and xxx872yy
05-07-2011 01:26 AM
I had a discussion with my colleagues about this problem and he told me that he had the same problem and he has fixed it using configuration like this one:
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn overlap-receiving T302 4000
isdn negotiate-bchan
no cdp enable
dial-peer voice 3130 pots
permission orig
description Incoming from PSTN
translation-profile incoming tp_PSTN_to_ITN
huntstop
incoming called-number xxx87.&
direct-inward-dial
voice translation-profile tp_PSTN_to_ITN
translate called 3130000
voice translation-rule 3130000
rule 1 /^xxx87\(...$\)/ /2222\10/
rule 2 /^xxx87\(..$\)/ /2222\100/
rule 3 /^xxx87\(.$\)/ /2222\1000/
rule 4 /^xxx87/ /22220000/
dial-peer voice 1250000 voip
permission term
huntstop
destination-pattern [2-7].......$
session protocol sipv2
session target ipv4:x.x.x.x
dtmf-relay rtp-nte
Apparently he just did the same with one exception in the incoming dialpeer (incoming called-number xxx87.&). I am going to test it next week so I will let you know if it works.
Thanks.
05-07-2011 04:46 AM
To my knowledge, ampersand is not a valid character in number patterns:
CME(config-dial-peer)# incoming called-number .&
Incorrect format for E.164 Number
regular expression must be of the form ^[][^0-9,A-F#*.?+%()-]*T?(\$)?$
05-08-2011 01:09 AM
I meant this:
incoming called-number .%
Sorry about it.
12-13-2011 10:36 AM
Hi.
Solution for overlap receiving is descripted in this thread.
https://supportforums.cisco.com/message/3377554#3377554
Thanks for help. bye
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