PVX w/ Tandberg Border Controller Q

[sully127]

Hi everyone,

I already looked around and didn't see this specific question so sorry if it was asked:

Is it possible to register PVX with a Border Controller? I am able to register it internally to my Gatekeeper (internal IP), but it errors out ("rejected by gatekeeper") when I try to register it to my Border Controller (external IP, but pingable from network,and endpoints are able to register directly)

Any help?

[robertk]

No you can not register a PVX with a Border Controller.

PVX doesn't have support for H.460-18/19 (Or TANDBERGs ASSENT protocol) wich is required to register with a Border Controller.

//Robert

[sully127]

Okay; thanks for the reply.

Do you guys think it makes sense to NAT a public IP to your Gatekeeper so that PVX can work remotely?

I'd use VPN, but I would think connecting through the Internet would be less bandwidth constrained than VPN

Anyone have a setup that they wouldn't mind discussing? I'm just trying to come up with the best performing, logically sound way of doing this.

Thanks

[Boris]

Hi everyone,

I already looked around and didn't see this specific question so sorry if it was asked:

Is it possible to register PVX with a Border Controller? I am able to register it internally to my Gatekeeper (internal IP), but it errors out ("rejected by gatekeeper") when I try to register it to my Border Controller (external IP, but pingable from network,and endpoints are able to register directly)

Any help?


Border controller - no. You can register it on VCS Express way, or on TANDBERG Gatekeeper, and GK register as neighbour on BC.

[JFCOMEngineer]

Okay; thanks for the reply.

Do you guys think it makes sense to NAT a public IP to your Gatekeeper so that PVX can work remotely?

I'd use VPN, but I would think connecting through the Internet would be less bandwidth constrained than VPN

Anyone have a setup that they wouldn't mind discussing? I'm just trying to come up with the best performing, logically sound way of doing this.

Thanks


If you have a Tandberg gatekeeper, then register the PVX to the GK, and the GK to the BC. Maybe I missed something, but that is the recommended mode of operation

[nozzer]

The problem with a PVX registering with a Tandberg Gatekeeper only occurs with firmware release N6.0 or later for the gatekeeper. The PVX does not think the registration is successful, however the gatekeeper does. So you are able to call the PVX using e.164 but the PVX cannot because it doesn't think it is registered. Rollback to version N5.1 on gatekeeper to get things working again.