Recent posts

#71

IDNet Help / Re: Since VoIP callers names f...

Last post by john7 - Oct 04, 2024, 11:08:42

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.

#72

IDNet Help / Re: Since VoIP callers names f...

Last post by john7 - Oct 04, 2024, 03:38:50

The Gigaset handset won't be VoIP. It's going to be DECT.

If you're connecting via the 431A jack socket or an RJ11 socket, it's an analogue connection. The analogue-to-digital interface is within the TP-Link router.

The handset is only going to be VoIP if it's on your WiFi and you had to program it with username/password/SIP server/etc. details.

Did IDNet supply the router? If so, did they pre-configure it for you?

https://en.wikipedia.org/wiki/British_telephone_socket shows the 431A plug.

Hi yes supplied and set up by IDNet which is why I am so angry they just try to blame my phon/s

#73

IDNet Help / Re: Since VoIP callers names f...

Last post by Simon - Oct 04, 2024, 00:54:51

My guessing is that iDNet has made a decision not to provide you with CLI in the form that BT would provide.

I've just checked with an incoming SIP number I have with Internet Calls. That presents 00441632123456 as the format of the number. My SipGate number presents my server with the number format 01632123456.

I have found nothing in any TP-Link manual online which suggests that the router can mangle CLI numbers to satisfy your DECT handsets.

This is all on IDNet and how they've set up their SIP exchange software.

(As they're not currently in use, and I want them to keep live, the SipGate line currently reads back the CLI of the number that dials it, and the Internet Calls line does the old speaking clock with the voice of Pat Simmons.)

So, are you saying that no Gigaset handset will display phonebook names if using UBOSS through IDNet?  Or is this issue specific to John?

#74

IDNet Help / Re: Since VoIP callers names f...

Last post by nowster - Oct 04, 2024, 00:19:23

My guessing is that iDNet has made a decision not to provide you with CLI in the form that BT would provide.

I've just checked with an incoming SIP number I have with Internet Calls. That presents 00441632123456 as the format of the number. My SipGate number presents my server with the number format 01632123456.

I have found nothing in any TP-Link manual online which suggests that the router can mangle CLI numbers to satisfy your DECT handsets.

This is all on IDNet and how they've set up their SIP exchange software.

(As they're not currently in use, and I want them to keep live, the SipGate line currently reads back the CLI of the number that dials it, and the Internet Calls line does the old speaking clock with the voice of Pat Simmons.)

#75

IDNet Help / Re: Since VoIP callers names f...

Last post by nowster - Oct 03, 2024, 23:51:22

The Gigaset handset won't be VoIP. It's going to be DECT.

If you're connecting via the 431A jack socket or an RJ11 socket, it's an analogue connection. The analogue-to-digital interface is within the TP-Link router.

The handset is only going to be VoIP if it's on your WiFi and you had to program it with username/password/SIP server/etc. details.

Did IDNet supply the router? If so, did they pre-configure it for you?

https://en.wikipedia.org/wiki/British_telephone_socket shows the 431A plug.

#76

IDNet Help / Re: Since VoIP callers names f...

Last post by john7 - Oct 03, 2024, 14:22:18

This is getting more than frustrating. Support now say I should contact TP-Link to see what they can do. Even though they sold the router to support UBOSS and said when it was supplied by them"You shouldn't need to contact TP-Link as we will be providing the support for any devices you purchase through ourselves".
They also are ignoring that BT have repeatedly said all there current phones work with correctly set up AoIP and again said contact BT.
Worse I replaced as a test the phone with a Gigaset s850HX  and it also had the same +44 display and its was sold as a AoIP phone.

#77

Networking & Routers / Re: RT-AX59U router

Last post by nowster - Oct 03, 2024, 12:27:23

Depends on how fast your connection is and how demanding your needs are.

I've been using a pair of Unifi Access Points which are good up to about 400Mbps. They're a bit of overkill for a domestic environment, though.

For my dad's place (with a 50Mbps connection) we're using cheap travel routers in Access Point mode (GL.iNet Opal), all interconnected via 1000BaseT Ethernet. If you catch the sales you can occasionally find them for less than £40 on Amazon.

#78

IDNet Help / Re: Since VoIP callers names f...

Last post by john7 - Oct 03, 2024, 08:16:50

Interestingly calls are shown on the IDNet customer dashboard as 0 not +44. They must convert them to this format if international numbers are being used on my VoIP not clear how it helps but one reason I never realized the problem as the numbers are difficult to see on the phone here as they move over the screens quite rapidly.

#79

Networking & Routers / RT-AX59U router

Last post by g7pkf - Oct 02, 2024, 22:19:18

RT-AX59U bit limited on wi-fi range any recommendations to extend PROPERLY via ethernet not an issue.

#80

IDNet Help / Re: Since VoIP callers names f...

Last post by john7 - Oct 02, 2024, 18:30:06

Pitty as I'm not geting anywhere with IDNet an abortive change yesterday's and nothing since. I just don't understand the problem others are getting numbers starting in 0 not +44 so why can't they just do the same settings for me? I also don't understand why they thought a customers analog phone would work with international phone number's
Any way thanks for your help, BT support said it depends on the correct setup for a phone to work correctly born out by this