Extensions going in and out of service

[twitchy087]

Hey All,

I have an IPO SE 9.1.5 working in tandem with BBX Vuesion. We constantly have random issues with phones going in and out of service, per the TAPI messaging sent to Vuesion. This is causing all sort of mayhem as sometimes the extensions simply never completely re-establish their connection. Vuesion then cannot properly work with the extensions, even though the desk phones seemingly are working 100%. BBX states that this is not an issue anywhere else and that their software simply works with what it is given by the IPO, which is fully understandable and appreciated.

My question to you guys -- is there any hidden setting on the SE which I may be missing which could cause these phones to go in and out of service? If not then I can only imagine that it is an issue with the network and/or the Virtual Host which the system resides on. I appreciate any input.

Here is a part of the Vuesion log which I am referring to;
02/26 13:42:13 User Ext:1100 Base Ext:1100 is IN SERVICE
02/26 13:42:13 User Ext:1138 Base Ext:1100 is OUT OF SERVICE
02/26 13:52:01 User Ext:4142 Base Ext:4142 is OUT OF SERVICE
02/26 13:52:01 User Ext:1860 Base Ext:1860 is OUT OF SERVICE
02/26 13:52:16 User Ext:4142 Base Ext:1860 is IN SERVICE
02/26 13:52:16 User Ext:1860 Base Ext:1860 is IN SERVICE
02/26 13:59:26 User Ext:4234 Base Ext:4234 is OUT OF SERVICE
02/26 13:59:26 User Ext:4214 Base Ext:4234 is OUT OF SERVICE
02/26 13:59:31 User Ext:4234 Base Ext:4234 is IN SERVICE
02/26 13:59:31 User Ext:4214 Base Ext:4234 is IN SERVICE
02/26 14:11:25 User Ext:1138 Base Ext:2023 is IN SERVICE
02/26 14:13:54 User Ext:1946 Base Ext:1946 is IN SERVICE


Thanks!!

 

[intrigrant]

Are these twinned extensions?

 

[twitchy087]

These are not twinned extensions and so far I have not been able to see such messages via monitor however we are going deeper into it. The log shown is pulled via tapi messaging.

 

[Okkie26]

What type of extensions?
How are IP addresses given to the extensions?
Correct firmware for the extensions present on the file server?
DHCP setup correctly?
Option 242 available?
VLANs setup on the switches?

Could be a lot of issues...

We need more info.

 

[twitchy087]

H323 extensions with direct media off as a requirement for Vuesion recording.

DHCP

The firmware is correct

I am of the belief that DHCP is correctly setup however that would depend on your definition of correct. Are you looking for specific lease times?

Option 242 is setup across the board

VLANs are set up across the board for voice.

Another lovely detail; it is not our network and have little visibility into it....

Appreciate all of the input.

 

[Okkie26]

My wild guess. IP conflict...

 

[sizbut]

If I read the original description correctly, there is no problem on the IP Office telephony side - the phones are working okay to make and answer calls - correct?

The problem is on the TAPI output side from IP Office SE (or possible the TAPI receive side of BBX).

Had to ask as the answers are already descending into phone installation diagnostics when that isn't the issue.

A quick summary of your SE system would help. Is it just a single primary server or multiple servers? I'm not sure if IP Office TAPI has ever supported extensions that are on different IP Office servers in a network.

Stuck in a never ending cycle of file copying.

 

[derfloh]

I'm not sure if IP Office TAPI has ever supported extensions that are on different IP Office servers in a network.

Not officially but it works. But who knows how long? You have to create a NoUser source number on primary server and you have to change a registry value on Windows machine where you installed third party TAPI. After restarting telephony service you can use all TAPI lines from all nodes.

It is documented in CIE admin guide R3.1

 

[intrigrant]

If BBX Vuesion is a Avaya DevConnect partner they best report this there and leave it to Avaya to dig into this.

 

[twitchy087]

Sizbut,

You are correct in that all standard Avaya telephony seems to be operational during troubled periods and that the issue is either withe tapi output or something behind the scene which is forcing the tapi to output such a message. The IPO is a single Primary non select server running on a VMware environment.

Intigrant,

They are a devconnect partner and you are correct in that I may ultimately need to go down that road. I am sure you know how painful and sometimes very useless that road can be. I am attemtping to avoid opening a ticket which wastes a ton of my time and goes nowhere.

We shall see....

 

[intrigrant]

My advise: try different versions of TAPI, it may be version specific aka a bug.