dcurrey
Premium
join:2004-06-29 | reply to dmolavi
Re: sigh...call logs not working...again
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. |
|
k2rj
Premium
join:2005-03-24
Solon, OH
·ViaTalk
| 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. |
|
