Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Question about Incoming Call Route and inter-digit timeout

Status
Not open for further replies.
Alfalis

Alfalis

Technical User
Oct 15, 2012
250
DE
Hi,

is there a way to force an IPO to wait for additional digits over an E1 before routing the call?
With Cisco CM there seems to be a timer "T302" for exactly that matter but I can't find a similar setting for IPO.

The basic problem is that if a caller is overlap signalling the number he wants to call sometimes IPO starts routing the call before it receives the complete number - sometimes even resulting in a complete disconnect for the caller.


I hope you know what I mean and can help me with my problem

bw
Alfalis

ptc.png

- ACSS

IPC - Very convenient tool for IPO admins

IPO Call Logger - Customizable Call Logging Utility
 
Sort by date Sort by votes
The number should be en-bloc well before it reaches you, or is this a tie line between 2 systems? Never heard of this issue before :)

 
Upvote 0 Downvote
I thought so..
No it's not a tie line between two systems. The problem only occurs when the caller is using an old analog "home" line.
I already called the service provider (Deutsche Telekom) to see if they can "force" en-bloc on my customers line but they declined and said it wouldn't be possible.

For now I've implemented a fallback routing for all incomplete or wrong numbers to the main operator but I can understand my customers anger about this issue.

Any ideas for some kind of workaround or fix?

ptc.png

- ACSS

IPC - Very convenient tool for IPO admins

IPO Call Logger - Customizable Call Logging Utility
 
Upvote 0 Downvote
You could try using a - in front of the DDI numbers, this causes a left-to-right match so should hold off until a full match :)

 
Upvote 0 Downvote
Bear in mind DDIs must match the exact length they send you or it will now work :)

 
Upvote 0 Downvote
They probably use DISA and then you need to add the - in front of the number in the incoming call route.
Only then this will work.


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
I already added the "-" for exact length comparison so no luck there.. :(

Example routing:
-918xxx -> #
-9180 -> Operator

In this case incomplete incoming numbers like 9182 or 91820 (203 being the number that was originally dialed) IPO would either cut the connection right away resulting in an announcement from the provider ("The number you have dialed is temporarily not available....") or the caller would just get a dial tone without the IPO actually routing the call anywhere (in this case the call was not even showing up in SSA)

My "solution" for now is an additional fallback routing:
nothing -> Operator

That way no calls get lost and you at least get through to the operator and can be trandfered but as you can imagine my customer is not completely happy with that solution.

ptc.png

- ACSS

IPC - Very convenient tool for IPO admins

IPO Call Logger - Customizable Call Logging Utility
 
Upvote 0 Downvote
It's the line providers issue though, for them to fix. They shouldn't be sending routing digits overlap to you, just let the customer know that :)

 
Upvote 0 Downvote
Seems to be the only option at this point because if amriddle01 and tlpeter don't have a solution I guess there is none ;D

I'll give the provider another call and see what I can do - Thanks for your help guys!!

ptc.png

- ACSS

IPC - Very convenient tool for IPO admins

IPO Call Logger - Customizable Call Logging Utility
 
Upvote 0 Downvote
I have to agree with amriddle & tlpeter
this is a provider issue.
It cannot be due to the old pots customer dialing slowly.
Simple logic, How does the network know to route a call to your site whilst the number is incomplete?



A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
 
Upvote 0 Downvote
Alfalis, I had the exact same issue with an ISDN (BRI) from Deutche Telecom, got zero help from DT, the ticket has been open for 2 years now.
And strangely enough, the problem was calls from analogue (Hamburg) + long distance (Berlin, Frankfurt, etc), while international was OK.

I solved it in ICR. DT have some strange numbering plans, main number is a digit shorter than DDI's and they use DISA as Peter assumed, so a minus is needed.

I'll find the config for you later today, didn't bring my laptop to the beach :)

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Upvote 0 Downvote
Well I guess as soon as the "main line number" (I don't know the english term, I hope you know what I mean xD) reaches the provider all additional digits are routed to this line.

So for example 01234 / 918 - xxx with all numbers from 0 to 999 belonging to the customers line, it could be possible that as soon as the provider gets 1234918 (call type national) it is obvious where you want to call so the connection is established.
From that point on the IPO has an incoming connection but no additional digits for the extension so the call is disconnected.

Not the perfect technical explanation but that is how far my english got me ;D

ptc.png

- ACSS

IPC - Very convenient tool for IPO admins

IPO Call Logger - Customizable Call Logging Utility
 
Upvote 0 Downvote
The IPO finds a match before it has read all numbers, passing the call to the destination in your ICR. This is the DISA's doing.

So, relax, have a beer and in a couple hours you get the config template (or maybe someone else on the forum will beat me to it)

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Upvote 0 Downvote
What you need to do is just add the numbers.
Example

011-12345 is the main number but they also have these:
011-1234501
011-1234502
011-1234503

Then you need to add them all in the incoming call route with a - in front.
The best match wins.


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
Good idea and maybe it will work (will have to test it next week) but wouldn't 011-12345 always be a match IF all numbers are sent one after another and not en-bloc? Or is there some kind of "timer" which makes the IPO wait for more after each incoming digit?

ptc.png

- ACSS

IPC - Very convenient tool for IPO admins

IPO Call Logger - Customizable Call Logging Utility
 
Upvote 0 Downvote
The provider must send all digits in one go or there will be a best match before all digits are send.


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
Alfalis, you got mail.

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

finest
  • Locked
  • Question
Incoming call route to match extension 1
Replies
5
Views
914
Qzwsa
Qzwsa
JMC1
  • Locked
  • Question
No Audio on Calls going pointed straight to user in incoming call route
Replies
5
Views
799
Ekster
Ekster
john3voltas
  • Locked
  • Question
Avaya Call Reporting (Web) - session timeout
Replies
6
Views
579
john3voltas
john3voltas
tetratech
  • Locked
  • Question
Incoming Call Routes vs Users SIP details tab
Replies
1
Views
294
IPGuru
IPGuru
BerettaGuy
  • Locked
  • Question
Incoming Call group and appearance buttons.
Replies
4
Views
440
BerettaGuy
BerettaGuy

Part and Inventory Search

Sponsor

Back
Top