Is it normal to have a new open ticket for 2 days?

**VOIPoTim** · 09-08-2009 04:47 PM

In this situation, it sounds like we're waiting to hear back from an upstream carrier. Our system doesn't modify the Caller ID in any way so it sounds like we're passing the correct CID info and the carriers delivering the calls are changing it so it could take a while to hear back from them.

If it would be a fix on our end it would be a lot quicker, but sometimes other carriers do respond kind of slowly.

I'll look up the ticket and have someone call you with an update.

**gls101** · 09-10-2009 06:32 PM

Just a quick update. Through testing with Brandon yesterday, it was determined that this is NOT a problem caused by Voipo.

I have my existing ATTCV number forwarded to my Voipo number while evaluating Voipo as a replacement. It seems that every time a Private (as in, the caller is not allowing CID to be sent) call is received via the CV number, CV or some other intermediary carrier is inserting a fake CID number. It's always the same number, and it is 1 DIGIT AWAY from the CV "Control By Phone" number! It's truly bizarre! The same call placed directly to the Voipo number works correctly.

Brandon Is escalating to AT&T, trying to find out what's going on, but I suspect they won't be very motivated to do anything about it, since they won't be around much longer.

So this particular "problem" isn't.

I do have one other critical issue, which I'll save for another thread.

Much thanks to Brandon for your patience and troubleshooting skills. They are recognized and appreciated.

Gary

**fisamo** · 09-11-2009 12:14 PM

Glad to hear that things are going well overall. That's an odd situation, though, as I don't recall hearing any other CV customers having such an issue. (As a CV refugee myself, I can say that I didn't notice that issue.) Then again, I don't get many 'private' calls...

**Warus1** · 09-12-2009 05:35 AM

Originally Posted by fisamo

Glad to hear that things are going well overall. That's an odd situation, though, as I don't recall hearing any other CV customers having such an issue. (As a CV refugee myself, I can say that I didn't notice that issue.) Then again, I don't get many 'private' calls...

FWIW: Ditto, CV refugee, not many private calls.. have not noticed the issue

**gls101** · 09-12-2009 09:44 AM

Originally Posted by fisamo

Glad to hear that things are going well overall. That's an odd situation, though, as I don't recall hearing any other CV customers having such an issue. (As a CV refugee myself, I can say that I didn't notice that issue.) Then again, I don't get many 'private' calls...

After I port to Voipo I suspect I won't see the problem any longer.

It seems to be caused by CV forwarding to Voipo. CV is modifying the CID data before routing the call.

After porting, the call data wouldn't be under CV's control, thus not subject to CV modification, so I think the "problem" will simply disappear. (I hope

)

Gary