how-to block ads
|
|  
unknvoip
WWJID?
join:2006-07-25
Rochester, NY
 ·ViaTalk
| Re: Broken record alert- Call logs 2 days behind Wow, you sure have problems with your call logs. What astounds me is the variability of the issue. For example, 8 calls in and out on my VT line yesterday, all logged properly, while you (and others at times) experience extended delays.
I can't say for sure how long it took for them to show because quickly looking up my recent calls in the log is not a priority for me, but I rarely have the delays that you do.
The occasions of call log delay for me have been few and far between. Last I checked, my server was Megatron - perhaps the server is the root cause of this.
Good luck. | |
| | 
dmolavi
Premium
join:2005-04-11
Sewell, NJ
 ·Verizon FIOS
 ·Comcast
·ViaTalk
| Re: Broken record alert- Call logs 2 days behind said by unknvoip  :Wow, you sure have problems with your call logs. What astounds me is the variability of the issue. For example, 8 calls in and out on my VT line yesterday, all logged properly, while you (and others at times) experience extended delays. I don't mind if they take 5 or 10 minutes, though there is no excuse for it to take that long, but as you can see from the screenshot above that I just took a few minutes ago, there hasn't been a new call posted in 2 days.
VT - WTF is up with this? I've been told that it doesn't matter what server I'm on, call logs are all handled the same way. FWIW, I'm on hightower. This is getting really old; this is probably my 3rd post in a month about this. In the waning days of my 2 year subscription with you, this doesn't leave a good taste in my mouth.
--
NukedGallery.net
TheMolavis.com | |
| | | 
dcurrey
Premium
join:2004-06-29
·ViaTalk
| Re: Broken record alert- Call logs 2 days behind Just did a quick check. Took 3 minutes for call to show up.
Wild guess but are you logged into the CP before you make the call? Wonder if they do some sort of lock tables on the database when you query it not allowing new entries to be in limbo for whatever reason. Databases might have to be synced to correct.
Don't notice this problem myself could be because I don't usually need to pull a number out from them. | |
| | | | |
dmolavi
Premium
join:2005-04-11
Sewell, NJ | wow, calls are now listed through yesterday...almost there... | |
| | | | | kdpo1990
join:2005-06-02
Bradenton, FL
| Re: Broken record alert- Call logs 2 days behind i've had same issue, and after i opened ticket they fixed it .
Call log
Hello,
I apologize for any inconvenience. It appears that the CDRs were queued for delivery and delayed. Please check back in the evening and the records should be up to date.
If there is anything else we may assist with, please let us know. Thank you. | |
| | |
dmolavi
Premium
join:2005-04-11
Sewell, NJ
·Verizon FIOS
·Comcast
·ViaTalk
| Re: Broken record alert- Call logs 2 days behind said by kdpo1990 :i've had same issue, and after i opened ticket they fixed it . Call log Hello, I apologize for any inconvenience. It appears that the CDRs were queued for delivery and delayed. Please check back in the evening and the records should be up to date. If there is anything else we may assist with, please let us know. Thank you. That is word for word the EXACT same message I received when they closed my ticket.
VTBrendan, what gives? Why is this happening so frequently to some accounts and not others? Why can't the system detect the occurrence and self-correct?
--
NukedGallery.net
TheMolavis.com | |
| | | | TexasPlus
join:2004-06-16
Bedford, TX
 ·Millenicom
·ViaTalk
| Re: Broken record alert- Call logs 2 days behind said by dmolavi :said by kdpo1990 :i've had same issue, and after i opened ticket they fixed it . Call log Hello, I apologize for any inconvenience. It appears that the CDRs were queued for delivery and delayed. Please check back in the evening and the records should be up to date. If there is anything else we may assist with, please let us know. Thank you. That is word for word the EXACT same message I received when they closed my ticket. VTBrendan, what gives? Why is this happening so frequently to some accounts and not others? Why can't the system detect the occurrence and self-correct? I was having this same "Days delayed problem" with my ViaTalk primary number, was also having the "Many calls going to busy" problem as well as the occasional "Hello Hello Hello Hello problem, but I found a sure fire fix for them all.
1) A few weeks ago I had ViaTalk Swap my Primary phone number with my Virtual phone number.
2) I signed up with VIOPo, and had them port my Virtual phone number to VIOPo.
I am happy to report that in the week or so since the port completed, I have not had a single re-occurrence of any of these problems on my ported number....
Alas the number left with ViaTalk still suffers from them all..... Oh well, say la vee, in a few weeks that to will no longer be a problem to me when my second painful year with ViaTalk runs out.... 
--
"The world is a book; those who do not travel read but a single page." -St. Augustine | |
| | | |
|
