05-22-2012 08:23 AM - edited 03-21-2019 05:49 AM
Hi there,
I have a problem with a UC540 connected to the BRI network. When some partners call the central number or some extensions, the receive a "busy" signal. The isdn q931 debug log shows the following (just an example)
---
024282: May 22 14:42:15.405: ISDN BR0/1/1 Q931: RX <- SETUP pd = 8 callref = 0x75
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 = 0x2181, '607XXXXXXXXX'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '93211'
Plan:ISDN, Type:Subscriber(local)
High Layer Compat i = 0x9181
024283: May 22 14:42:15.413: ISDN BR0/1/1 Q931: TX -> SETUP_ACK pd = 8 callref = 0xF5
Channel ID i = 0x89
Exclusive, B1
024284: May 22 14:42:15.545: ISDN BR0/1/1 Q931: RX <- INFORMATION pd = 8 callref = 0x75
Called Party Number i = 0xC1, '0'
Plan:ISDN, Type:Subscriber(local)
024285: May 22 14:42:15.553: ISDN BR0/1/1 Q931: TX -> DISCONNECT pd = 8 callref = 0xF5
Cause i = 0x809C - Invalid number format (incomplete number)
024286: May 22 14:42:15.781: ISDN BR0/1/1 Q931: RX <- RELEASE pd = 8 callref = 0x75
024287: May 22 14:42:15.781: ISDN BR0/1/1 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xF5
---
What I am wondering about are the two Called Party Number - Entries. I set the isdn timers to:
T203: 20000
T303: 60000
T310: 60000
isdn overlap-receiving T302: 20000
Any ideas, how I can resolve this?
kind regards,
eckhard
p.s.: Ahh, sorry, UC540, SW 8.2
05-22-2012 09:14 AM
Do you have something configured for 932110 ?
And if yes, what it is ?
Note that once overlap receiving works, there is no need to change timers from default.
05-22-2012 09:38 PM
Hi Eckhard,
Paolo has pretty much given you the answer, but it should be noted that your ISDN is working as it should be, just that the incoming calling is not pointing to a valid DN on the system somewhere, please check your incoming call programming and make sure you either have the incoming calls going to a reception extension number, direct to the staff phone extension number, or, to an AA/B-ACD.
A call flow topology would be very helpful so we know what you are trying to achieve as well
Cheers,
David.
05-23-2012 07:28 AM
Hello David, hello Paolo,
thank you for your support, even if my mail was rather short and cryptical ;-)
Before going into details: The core problem seems to be that some calls from some partners do reach the central number or an extension. "Normally" all extensions and the central (-0) can be reached. But there is a small number of calling parties that can not call the central number or an extension. The partners are always the same, but they use different carriers. The problem is persistent - if you belong to these partners, you can not reach the numbers.
The problem is not limited to one of the three existing BRI interfaces - all are effected.
So, now here is the config (in parts):
voice translation-rule 1
rule 1 /^93211$/ /22/
rule 2 /^932110$/ /22/
!
voice translation-rule 2
rule 5 // /000/ type international unknown
rule 6 // /00/ type national unknown
rule 7 // /0/ type subscriber unknown
!
voice translation-rule 3
rule 5 /^000/ // type any international plan any isdn
rule 6 /^00/ // type any national plan any isdn
rule 7 /^0/ // type any subscriber plan any isdn
!
voice translation-rule 4
rule 15 // //
!
voice translation-rule 5
rule 1 /^932110/ /22/
!
voice translation-rule 6
rule 1 /9321110/ /10/
rule 2 /9321111/ /11/
rule 3 /9321112/ /12/
-- Other translation-rules following, but similar to the ones above.
[...]
voice translation-profile PSTN-IN
translate calling 2
translate called 1
!
voice translation-profile PSTN-OUT
translate calling 3
translate called 4
!
[...]
interface BRI0/1/0
no ip address
isdn switch-type basic-net3
isdn timer T203 20000
isdn timer T303 60000
isdn timer T310 60000
isdn overlap-receiving T302 20000
isdn tei-negotiation first-call
isdn point-to-point-setup
isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
isdn outgoing-voice info-transfer-capability 3.1kHz-audio
isdn static-tei 0
isdn skipsend-idverify
trunk-group ALL_BRI 64
!
[...]
voice-port 0/1/0
translation-profile incoming PSTN-IN
translation-profile outgoing PSTN-OUT
compand-type a-law
cptone DE
bearer-cap Speech
!
voice-port 0/1/1
translation-profile incoming PSTN-IN
translation-profile outgoing PSTN-OUT
compand-type a-law
cptone DE
bearer-cap Speech
!
voice-port 0/2/0
translation-profile incoming PSTN-IN
translation-profile outgoing PSTN-OUT
compand-type a-law
cptone DE
bearer-cap Speech
!
voice-port 0/2/1
translation-profile incoming PSTN-IN
translation-profile outgoing PSTN-OUT
compand-type a-law
cptone DE
bearer-cap Speech
----
Hope this helps. Any help / idea is appreciated.
cheers
ekki
05-23-2012 09:42 AM
Remove this:
rule 1 /^93211$/ /22/
and should be ok.
The reason is that the router has no way of know that more digits are coming, so it applies the translation meediately.
In other words you have to configure for the complete number, not just part of it.
Ans, you cannot to have number overlap.
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: