|
 
unknvoip
WWJID?
join:2006-07-25
Rochester, NY | Re: sigh...call logs not working...again 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 | Re: sigh...call logs not working...again after 45 minutes, the calls in question finally appeared... | |
|
dcurrey
Premium
join:2004-06-29 | 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 | Re: sigh...call logs not working...again i've tried *BLK and it hasn't always worked. that was early on, though.. | |
|
| RogerD
join:2008-07-15
Sunnyvale, CA
| 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. | |
|
| | |
| |
dcurrey
Premium
join:2004-06-29
 ·ViaTalk
2 edits | 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" | |
|
| | | |
| | | |
dcurrey
Premium
join:2004-06-29 | Re: sigh...call logs not working...again If talking to me I am on galvatron server. VT supplied adapter provisioning off. | |
|
| | 
VTEric
join:2008-08-27
Clifton Park, NY
| 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. | |
|
| | | k2rj
Premium
join:2005-03-24
Solon, OH
·ViaTalk
| Re: sigh...call logs not working...again 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
| 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. | |
|
degauss1
join:2001-07-02
Hillsboro, OR | Mine's been working without issue. | |
|
RogerD
join:2008-07-15
Sunnyvale, CA
| 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 | Re: sigh...call logs not working...again 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. | |
|
| |
unknvoip
WWJID?
join:2006-07-25
Rochester, NY | Re: sigh...call logs not working...again 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. | |
|
| | |
unknvoip
WWJID?
join:2006-07-25
Rochester, NY
·ViaTalk
| 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. | |
|
RogerD
join:2008-07-15
Sunnyvale, CA | 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... | |
|
RogerD
join:2008-07-15
Sunnyvale, CA | 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. | |
|
RogerD
join:2008-07-15
Sunnyvale, CA
| As stated above, all I see is Answered or Failed in the call logs. I do not use Network Unavailable Failover since I almost never have an ATA/IP Phone connected and I want calls filtered/forwarded according to the settings.
Can anyone confirm that their call logs show calls going to VM or being forwarded (other than NUForward)? | |
|
|
dcurrey
Premium
join:2004-06-29
·ViaTalk
2 edits | Re: sigh...call logs not working...again Ok I did a couple of test.
Outbound Routing showed up
Blacklist showed up. Technically this should say forwarded. Had call from cell forwarded to another number
Voicemail showed up. | |
|
RogerD
join:2008-07-15
Sunnyvale, CA | Not seeing that detail. Submitted ticket...
Anyone else notice the lack of postings from VT people lately? | |
|
| |
| |
unknvoip
WWJID?
join:2006-07-25
Rochester, NY
·ViaTalk
| Re: sigh...call logs not working...again said by ptrowski :said by RogerD :Anyone else notice the lack of postings from VT people lately? The forum overall has been slow, so that may be one reason. Just a guess! It's been so slow that even the trolls have taken to PMs. 
Times like this make me think that some of the individual groups should be collapsed back into the general VoIP forum: »VOIP Tech Chat
The overall volume there is not that great either. | |
|
RogerD
join:2008-07-15
Sunnyvale, CA
| Ticket ID: MQX-71423
Got a response:
Even if you do not have a device registered at the time of a call, the call will be sent to the server to which you were last registered for processing. If you register a device to any of the aforementioned servers and then disconnect that device, you will see the correct enhanced portion of the call logs. I used the info shown for EyeBeam to configure my IP Phone (Chicago-6) and that appears to be why I'm not getting the new format.
Good response time! | |
|
RogerD
join:2008-07-15
Sunnyvale, CA
| Had a friend call and he's set up with Incoming Call Routing to another number. Call log shows as ANSWERED (Blacklist). I'm told that's how all calls setup with Incoming Call Routing is listed. A bit misleading, but at least unique.
My calls are not making it to VM so going to presume that work when fixed. | |
|
|
dcurrey
Premium
join:2004-06-29 | Re: sigh...call logs not working...again Might want to double check the CP to make sure they didn't turn voicemails off when looking at you account. If not try toggling the setting off then back on. | |
|
|
|
|
·
·
sigh...call logs not working...again
·