dmolavi
Premium
join:2005-04-11
Sewell, NJ
 ·Verizon FIOS
 ·Comcast
 ·ViaTalk
1 edit |  sigh...call logs not working...again
my wife called me this morning asking me to block two numbers that called a total of 6 times in the past 30 minutes. neither of the numbers is appearing in the call logs, though. the last entry i have in my logs is from 7PM last night. the outbound call she made to me is not listed, either. is anyone else seeing longer than normal log latency (or non-functioning logs)?
Edit - A small aside here...my renewal is coming up, and basic things like call logs not working don't sit well. I like VT and the features that are available, but they need to work to make it worth my money.
--
NukedGallery.net
TheMolavis.com |
|
unknvoip
WWJID?
join:2006-07-25
Rochester, NY | No problem here. Just called home and my call showed up in the log within a couple of minutes. |
|
dmolavi
Premium
join:2005-04-11
Sewell, NJ | after 45 minutes, the calls in question finally appeared... |
|
dcurrey
Premium
join:2004-06-29 | reply to dmolavi
I just did my first call will update if it takes a long time to find its way into the log.
She could have used *255 (BLK) Blacklist last incoming number.
Number showed up while I was posting this so its under a minute. |
|
dmolavi
Premium
join:2005-04-11
Sewell, NJ | i've tried *BLK and it hasn't always worked. that was early on, though.. |
|
RogerD
join:2008-07-15
Sunnyvale, CA
| reply to dcurrey
said by dcurrey  :... She could have used *255 (BLK) Blacklist last incoming number. ... This begs the question, where does *255 get its info as to what number to block? If it comes from your call logs I can see it blocking the wrong number and you'll never know.
I know it sounds simple, but if someone from VT could shed some light on the process *255 uses and why it might take a long time for call log entries to show up, it might help ease some frustration. |
|
dmolavi
Premium
join:2005-04-11
Sewell, NJ
·Verizon FIOS
·Comcast
·ViaTalk
| this is exactly what happened when i used it the first time...it tried to block the number *before* the number i wanted to block, presumably because i performed the *BLK as soon as I hung up, and the offending number hadn't made it into the call logs yet...with a 5-10 minute delay in logs, this is kinda useless.
--
NukedGallery.net
TheMolavis.com |
|
dcurrey
Premium
join:2004-06-29
·ViaTalk
2 edits | reply to RogerD
I just tested this with my cell. First time ever using it.
Once you hit *255 a recording will read back the number and you press 1 to confirm. Did check call logs number hadn't shown up yet. So I think I beat the logs. Did show up a minute later. Also dialed *255 right after I hung up.
In inbound call routing it list the number as blocked with the name "BLOCKEDFROMPHONE" |
|
dmolavi
Premium
join:2005-04-11
Sewell, NJ
·Verizon FIOS
·Comcast
·ViaTalk
| are you using a VT ATA, and what server are you on? neither of these should make a difference, but, you never know...
--
NukedGallery.net
TheMolavis.com |
|
dcurrey
Premium
join:2004-06-29 | If talking to me I am on galvatron server. VT supplied adapter provisioning off. |
|
VTEric
join:2008-08-27
Clifton Park, NY
| reply to RogerD
The *BLK (*255) feature does not pull the last number that called you from the call logs. Every time you receive an incoming call the number of your last caller is updated and stored in a variable which will be accessed by this star code. This variable is updated as soon as the call hits our servers so regardless of if you answer the call that variable would be updated immediately. |
|
degauss1
join:2001-07-02
Hillsboro, OR | reply to dmolavi
Mine's been working without issue. |
|
k2rj
Premium
join:2005-03-24
Solon, OH
·ViaTalk
| reply to VTEric
said by VTEric :The *BLK (*255) feature does not pull the last number that called you from the call logs. Every time you receive an incoming call the number of your last caller is updated and stored in a variable which will be accessed by this star code. This variable is updated as soon as the call hits our servers so regardless of if you answer the call that variable would be updated immediately. Yes, you can see the last number dialed and received (on both lines, if they are different) on one of the pages when you log into the adapter. |
|
RogerD
join:2008-07-15
Sunnyvale, CA
| reply to VTEric
said by VTEric :... Every time you receive an incoming call the number of your last caller is updated and stored in a variable which will be accessed by this star code. Does this include calls to a Virtual Number or SIP Dialed? I recall reading another thread where Virtual Numbers are not processed the same as to primary. |
|
RogerD
join:2008-07-15
Sunnyvale, CA
| reply to dmolavi
I just set up Custom Call Routing to send a caller to a real number. Those calls do not show up in the call logs as either inbound or outbound. I'm presuming if I was forwarding to a international number that I would be billed for the call. Shouldn't the call logs show what's happening? I know I'd be upset if I was billed for something that didn't show up.
Also, I've read a few messages about improved call status notations in the call logs. All I ever see is Failed if they hang up before being answered or Answered for everything else regardless of being answered, forwarded, or sent to VM. Is it really that difficult to properly show the actual call disposition? |
|
dcurrey
Premium
join:2004-06-29
·ViaTalk
1 edit | Showed up for me. Granted incorrectly labeled it as blacklist but it showed up.
You should be seeing blacklist, outgoing call routing, NUforward, and Voicemail.
Edit: after a couple quick checks it appears anything in inbound call routing gets tagged as blacklist in the logs except for forwards to voicemail. |
|
RogerD
join:2008-07-15
Sunnyvale, CA | reply to dmolavi
No, all I see is Failed or Answered...
Did a test of the Incoming Call Routing yesterday and it's not in the logs at all.
A VT constant is inconsistency... |
|
unknvoip
WWJID?
join:2006-07-25
Rochester, NY | reply to dcurrey
Calls have been showing up in my call logs just fine, but the 'enhanced' logs no longer work. No indication of any custom call routing treatment on some of the calls that I have filtered.
Come on, VT. let's get this straight, please. |
|
RogerD
join:2008-07-15
Sunnyvale, CA | reply to dmolavi
Re: sigh...call logs not working...again... still?
What's happening with the "enhanced" call logs? All calls are still showing as either Answered or Failed regardless of the call being forwarded or blocked. |
|
unknvoip
WWJID?
join:2006-07-25
Rochester, NY
·ViaTalk
| reply to unknvoip
Re: sigh...call logs not working...again
I just wanted to follow up that it seems the issues with the enhanced call logs seem to be worked out. I received a call on my cell today I didn't expect I would get. Turns out there was an internet interruption at home and the call was forwarded to my failover number (my cell).
A check of my logs show an indicator of the call and that it went to 'NUForward'.
On a side note, the Network Unavailable Forwarding is just about the most important feature to ensure we can still get calls when the Power or Cable company's lines crap the bed. |
|
