Connecting Polycom video conferencing system to IPOffice 406DS

[wfaulk]

I have a Polycom video conferencing system, a VSX7000A. It is supposedly H.323 compliant. I also have an IPOffice 406 DS system running firmware 4.1(15), for which I've purchased a single "IP End-points" license.

I want the Polycom to be able to use the IPOffice to make audio-only calls on the PSTN, but I can't get it to work.

On the IPOffice, I defined a new VoIP extension with ID 8001 and extension number 1899. I set up the Polycom to use the IPOffice as a gatekeeper and to "log in" as extension 1899.

The Polycom claims to successfully register with the gatekeeper, and I can make calls to the extension apparently without problem.

However, if I make calls from the Polycom, they don't work. If I dial an internal extension, the phone rings, but when I pick up, there is nothing on the other end, and the Polycom continues to receive a ringback tone. If I hang up the Polycom, the called extension will immediately drop the call if it's a digital extension or emit a continuous tone with which I'm unfamiliar if it's an analog extension.

If I dial an external number from the Polycom, the Polycom receives a ringback tone indefinitely, but the called party never rings. A System Status trace shows that the outgoing line is picked up and immediately dropped.

I have some System Status traces for these calls:

trace of Polycom to internal extension
trace of called extension

trace of Polycom to external number
trace of PRI

I've also tried using the Netmeeting H.323 client in Windows XP (Start->Run->conf) with similar results, though when I hang up a half-connected call, the IPOffice gatekeeper frequently boots it out and it can't reconnect.

I have also tried to use the IPOffice system as a gateway instead of a gatekeeper, with similar results, and though it is more irritating to use that way, if using it as a gateway is a way to make it work, that's fine. The reason I say that is that, at one point, I got it working that way, and it seemed to work fine for a few days, but then stopped for some reason and I haven't been able to reproduce the success.

Polycom's H.323 config options:

This is the only VoIP client on the IPOffice (all of our phones are digital or analog), though there are a couple of VoIP trunks to other offices, which are also running IPOffice systems.

I'd very much appreciate any pointers anyone could provide me. I've been arguing with this for ages.

 

[Westi]

wfaulk
this is half the battle, finding the actual detailed cause and getting a workaround. Well done and if you get an answer from Polycom then please let us know then we can make this thread another one for the archive

Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[wfaulk]

I got this response from Polycom:

The VSX requires an Option Key to work with an Avaya network. Check with your reseller for availability and pricing. Also check the VSX Administrators guide for instructions on configuration:

http://www.polycom.com/global/docum...nce/products/video/vsx_series_admin_guide.pdf

see page 2-7 The VSX release notes also have information regarding Avaya networks. Please reference:

http://www.polycom.com/global/docum...nce/products/video/vsx_series_admin_guide.pdf

There is a comment in the release notes for the firmware version I'm running that sounds familiar:

When a V Series system or VSX system attempts to call another V Series system or VSX system through Avaya Communication Manager, the near-site system continues to ring if the far site rejects the call and has Auto Answer Point-to-Point Video or Auto Answer Multipoint Video set to No.

I'm not calling another Polycom, but the near side does keep ringing after the gatekeeper rejects the call.

Given that I can just transfer a call to the Polycom and that seems to work fine, I don't think I'll be capitulating to their nickel-and-dime sales tactics. I've told them as much, and requested that they reconsider their response, considering that they're asking me to pay for a license to disable a feature.