UBoss Basic Phone Service and passing Caller ID

[CallMeMaybe]

Hi there,
I've a question about UBoss, call forwarding and passing the Caller ID that I'm hoping someone can help with.

If we setup call forwarding on UBoss, would the external caller's ID be passed to my mobile in the following scenario (so that I can see who's calling)?

External caller ➡ UBoss number ➡ my mobile phone


Many thanks in advance.

[Simon]

Hi,

Making the switch to UBOSS is something I've been putting off while I still have a copper landline, but hopefully someone will be able to answer your question.   

Caller ID through call divert always worked through PSTN line, so I'd be quite disappointed if it didn't work with VoIP.

[Upminster 309]

Hi there,
I've a question about UBoss, call forwarding and passing the Caller ID that I'm hoping someone can help with.

If we setup call forwarding on UBoss, would the external caller's ID be passed to my mobile in the following scenario (so that I can see who's calling)?

External caller ➡ UBoss number ➡ my mobile phone


Many thanks in advance.

Hi,

Yes, I Have my UBoss on divert at the moment and can confirm I receive the number of the orignal caller and not the Uboss number.

HTH

[Simon]

  Upminster 309

Is it safe to presume from both of these messages that Caller ID works well with UBOSS?  Just asking because we had a long thread on here from someone who was having problems with it, and that's one of the reasons I've been holding back. 

[Terryphi]

I am still having occasional problems with UBOSS and caller ID. Caller ID does not work properly consistently. Sometimes it shows just "incoming call" other times it shows the caller's number in +44 format which does not trigger the display of the caller's name even though the caller's number (in UK format) is in my Address Book. The problem is confounded by spam calls increasingly using spoofed +44 numbers.

I increasingly use a mobile phone to make calls but it is not on most of the time. I use the UBOSS service to keep my old landline number available to anyone who wants to use it because they can reach me on it anytime.

To sum up, the UBOSS service isn't great but may be a useful backup depending on your usage.

[Simon]

Thanks for the heads up, Terry.  I don't have a lot of incoming calls to my landline, but when it is used, I'd like to see the caller's name displayed on the handset.  I'm still undecided as to whether to go with UBOSS or look for an alternative which may have a proven track record for the caller display feature. 

[john7]

UBoss only does +44 which doesn't trigger the caller information on domestic phones. Its purely a a service to firms who use phone systems that can covert +44 into actual caller information  as mobile phones do where every call is preceded with the international code but they have the coding to use it with your contact list which is why calls diverted to a mobile phone displays the right information. Its probably a very good system in the right use but no for domestic phone use.

[Terryphi]

Thanks for that information John7. However, When I first started using UBOS callerID worked. Recently, it has stopped working and display simply says "Incoming Call". Without callerID there is no caller log information so pretty useless. Something seems to have changed in the system.

[Terryphi]

I raised this problem with IDNet Support and following a fix Caller ID works as expected for me. Excellent service!

[stan]

I have nothing startling or innovative to say beyond that which I've said before - except to say to those on UBOSS or considering going on to UBOSS ..... I moved from Idnet's ADSL over to their FTTP in March this year and all was well. No issues with Openreach providing the fibre connection and no problems moving the billing etc over to FTTP. 

At the time of the change I obviously had to decide what to do with the landline given that the copper pair was no longer going to provide it any more. It didn't take long to see that the choice would be either Idnet's UBOSS or Andrew and Arnold's own VOIP plan which was available for the cost of £12 transfer fee and an ongoing £1.44 per month (with calls on top).  That didn't take long and I can now report that it has been functioning for more than six months and that both it and them have been faultless.

I never understood what John7 was on about in his to and fro concerning whether or nor the UBOSS system recognized +44 prefixes ... or whatever it was that was apparently not working.  But, suffice to say my own arrangement works for me and I haven't, yet, found anything to complain about. Least of all the customer service provided by A&A.  There's nothing to choose between their service and Idnet's service - both have served me well.  The A&A VOIP has a number of options regarding how to receive incoming calls.  I have chosen to have it set so that incoming calls ring for twenty seconds, then an announcement invites the caller leave a message, then I immediately get an email on my chosen email address which pings my mobile phone and lets me hear the message. And I can say that the vast majority of calls are scam calls of one sort or another ... as they were before I changed over from copper to fibre and that the scammers never leave a message therefore I don't have the inconvenience of listening to their opening introductions prior to me terminating the calls.

In fact I wil admit I don't really need the landline any more but for the tiny monthly outlay (it's now gone up to £1.50 plus VAT) I keep it just as a sort of back-up.  I don't know why, but there it is.

