Sam the Deaf

Issues with local number from VP200 to ZVRS (and Purple, too)

General, I'm Deaf, Wireless

I use ZVRS Z4 app for my iPod Touch (4th-gen model) to make call to anybody with Video Relay Service (VRS) or point-to-point. I like to have both VRS and personal leave message in video, which is cool. Even I get my own Local Number, it make a real deal.

For quite time, I start to concern on how people are start to call me. There is a major problem with Sorenson compatible with different video relay service. It’s about the how the caller ID appears toward Sorenson VP200.

You see, when I test it by call from my Z4 to my VP200. You can see how wrong when it appear on the display from the history call listing. What’s wrong? It doesn’t appear as the local number. It’s only ip-address. When anyone, like me on VP200, tried make the redial from either history call listing or contact listing after add my “caller id”. It will dial as Ip-address instead the actual local number. It ends up bringing you to where you would only leave the video-message. It will NOT ringing to my Z4 from iPod or laptop.

What has hassle me is, that I have to remind everybody to make sure they add my Caller ID and then edit to change from Ip-address to my local number. It’s more work for them to do than simple add from the history call listing.

I find it un-compatible between videophone Service Company to videophone Service Company. They’re not well equal when someone miss the call and redial as number instead being different direct. I could blame to Sorenson.

So, I leave the feedback to ZVRS to be aware about my issues. I hope to see every videophone service to be equal on quality on video and satisfactory to call like every telephone Landlines/wireless Company does.

UPDATE: It also affect on Purple P3, too. I gave the feedback to Purple Staff, too.

Related Posts

  • Ian Blenke

    First, a warning: I am an engineer at ZVRS.  I am not representing ZVRS in this comment, and this only reflects my own personal opinion. I will attempt to stick to the facts involved here.

    Purple, Snap, ZVRS, and other providers use something called “server based routing”. It is important that VPs H.323 signal both their identity (Q.931 callingPartyNumber and H.225 sourceAddress dialedDigits), as well as the VP that they are trying to call (Q.931 calledPartyNumber and H.225 destinationAddress dialedDigits).

    The problem here is that the VP200 has a pretty severe bug: it will only
    return a call in its call history by IP address, and it does _not_
    signal the calledPartyNumber when doing so.

    Purple, Snap, ZVRS, and pretty much every VP other than Sorenson use some form of SIP to H.323 gateway to originate VP calls per the iTRS database, which requires H.323 calling by IP address today.

    This means that all of these providers originate from one or two gateway IP addresses from their platforms. This is fine so long as the VPs honor the call signalling phone numbers when placing calls. The VP200 does not.

    So, when a VP200 places a return call from its call history, it makes an H.225 connection to the provider’s gateway, but it does not signal who it is trying to call.

    ZVRS has something called ZConnect that should have made your call work. If your Z  phone doesn’t have a ZConnect assigned, the call wouldn’t have originated from your Z phone’s ZConnect IP address, so the return call from the VP200’s call history wouldn’t have worked. You should contact ZVRS Customer Support and make sure your Z phone has a ZConnect IP address assigned to it.

    As for the other providers: they do not have anything like ZConnect, so they have problems with return calls from the VP200. It isn’t really their fault, it is Sorenson’s broken VP200 firmware doing the wrong thing.

    The VP200 has numerous other “features” as well, which you haven’t directly asked about, so I won’t get into in this comment.