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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office first call doesn't connect after system has been inactive

Status
Not open for further replies.

Jimbo2015

Technical User
Nov 9, 2013
317
GB
We are having a strange issue with a customers system. If there has not been a call for a while the first call to the system (inbound) does not connect. The person calling in to the system gets a constant ringing but then if they call again it does the usual 6 rings then goes to voicemail.

Any idea what could be causing this?

TIA,
 
Since you can't describe the system, the phones, the type of lines or anything about the routing - not really.

Stuck in a never ending cycle of file copying.
 
Ok it's an Ip500 v2 on release 9.1 with 9611G handsets. The lines are SIP lines. There is also a watchguard in place.
 
ALG in the watchguard off?

that is the first thing that always comes to my mind when any SIP issue happens.

Also the firmware of the watchguard, I had a firmware that was nasty when implementing QoS on the watchguard firewall (was around 2015 though)

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
Reregistration. Find out what the expected reregistration timer is from the carrier and match it or reregister before their timer expires.
Manager/ Lines/sip/account details reregistration timer.

Hail the tripod!
 
Keepalives


Do things on the cheap & it will cost you dear
 
Thanks for the help here.

SIP ALG on the watch guard was already off. I'm sure it's not the firmware but may change this if nothing else comes up.

The registrstion settings are correct. Keep alive settings are all as they should be at RTP - RCP at 10 seconds.

I have tested again this evening when the system is not in use and the first call took ages to do anything and then went to busy. The second call went through fine.

The customer also finds that long calls disconnect after 15 minutes and I guess these two issues are related.

Any other ideas? Does anyone else have any other suggestions for settings that can be changed on a watch guard and Avaya, I am confident that the watchguard is causing this but time will tell.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top