What it has done, though, is let me know that if I ever stopped having Idnet supply my broadband then the next option on the list would be A&A.

[Simon]

Glad to hear things worked out for you, Stan. 

There's still no word of my PSTN line being switched off, so I'm still in blissful ignorance of what delights VoIP might hold. 

[stan]

Quite so, Simon ..... I keep saying to my neighbour that he'll have to start thinking about getting fibre one day and deciding who to go with and whether to keep his landline .... and still he carries on as he is and still there's no word of him being forced to do anything - so I suppose he might as well just carry on as he is.  But I do believe there is an actual projected date when it's all supposed to change over. He uses VOXI for his mobile (£10 a month with calls included) and TalkTalk for his ADSL broadband (via a copper pair, obviously).  His landline is TalkTalk too.  He's 85 and so it's just possible he need not actually do anything - or maybe that's not quite the right thing to say  ......       No, you're right  -  it's not.

All the time you have your PSTN then, like my neighbour, you can simply carry on although when the Openreach installer was here he did say something along the lines - it's better to get the FTTC in and up and running sooner rather than later in case there's  any sort of "rush" when the cut off date draws near and a load of people start realising they need to get it done and there's a backlog of some sort - and he did go on to try to explain that there's some technical reason why it's best not to leave it to the last available moment ... it was something to do with the actual number of connections available between the connection in the street and the main 'exchange' where all the individual fibre circuits finish up - but I didn't understand it at the time and I still don't understand what he was saying.  Either way it'll all come out in the wash.

I do have to say that the new VOIP arrangement wasn't particularly difficult to sort out - I contacted the new provider (who I have already named) and filled in an application for them to port my old number over to themselves (which was was all painless) and when, after a few days,  they told me it was "live" I connected a single cable from the new ONT box that Openreach provided into the back of the new TP Link router that Idnet provided and plugged my old analogue phone(s) into a small splitter/adaptor type thing that A&A kindly posted out to me and basically it worked.  I completed an online form for A&A  with my details and with a few settings that they helped me with and it then worked, and has done since.  You can choose how to have your incoming calls dealt with and can change your settings just by going on to the website and changing it then and there.  Even I could manage it.

Anyway that's enough.  Carry on regardless

[nowster]

So I get all the kit ready at Dad's, including an old NTE5 master socket with split phone/DSL faceplate to use to plug the RJ11 cable from the VoIP ATA box into so that I can wire in the existing extension socket cabling easily...

Asterisk configured on the router. The Grandstream HT812v2 ATA configured to talk to it.

The old black Cisco 7940 unit configured to talk to the local Asterisk server rather than the one on the far end of the VPN to my home in Manchester. The Cisco phone had been used for international calls with "Internetcalls".

IAX2 link between the two Asterisk instances configured and tested.

Incoming calls from SipGate working. I've had a local number on this dialling code for years, incoming only. I used to have the speaking clock on it.

Backup battery (1kWh LiFePo solar power bank) to run the whole shebang for about 48 hours during a power cut. (We had two last winter.)

All this in preparation to tell iDNet we don't want to renew the copper PSTN when it's up for re-billing in January, and to transfer the number to A&A.

And the following morning (Sat 8 Nov) the FTTP goes dead.

It's still dead (LOS light) today as there's a massive OpenReach fault in this area. I've heard they're waiting on being able to dig up the road somewhere. Current ETA for the fix is tomorrow evening, but I'm not holding my breath.

The landline still works of course.

Thankfully EE has pretty good 5G here but only one mast for the whole area.

[Simon]

The more technology moves forward, the more unreliable it seems to be.   

[zappaDPJ]

We are experiencing regular outages on our FTTP connection again. I'm pretty sure it's due to some kind of OpenReach maintenance but it's a right pain.

[nowster]

The FTTP link had been rock solid from July 2022 to August 2025.

That outage was a "stuck session" at a LNS, even though that was only fixed after OpenReach engineers had come, scratched their heads, swapped the ONT box, then gone away with "No Fault Found".

Of course, the OpenReach field engineers get confused by anything that isn't a BT HomeHub. ("Where's the blue light?") Me showing them a tcpdump of outgoing PPPoE PADI frames with no response from the far end meant nothing to them.

That fault was only Saturday to Wednesday. This one's going to be three weeks tomorrow.

For the first two and a half days there was definitely something on the other end (flashing PON light meaning something was signalling on the fibre from the other end) but that OLT must have been switched off when someone visited the exchange and realised there was no working upstream connection.

The weird thing is that both faults started within 5 minutes of 6am.