[cisco-voip] What do you do when a telco doesn't seem to know what they're talking about? "Voice" PRI being used for voice and videoconferencing.

[Matt Slaga (AM)]

Secret code word:  'NTT does this without issue, do we need to switch providers?'

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Robert Kulagowski
Sent: Friday, November 04, 2011 7:49 AM
To: Cisco VOIP
Subject: [cisco-voip] What do you do when a telco doesn't seem to know what they're talking about? "Voice" PRI being used for voice and videoconferencing.



It may be the language barrier - I have an office that's moving in
Hong Kong (Wharf T&T is the provider), and we've been deploying our
Polycom video units with a cross-over PRI to the voice gateway at the
site, using the PRI to the telco as the path for video conferencing.
That's worked everywhere that we've deployed it (about 15 locations
now).

The provider says that the voice PRI can't be used for video.

We said,
"With our current ISDN PRI 'voice only' circuit, is it provisioned for
64Kbps Unrestricted Digital on each b-channel ?"

The Wharf T&T person says,

"
It is recommend to relocate yr existing IDAP (ISDN PRI) from yr old
office to the new office. It won't interrupt yr voice service.
But, u cannot use this IDAP for VC as it does not support this kind of
function. Normally, it takes 14 days for the voice service relocation
and I have already checked this site is ready for the IDAP (ISDN PRI
).

U are recommended to use BRI or internet service for the Polycom 8400 model.

It is a normal method for the VC in Hong Kong.
"

We've explained to them that all we need is that the PRI be configured
on their side for 64Kbps unrestricted digital, but they're putting up
a fight about this.

What's the secret code word that I'm supposed to be using here for
describing the provisioning of the new PRI? If we deploy per our
standard, then the Polycom HDX system will ship with a PRI module, and
if the PRI to the telco really doesn't work for VC, we then need to
get a BRI module and order BRIs for that site, and that will take
time. (And we'll have a PRI module that we can't do anything with).

I can't get a straight answer as to whether the provider is saying
that it can't be used for voice and video for technical reason, or for
administrative/political reasons.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111104/60262a4a/attachment.html>