[WXC/VFX] VFX Caller ID suddenly screwy

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] VFX Caller ID suddenly screwy

RedJungle

Phil Gale
1108 posts

Uber Geek

Trusted

Red Jungle

Subscriber

#30205 1-Feb-2009 16:48

Hi folks,

An odd issue has popped up this week on my VFX lines. Inbound caller ID has started appearing with '0500' in front. i.e. rather than 6870XXXX, I'm getting 05006870XXXXX.

Any thoughts on why this has started to happen? Nothing has changed at this end.

hairy1

3332 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#193267 1-Feb-2009 18:40

I am sure something has changed at the Xnet end as all the email call notifications have the format 9****** instead of 09****** (the 0 has dropped off the front) in the last couple of days. If you have a pansonic cordless you may be able to change the options for local numbers in the phone (sorry not in front of the phone at the moment). My caller id is fine when the phone rings though.

Cheers,

Matt

My views (except when I am looking out their windows) are not those of my employer.

chchmjr

66 posts

Master Geek

ID Verified

Lifetime subscriber

#193272 1-Feb-2009 19:16

I had the 0500 thing for 2 calls on Wednesday. Appeared on both the phone and email. Been OK since.
Michael

RedJungle

Phil Gale
1108 posts

Uber Geek

Trusted

Red Jungle

Subscriber

#193293 1-Feb-2009 20:55

Just had another one - this time an international number, but still with 0500 in front :/ Looks like it may be only effecting PSTN originated calls as a call from another VFX user came through correctly.

Oh, and it's definately not my phone / box here as the numbers are wrong in my call notify e-mails too.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#193298 1-Feb-2009 21:10

I finally got around to setting my divert for VFX this week (if my Asterisk box does down it diverts to my mobile) and noticed that when I rang my VFX number from my mobile I got a call on my mobile from +50021xxxxxx so there is definately an issue somewhere.

dimsim

848 posts

Ultimate Geek

Trusted

Lifetime subscriber

#195009 9-Feb-2009 22:32

I had the same thing last week, seems to have righted itself now so must have been a glitch at WXC.