I've asked Zen for VOIP details - and I have what they have given me, but those don't quite match what is needed from the ATA 192

In case anyone else ends up here, I have solved this for the Cisco ATA192. What I did:

- Install the latest firmware 11-2-4MPP0001-115 Aug 9 2023 - not sure if this was necessary, but here for completeness
- Reset all parameters to default including voice
- Then made *only* the following changes:

Network Setup -> Bridge
IPv4 Settings -> Static IP etc
Quick Setup -> Line1 -> Proxy -> voip2.zen.co.uk
Quick Setup -> Line1 -> User ID -> <uk landline number incl area code>
Quick Setup -> Line1 -> Password -> <password from zen>
Voice -> Provisioning -> Provision enable -> no
Voice -> SIP -> NAT -> Ext IP -> Fixed IP from Zen
Voice -> SIP -> RTP -> Port Min -> 7078
Voice -> SIP -> RTP -> Port Max -> 7097
Voice -> SIP -> SIP -> TCP Port Max -> 5060

I then punched port 5060 inbound in my router to go to the fixed IP above
It then all worked!

Hi all - complete noob here, but found this thread when trying to resolve a frankly stupid situation with our provider.

We've just gone FTTP with IDNet and opted to go with their UBoss Basic service. Rather than go with their Yealink option I ordered myself a Gigaset N300AIP. Landline number was ported and then they requested the mac address of the device. They haven't been able to get it setup and now are effectively beyond the point of helping as it's not a supported device.

They've sent through a connection guide from Zen DV, who I guess the service is actually with. All this tells me is the following:

Domain Proxy address: sbc.insmartcloud.com
Registrar Server Address: as above
Proxy Server Port: 5060

I've got the Codecs as well.

But crucially no authentication info and they've said that they're unable to provide that as "the device is setup via the MAC address".

When I found this thread last night I was hopeful that with the info in here I'd be able to sort it myself, but without a password I'm stuffed I guess?

Not sure what to do right now. They've offered to send out an adapter for free (I assume they mean ATA) but our old phones are a bit knackered and I've got the new Gigaset base station and DECT phone sat here that I can see being a pain to return.

In reply to a post by Swervin_:

Hi all - complete noob here, but found this thread when trying to resolve a frankly stupid situation with our provider.

We've just gone FTTP with IDNet and opted to go with their UBoss Basic service. Rather than go with their Yealink option I ordered myself a Gigaset N300AIP. Landline number was ported and then they requested the mac address of the device. They haven't been able to get it setup and now are effectively beyond the point of helping as it's not a supported device.

They've sent through a connection guide from Zen DV, who I guess the service is actually with. All this tells me is the following:

Domain Proxy address: sbc.insmartcloud.com
Registrar Server Address: as above
Proxy Server Port: 5060

I've got the Codecs as well.

But crucially no authentication info and they've said that they're unable to provide that as "the device is setup via the MAC address".

When I found this thread last night I was hopeful that with the info in here I'd be able to sort it myself, but without a password I'm stuffed I guess?

Not sure what to do right now. They've offered to send out an adapter for free (I assume they mean ATA) but our old phones are a bit knackered and I've got the new Gigaset base station and DECT phone sat here that I can see being a pain to return.

The MAC address is a red herring I suspect. With the Yealinks they are set up to use Yealinks auto configuration, so the phone calls home to Yealink with the MAC address, Yealink will see that has been configured on their system by Zen, and then send the necessary setup files.

This is never going to happen with a different device regardless of what the MAC address is or isn't.

Basically you are not going to get anywhere now without having the credentials.

In reply to a post by E300:

The MAC address is a red herring I suspect. With the Yealinks they are set up to use Yealinks auto configuration, so the phone calls home to Yealink with the MAC address, Yealink will see that has been configured on their system by Zen, and then send the necessary setup files.

This is never going to happen with a different device regardless of what the MAC address is or isn't.

Basically you are not going to get anywhere now without having the credentials.

Thanks E300. Well, I phoned Zen in the end and they confirmed that I should be able to get the relevant details via our provider. Credit to the guy at Zen as it wasn't even the right depratment for them, but he was incredibly helpful. I've been sent a "username" and "password", and have since tried multiple combinations using both that info and the BYOD info they sent, and tried with the details listed above using the voip2 Zen address etc, but still to no avail.

So I've requested they confirm with Zen exactly what the provided username and password relates to and how that differs with what I've seen online of people using the telephone number as the username etc.

At the moment I'm not hopeful of a positive resolution and can see me looking around for another VOIP provider.

ETA: I'm also wondering if I need to change any firewall settings in my RT-AX59U router, but not sure what needs to be set.

Edited by Swervin_ (Tue 27-Feb-24 14:23:42)

In reply to a post by Swervin_:

ETA: I'm also wondering if I need to change any firewall settings in my RT-AX59U router, but not sure what needs to be set.

I have never needed to change a broadband router to allow VOIP through it. The N300 starts the connection by registering with one or more VOIP ISPs.

I have also not added any codecs.

For Sipgate I use the following settings:

Connection name or Number: BV Sipgate

Authentication name: 1234567
Authentication password: ABCDEDG
Username: 1234567
Display name: Sipgate


Hide advanced settings

DNS SRV Lookup Yes

Domain: Sipgate.co.uk
Proxy server address: Sipgate.co.uk
Proxy server port: (Blank)
Registration server: Sipgate.co.uk
Registration server port: (Blank)
Registration refresh time: 60 sec

STUN enabled: Yes
STUN server address: stun.sipgate.net
STUN server port: 3478
STUN refresh time: 240 sec
NAT refresh time: 20 sec
Outbound proxy mode: Automatic
Use DHCP Option 120 "SIP Server" Not selected
Outbound server address: (Blank)
Outbound proxy port: (Blank)
Select Network Protocol: Automatic

OK, I'm pretty much at the point of giving up with this.

I've disabled the SIP Passthrough on the router. All settings match those provided, albeit I don't have any info regarding whether STUN is enabled or not. I've gone with not on that basis.

Only one other thing I've noticed - when I paste in the SIP password and hit "set", when I go back into the settings the number of *** in the SIP password box is much shorter than the number of characters in the password I've entered. Not sure if this is just a quirk of the N300 or something is actually amiss.

Not used an N300 but in most circumstances would expect the number of *s to be the length of the password.

Do you use a password manager? I have found with some webpages (usually with 2-step authentication) if I just hit enter at the end of the password/addition question response it works but if I click the Next button the password mangler replaces what I typed with somethingh else before submitting (I suspect it tries to insert the same password as for the previous page).. In your case it might be submitting the N300 password rather than the SIP password you have entered.

In reply to a post by Swervin_:

Only one other thing I've noticed - when I paste in the SIP password and hit "set", when I go back into the settings the number of *** in the SIP password box is much shorter than the number of characters in the password I've entered. Not sure if this is just a quirk of the N300 or something is actually amiss.

This is commonplace in password entry, to stop anyone looking over your shoulder and guessing the password from the number of characters.

I have outgoing calls! Was provided with a couple more setup details by IDNet, which at first didn't seem to work. Came back an hour later and the N300 was showing the connection as registered.

However, if I try calling the number it comes up as invalid number. So there's work to be done yet on figuring out the incoming calls.