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!

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

IP Office outcalling delay?

Status
Not open for further replies.

Jerrberr

Technical User
Aug 14, 2006
95
US
Good Afternoon all,
I have an IP Office r8.2 with embedded VM and two ATM combo card and analog lines in ( from Comcast)
The problem is a 7-9 second delay when calling out. If i do a forced "enter" with the # on the end of the dialing then the call completes in 3 seconds. If i let the IP Office run its protocol its the 7-9 second delay.

As of now i have:
- set the lines to Loop start instead of iclid
- set the "await dial tone" in telephony to 500ms
- removed the [highlight #FCE94F];[/highlight] (semicolon) from the ARS tables
- attempted to add [highlight #FCE94F];[/highlight] to the 9N shortcode
- turned down dial delay to 1 sec
- turned down ring delay to 1 sec
- added in XXXXXXX; /N / Dial 3K1/ 0 to ARS tables
- added in XXXXXXXXXX; /N /Dial 3K1/ 0 to ARS tables

restarting each time, but nothing seems to change the delay.
anyone have anymore bright ideas? Or a new bottle of whisky, Advil or other mind numbing alternatives?

I appreciate any help Thanks

Jerrberr
 
I need to revise the terminology a bit, I am attemting to "call out" on a normal call. Not use what was refered to as "outcalling" in earlier AVAYA lines. Sorry if that was confusing.

Jerrberr
 
Only have the ; in ARS not system shortcodes, ARS also has it's own dial delay timer (if you didn't know).

For testing make a code off -

SC - 123456
Feat - Dial
Tel number - your cell/mobile
line group - a valid external number for testing

Dial 123456, does it ring your test number with the correct delay?

If so it's your programming not the IP Office :)

 

amriddle01 (Programmer) Frustration has humbled me ,I surrendered to the fact its my programming a long time ago, just trying to fix it now.
I set up the short code as you posted, it rings but its a 9 sec delay still.

I had already set the ARS delay to "1" (sec) so i think that is as short as it will allow.
I also understood in ARS the ; was for PRI and SIP applications. ( could be wrong but thats what i understood)

Jerrberr
 
Did you go straight out the lines with the code above or via ARS? Try straight out the line group, if it delays by 9 sec it isn't the system it's the line delaying until you're sending # :)

 
I belive it went streight, the (test) shortcode is on the defaut "0" which analog 1-4 are assigned to.
the ARS is "50" or labeled "main 50" which is pointed at "0" line group.

I ran with both 0, and 50 on the test shortcode ,with the same result.

Jerrberr
 
Sure sounds like the delay is coming from the line then.... watch monitor. If it dials to line then there's a delay after that the delay isn't yours :)

 
i went that route at first but with a # at the end of the dial string, the call rings at 3 seconds, and I putin a trouble ticket with Comcast they tested and came back with no latency, a well as i used a test set and it is at about 2-3 second as a normal call should be. I have this issue at another site as well on a new system out of the box so its sitting in default settings but i caannot pin down exactly where....

Jerrberr
 
US locale systems have different (very different) default config to UK systems. Your line providers also seem massively varied in how they implement what should be a common/simple service. So I can't advise exactly as my testing will always vary from what you experiance anyway.....over to more US oriented Tek tippers :)

 
amriddle01 (Programmer)- Thanks for your help, i really aoppreciate your time and a fresh pair of eyes to help me dicount my level of insanity with this.

I have some other engineers emailed on this as well, if I get a solution I will post it, But i know there is others in the same situation, hopefully a master tech will see me here, floating helplessly lost at sea here and throw a tech a life preserver.. i hate when my post falls further into the abyss of the list unresolved... ha ha.
Jerrberr
 
Anyone else have any Ideas?

As of today I sent my config to another engineer and in his system he ran my configs and said the calls ring immediately. So it points me back to Comcast.. but on a test set it works immediately too! My next conclusion is voltage on the modem based Comcast lines against the voltage on a CO based phone line. Anyone think this would cause the IP Office to balk and cause a delay in ringing?
Jerrberr
 
How many short codes and users do you have? The usual 60-70 SCs and 1-60 users? Directory numbers- how many?

Is this a new install or something that magically started? Got a spare combo card to chuck in?

Hvis du kan lese dette, du snakker nok norsk.
 
Holdmusic, love your signature! Ha Ha[thumbsup2]

Kind regards

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

2cnvimggcac8ua2fg.jpg
 
You've only got two analogue lines. Have you set the other two to out of service?
Line> line setting> Admin> Out Of Service

Try setting a 10x short code to match your full national number as described here: thread940-1668587
I believe there may be enough information here to nut out what was suggested.

Thanks to Kyle.



Firewall Schmirewall
 
Don't think this is an isolated fluke issue... I have the same exact problem with a new install on Comcast trunks. They only have one combo card with 1616 IP Phones. We try to avoid Comcast digital trunks like the plague, however their PRI service is rock solid though. I am going out Monday to try and resolve this issue plus some others(echo [sad]).

Would love to get in on this effort to resolve the problem. This is our only IPO install that wasn't a PRI or POTS lines and go figure it's our only one with issues. I saw this issue before but like someone said above, make sure your unused trunk lines are disabled. I've also seen a line being plugged in that was dead (thought to be live) that caused almost a 10 second delay for outgoing calls.
 
That's already done through my ARS table. I have XXXXXXX - Dial 3K1 - N and 1XXXXXXXXXX - Dial 3K1 - 1N Same table as our own system on a PRI and calls route instantly.
 
If it's instant on other vendors trunks but not Comcast, it's just an incompatibility between Comcast and IPO. So no amount of config will change it, I would check the voltages on their trunks against a known worker, I would wager they are barely within the specs and the IPO isn't happy :)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top