Page 1 of 2
Overflow issues
Posted: 18 Feb 2011 10:20
by tjm0852
I have 2 issues with call overflow. One inbound and one outbound.
The outbound issue obviously using ARS. I have second, third, fourth and fifth choices built but for some reason it skips my second choice and goes right to the third even though channels are available on my second choice route. If I delete the 3rd, 4th and 5th choice route it will take the 2nd. As soon as I add the third choice back it skips 2 and goes right to route 3. Anyone know what would cause that?
Inbound issue is as follows and is most problematic. I have my service provider using a trunk group overflow in case PRI to 1 node is unavailable overflow to another node. If I run a trace I can see the service provider passing the 4 digit extension of the station that was dialed. But the PCX returns an unallocated number error and forces the call to the attendant. I have the default did translator built to look for that other did and turn it into the internal extension I want it to ring. I can see that the internal extension is built, lives in the numbering plan and is shown as a station on the other node, but the call does not find the station. Is there something I am missing?
I can provide specific on the programming I have in place if needed. There seems to be something I am missing.
Thanks in advance for any help
Re: Overflow issues
Posted: 22 Feb 2011 12:37
by tjm0852
Just as a follow up. If I created a number assigned as a DID in node 2 in node 1 and call it the call finds it's ways across the network to the destination. Even though it is returning the same unallocated number in the t3 trace I am running. I am not so concerned about the outbound routing because it works and the call does get out. I am most concerned about the inbound.
Why doesn't a call get routed across my network to the correct node/station? There has to be something stupid I am missing. All my nodes are in the same Domain, all the stations are in the numbering plan. What could I be missing?
Any help would be greatly appreciated.
Re: Overflow issues
Posted: 23 Feb 2011 00:14
by sipmotor
Hello tjm0852,
you don´t seem to get many replies to your post, so i try to help.
Outbound Problem:
Are there 4 Qualitys added in the second Route? If you don´t add at least 1 Quality the Route won´t ever be selected. Are the time based route list options OK?
Is choice no. 2 a physical trunk? If yes, is it possible to dial outbound digit by digit on this trunk?
Inbound Problem:
Have you tried to erase the Station and then run an immediate broadcast? Which OXE Release do you operate with? There was a bug with "unallocated number" when the target extension has a wrong isdn service configured. What is the ETSI Release Code?
Good Luck an kind regards
Re: Overflow issues
Posted: 23 Feb 2011 02:58
by Eliott
Which OXE version do you use?
Re: Overflow issues
Posted: 23 Feb 2011 14:33
by tjm0852
sipmotor wrote:Outbound Problem:
Are there 4 Qualitys added in the second Route? If you don´t add at least 1 Quality the Route won´t ever be selected. Are the time based route list options OK?
Is choice no. 2 a physical trunk? If yes, is it possible to dial outbound digit by digit on this trunk?
Inbound Problem:
Have you tried to erase the Station and then run an immediate broadcast? Which OXE Release do you operate with? There was a bug with "unallocated number" when the target extension has a wrong isdn service configured. What is the ETSI Release Code?
Good Luck an kind regards
Eliott wrote:Which OXE version do you use?
4400 running release 9.0, patch 30 on most sites and patch 43 on one site.
I have speech quality selected for all my overflow route choices. Not using any time based route lists, so I believe they are all set to 1, but I will double check. Choice's 2, 3, 4 and 5 are physical trunks but located on other nodes on my network. I can use a trunk group seizure prefix and go out, I just wonder ARS is not selecting my 2nd choice and skipping to my 3rd.
Could the NPD Identifier have anything to do with it?
Can you give me some detail about the unallocated number bug you reference?
What is an ETSI release code? I have never heard that terminology before.
Thanks
Re: Overflow issues
Posted: 24 Feb 2011 05:05
by Eliott
What is an ETSI release code? I have never heard that terminology before.
The release code e.g. NORMAL CALL CLEARING and so on => 90 = [1]001 0000 = 16 = Normal call clearing
Code: Select all
______________________________________________________________________________
| (106614:010379) 2419: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : 00 11
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
______________________________________________________________________________
| (106615:010557) Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 2 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 80 11
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
another sample d8 = [1]101 1000 = 88 = Incompatible destination
Code: Select all
______________________________________________________________________________
| (923754:014535) 1274: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 3 cpl: 22 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : a5 40
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 d8 -> [d8] INCOMPATIBLE DESTINATION
|______________________________________________________________________________
Re: Overflow issues
Posted: 24 Feb 2011 16:04
by tjm0852
The trace in the alternate route location (inbound call) has been showing unallocated number. I will have to test it again one night to show the full, exact message. I see 4 digits passed from the provider and then the unallocated number message. I am really not sure why it returns an unallocated number error when I have those extensions built in the translator and they live in the numbering plan.
Re: Overflow issues
Posted: 25 Feb 2011 02:11
by Eliott
Number of digits unused?
Re: Overflow issues
Posted: 25 Feb 2011 09:44
by tjm0852
Number of unused digits for what? Outbound? I have it set for 0 digits to be removed on all outbound routes.
What is the preempter?
For inbound the carrier is sending me 4 digits. I am translating them into 5.
Re: Overflow issues
Posted: 28 Feb 2011 12:29
by tjm0852
Anyone know about this unallocated number bug?