VoIP problem

I have a problem with UBOSS VoIP via IDNet. I use a BT Advanced Phone Z with a TP-Link EX800v supplied and setup by IDNet. The problem is calls coming in are using +44 not 0 so the numbers listed in our phone contacts don’t match up so names can’t be displayed which as we are at and over 80 is more than useful its very important. It also means blocked numbers aren’t blocked as again they don’t match whats held in that list.
IDNet have not been the most helpful saying they are told there is no problem with UBOS so it’s the phone or router and I need to contact the makers. BT have twice said to me all there current phones work with correctly set AoIP . IDNet have been told this a number of times but its ignored. I was also told IDNet who sold the router would support it.
Today I used a Gigaset s850HX and it also just received/displayed +44 so its not just my BT phone. A fellow IDNet user had a look at the phone setting in the TP-Link EX800v and like me could see no way it could be setup to change +44 to 0.
Is there anything I can do to get this working so our contacts and blocked list work on our phone? Even if is there a phone setup that could be made to work as I can’t see anyway of adding +44 to either contacts or the blocked list.

Edited by john7 (Thu 03-Oct-24 15:36:59)

There must be a way to add the +44 to the contacts in the directory as otherwise you wouldn't be able to enter any non-UK phone numbers in. I would suggest looking at that first. A quick google suggests you might need to replace the + with 00 - ie 00441234 567890. I would try that with your mobile number and see if it works.

Thanks added 00 to mobile but no use still +44. You dont use + to make international calls just 00 then the country code as phones don't have + on there keypads

Edited by john7 (Thu 03-Oct-24 17:21:16)

Maybe you should port you number to a decent VOIP supplier such as Voipfone or A&A. For Dect phones I like the Gigaset N300 with Gigaset phones.

That way you can change broadband supplier without having to worry about your phone service.

In reply to a post by john7:

I have a problem with UBOSS VoIP via IDNet. I use a BT Advanced Phone Z with a TP-Link EX800v supplied and setup by IDNet. The problem is calls coming in are using +44 not 0 so the numbers listed in our phone contacts don’t match up so names can’t be displayed which as we are at and over 80 is more than useful its very important. It also means blocked numbers aren’t blocked as again they don’t match whats held in that list.
IDNet have not been the most helpful saying they are told there is no problem with UBOS so it’s the phone or router and I need to contact the makers. BT have twice said to me all there current phones work with correctly set AoIP . IDNet have been told this a number of times but its ignored. I was also told IDNet who sold the router would support it.
Today I used a Gigaset s850HX and it also just received/displayed +44 so its not just my BT phone. A fellow IDNet user had a look at the phone setting in the TP-Link EX800v and like me could see no way it could be setup to change +44 to 0.
Is there anything I can do to get this working so our contacts and blocked list work on our phone? Even if is there a phone setup that could be made to work as I can’t see anyway of adding +44 to either contacts or the blocked list.

On page 31 of the instructions + is listed as being on charactor map on the 0 button

I have idnet's ubos voip service and works fine with the gigaset base and system

Very usfuull but no.idea how all I ger is 0 and P.

Thanks its very usfull to know it can work just have get them to sort it. It did +44 on a gigaset as well as the BT phone

Send Idnet an email, they should respond quite quickly

I have been on at them for weeks and they are just denied any thing to do with them. All my phone or router even when when I point out it's two different phones and a router supplied and configured by them..Basicly been usless!

Edited by john7 (Thu 03-Oct-24 20:39:11)

My own config'd n510 ip pro doesn't give show the +44 ....... but the 0xx

So it is the tplink....

can you try loging into the router and going to

Advanced > Telephony > Telephone Number

and click on advanced.

What is the locale set to ?

GB-UK

They have told me they forward +44 and the TP-Link lists phone calls and those in are all +44. It would be interesting to know if all the UBOSS calls to customers are shown at IDNet end as +44 if not why don't they pick up thats something wrong?

I have the uboss service.... it shows as 01202 or 079xx etc, so no +44 is showing.

Thanks for letting me know ,What router and phone?

Interestingly, I have started to notice quite a few calls from the UK starting to be shown as +4419xxnnnnnn. It is a BT Cloud Express VoIP service and going back through history it is around 50% that are +44. The show, for example, as teh call comes in +441999123456 however in the history the number is shown as +441999123456(01999123456)

I wonder if there has been a spec and software update somewhere.

I have also tried a call from mobile to my landline number - at one time is showed 07mmmtttttt but tonight it appeared as +447mmmtttttt and in history after teh call +447mmmtttttt(07mmmtttttt)

I have seen this on and off with traditional landline and mobile. I've not taken much notice of it to actually log it or make a point on a forum. It it is concerning (not for me) but for some who will be putt off by it.

IDNet say UBOSS forwarded all calls using +44 and its up to the phone to change that to local numbers. They feel I should change to yet another phone, no subjection as to what, to get the +44 over to UK numbers. So the router they sell isn’t suitable it’s the phones. To me this is rubbish and how is any normal consumer meant to deal with a phone switch over with this type of firm and mentality.

