Caller ID Format

Forums › New Zealand Broadband › Caller ID Format

ajobbins

5052 posts

Uber Geek

Trusted

#6744 20-Feb-2006 17:30

Just started using Woosh Phone in Wellington. I really don't like the way they format the Caller ID. Eg. They drop the leading 0 from the phone number, which is fine EXCEPT My phone won't associate a name stored in the phone book with a number on the Caller ID unless they numbers match exactly (and of course I want the leading Zero in the phone book. This also means I cannot return a missed call without first writing down the number. It also seems to be sending through a 'Name' with the Caller ID. This seems to be (From my testing from my 027) the number then an underscore and then the start of the number repeated again eg 271234567_271 for Name and 271234567 for Number.

Annoying!

Twitter: ajobbins

1 | 2

Hawkes Bay
8476 posts

Uber Geek

Retired Mod

Trusted

Lifetime subscriber

#28889 20-Feb-2006 18:45

Make sure you (and anyone else having this issue that doesnt like it), lets them know - it could be an easy fix, but may never know if you and others dont tell them.

Andy_Walker

89 posts

Master Geek

#29385 26-Feb-2006 19:09

I had the same isue & it was an easy fix. I was able to fix it because my phone has an option to add the zero on the incoming number (Uniden FP106). As was pointed out to my in another thread here the '0' is not actually part of the number but a dialing prefix code.

Take a look at the options on your phone and you might find the option to add an incomming '0'.

ajobbins

5052 posts

Uber Geek

Trusted

#29386 26-Feb-2006 19:35

I have a Uniden DECT1825. Can't find it in the options anywhere

Twitter: ajobbins

ajobbins

5052 posts

Uber Geek

Trusted

#29526 28-Feb-2006 18:10

About the same time as the format of Caller ID 'Name' dropped the _XXX at the end I recieved this e-mail from Woosh:

"Dear Adam,

We have tested the caller ID service and cannot find any issue with the prefix being omitted during an incoming call. This could possibly be a feature setting related to your telephone in which you may have to refer to your manual or supplier for support."

So they have fixed 1 part of the Caller ID, BUT STILL NO '0' Prefix. I have e-mailed them to tell them this it is definately not a problem with my phone (as I have more than one and they all worked fine with TCom Caller ID)

Twitter: ajobbins

Andy_Walker

89 posts

Master Geek

#29530 28-Feb-2006 19:29

Try this! divert calls to your mobile & see how they display there. If they appear woith the 0 prefix then you know it is a phone issue. If the 0 is still emitted then it must be a Woosh issue.

ajobbins

5052 posts

Uber Geek

Trusted

#29565 1-Mar-2006 09:54

Not necessarily because if I divert to Mobile the caller ID is formatted by Telecom before it reaches my phone. Even so, Woosh may be putting the leading zero on outgoing calls but not on incoming. This is definately not a phone issue as it worked perfectly fine until I plugged it into the woosh gateway. Remember we arent just talking one caller ID phone here we are talking 4. All have the same issue and none had the issue prior to being plugged into the gateway.

Twitter: ajobbins

ajobbins

5052 posts

Uber Geek

Trusted

#29567 1-Mar-2006 10:17

This is what used to come up on the screen with an incoming call:

Are here is what it looks like now:

Full number removed for obvious reasons

Twitter: ajobbins

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

tonyhughes

Hawkes Bay
8476 posts

Uber Geek

Retired Mod

Trusted

Lifetime subscriber

#29575 1-Mar-2006 11:38

Maybe the server is protected against linking to images? (Usually done to prevent bandwidth theft).

I put a link in there for ya...

Heres some info about hotlinking

OOOOOooooooooooooooooo look at my post count.... (1666 at time of writing), how historic (and slightly evil).

Andy_Walker

89 posts

Master Geek

#29577 1-Mar-2006 12:04

Well I am not sure. I've got caller ID working fine on my phone (Uniden FP 106). I am interested to hear what Woosh say about the issue (probabilly nothing).

That diaplay on your phone looked very odd to me, both the before & after pics seemed not what I am used to seeing.

I am interested in hearing of the caller ID experiance of other Woosh users.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#29578 1-Mar-2006 12:12

Is this issue happening with all incoming calls or just from certain networks? You need to remember that '0' is not part of the area code, it's merely an access code and the 0 is not necessarily passed between all networks.

ajobbins

5052 posts

Uber Geek

Trusted

#29588 1-Mar-2006 17:08

tonyhughes: Maybe the server is protected against linking to images? (Usually done to prevent bandwidth theft).

Yes your right. I thought about Hotlinking as soon as I walked out the door. I have added GeekZone to the Hotlink allow list on my server so all good now.

Twitter: ajobbins

ajobbins

5052 posts

Uber Geek

Trusted

#29590 1-Mar-2006 17:10

Andy_Walker: Well I am not sure. I've got caller ID working fine on my phone (Uniden FP 106). I am interested to hear what Woosh say about the issue (probabilly nothing).

Will post Woosh's reply to my e-mail as soon as i get one. They should at least reply

That diaplay on your phone looked very odd to me, both the before & after pics seemed not what I am used to seeing.

What do you mean by this? What does your look like?

Twitter: ajobbins

ajobbins

5052 posts

Uber Geek

Trusted

#30089 7-Mar-2006 15:09

Looks like Woosh have made a little bit of a blunder. I returned home today with a missed call that read the following:

A quick test from the Mobile, with number witheld of course and...

.

Actual phone numbers removed for obvious privacy reasons.

Twitter: ajobbins

Andy_Walker

89 posts

Master Geek

#30091 7-Mar-2006 15:16

Yes I've noticed that. I used to get that all the time but they only fixed it earlier this year. You are in Wellington right? My guess it perhaps they are running different firmware or different software in the different areas. I have not had that called ID issue with restricted numbers being dispalyed since Dec/Jan.

Perhaps we should notify the news media of this issue. That would give Woosh a kick up the pants.

ajobbins

5052 posts

Uber Geek

Trusted

#30092 7-Mar-2006 15:19

Well it wasnt happening a couple of days ago so they have obviosuly changed something. Yes I am in wellington.

I just got off the phone to them, to tell them of their little mistake. I don't think they believed me...

Twitter: ajobbins

1 | 2