sending over +44 is correct and it is up to the phone to sort it. Your mobile does do this.

can you check if the router firmware is upto date on tp-link - i tried to find your router on their website and i can't . If there is an update - take down the settings, incase you need to re-enter them

It's the latest firmware, in fact only one. https://www.tp-link.com/uk/service-provider/wifi-rou...

Something is really wrong with a system concept which allows a router to get involved in the format of phone numbers transferred over VOIP.

Not a good start looking for a phone that will deal withn +44 as IDNet say needs to be used

Dear Customer,
.

Unfortunately our devices do not have a converter for this, because 0044 is always the latest technology on the phone unless you are using the mobile network.
If you have any further questions, we will be happy to answer them and we wish you a good day.

With best regards,
Berk Efe Aztekin
Your Gigaset Team

how long have you had the tp-link router?

Basically it seems, that either the tplink router is misconfigured or can't rewrite 0044 to 0xxx.

I do think it its a poor show that they have provided a router that can't deal with 0044 to 0xxx. On the gigasets it just works (once you have put the right details in )

John, can you register at tplink forums and explain this problem in there, as its a bug or an issue with their router

https://community.tp-link.com/en/home/

Thanks tried worikng out where my one would go with out much luck. The problem is UBOSS and IDNet clearly say its the phones that do the conversion but clearly its not as both BT and Gigaset have now said there phones do not use + that is only used in Mobil phone networks.

What happens if you enter the contact as 1234567890 instead of 01234567890 ?

It will make no difference as the phone can't use +44 what ever the numbers are entered. As if they differ from the number coming in they will not match so contact or block list entries cant be used. Either the phone needs to convert +44 to o or the number getting to the phone has to be in 0 not +44 format. Which is what two phone makes have now said when saying there phones use a propperly configered VoIP system sending 0 not +44

My landline phone will do a substring match, so 1234567890 in contacts will match +441234567890 . Worth a try?

Right will have a go but will have to be latter as out now

Thanks I wasn't thinking I tried that additional didn't work

That's a shame, my basic BT phone will pick the longest number in contacts that matches a substring of the inbound caller ID. They probably built this functionality in for when people add numbers to contacts without the area code for local numbers.

Re tested and no nothing other than +44 coming up. IDNet have washed there hands of the problem. I asked them again what phones should work and just down to I need to get one you can use + on. As they have been told endlessly these don't appear to exist its stupid they are selling something ordinary phones cant do basic things like use contacts or black lists on incoming calls.

In reply to a post by john7:

Re tested and no nothing other than +44 coming up.

What number did you add to contacts?

My test one is my mobile so it was it less 0 to start with. All that cam up was the mobile number using +44

Ok, well I've tested the BT Decor 2600 and it definitely can match inbound caller id if the number in contacts has the +44 and 0 removed, so it's possible there are other phones out there which can do the same, if they cannot match the +44.

I'm not using "UBOSS VoIP" or anything fancy mind you, just the VoIP service that comes from Sky.

Thanks, that rather points to me to what BT support said the VoIP needs to be setup right. Your Sky sounds as if it is and UBOSS isn't.

Probably. When I ring from my mobile I get the 0 and no +44 on my caller ID. I would be suspecting Uboss here, their website looks quite corporate-y so maybe their VoIP plays more nicely with office-based systems.

It sounds to me that IDNet have found a nice earner for commercial users but it’s really not suitable to sell to home users. From what I have found and been told phone sets do not use +44 that’s a mobile phone system. Firms probably have the technology that will strip it out before internal use. Not the unsuitable routers and VoIP box that IDNet sell. Most home users especially of our age (80’s) use call blocking for very good reason. For us it been difficult losing the name information when we get call. For now we are stuck, my brother died at the weekend and we are having to deal with all that now, but I think we will, when able just get rid of the land line thanks to IDNets selling a useless product form home use

If it were me, I would be thinking about a complaint against your ISP as the service doesn't seem fit for purpose, caller id contact matching and call blocking is quite important. Sorry about your brother, this is obviously not something you want to have to deal with at the moment.

i do have the uboss voip service with a gigaset n510 ip pro and gigaset handsets - +44 doesn't show on the handset but 01 xxx or 07 xxx does

It would be interesting to know what the BT Advanced Phone Z would do on my Sky VoIP line, my guess it would display 01 and 07 for caller id. If the OP has some way to test this it would lend weight to any case.

Yes when we get things sorted I must admit I do think there stuff has been appalling.

I have had the impression for some time now that IDNet are not interested in domestic customers and will do the minimum possible to get them off the line. There is currently an altnet cabling into the village (which means that BT have also suddenly announced that we are now in the FTTP plan). As soon as we have a viable alternative I'll be moving away from IDNet.

I regret to say I agree over this. I have no problems with the fiber side, yet!