Renewing contract and maybe moving home phone to fibre...

[#1]

So, finally found some stuff from my cisco / linksys SPA 122, which I have working with Nimvelo. It has a "quick setup" page, that looks like this:

Quick Setup

Line 1
Proxy:
Display Name:
User ID: 2598869e0
Password:
Dial Plan: (*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)

Line 2
Proxy: sip.sipcentric.com
Display Name: 109xxx
User ID: 109xxx
Password: 
Dial Plan: (*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)

I remember reading that NAT can give issues, here's my NAT details:

Voice / Line 2: set NAT Keep Alive Enable --> Yes

NAT Settings
NAT Mapping Enable: no
NAT Keep Alive Enable: yes
NAT Keep Alive Msg: $NOTIFY
NAT Keep Alive Dest: $PROXY

Proxy and Registration
Proxy: sip.sipcentric.com
Outbound Proxy:
Use Outbound Proxy: no
Use OB Proxy In Dialog: yes
Register: yes
Make Call Without Reg: no
Register Expires: 3600
Ans Call Without Reg: no
Use DNS SRV: no
DNS SRV Auto Prefix: no
Proxy Fallback Intvl: 3600
Proxy Redundancy Method: Normal
Mailbox Subscribe URL:
Mailbox Subscribe Expires: 2147483647
Auto Register When Failover: no

[#2]

I'm a tech support person, and one thing I've learnt is that often the documentation is not only bad, it tells lies!

When another techie says "hey, did you try this" and you know it only takes a few moments to try it, then it has to be worth trying (and so often that's the detail you need)

I note that Sipgate also use an outbound proxy, so obviously not uncommon. There's an article that explains the outbound proxy https://kb.smartvox.co.uk/ip-phones/sip-outbound-proxy-server-explained/ also a link to https://kb.smartvox.co.uk/ip-phones/ip-phone-configuration-sip-proxy-server/ , where it says that if you leave it (the outbound proxy server) blank, then all SIP requests will generally be sent to the “Proxy Server”.  

I'd be very tempted to just try it, what is there to lose?

ADDED:

I see that, in that Linksys config, the "Use outbound proxy" is actually set to "yes", and the outbound proxy field is, as we already commented is blank.... my brain says either set it to "no" or fill in the outbound proxy!! ALSO set "DNS SRV" to no.

[#3]

I'd be very tempted to just try it, what is there to lose?

Agreed, but I'd suggest setting the 'use Outbound proxy' to no first and see if that sorts it, since the settings are inconsistent as they are.

[#4]

---

@dejjones wrote:

Below is what I believe to be the relevant config. details.

---

@dejjones 

For comparison I've attached a screenshot of the FreeVoipDeal settings from my Gigaset N300IP with 'Authentication name' and 'Username' (phone number in this case, see my earlier post) changed for obvious reasons.

Having just had a bit of a play with the settings I can confirm that the account still registers with any or all of the fields listed below BLANK, although I didn't try making any calls or leave it in that state for any length of time.

Proxy server address:

Proxy server port:

Registration server:

Registration server port:

Although I have entered STUN settings STUN is not being used (can't remember why I entered them).

[#5]

Thanks for all the feedback

I think I've tried all of your suggestions and many others.

FVD's instructions say leave Outbound Proxy blank, so they clearly do not need that, (I've tried putting their Proxy Server name in there, anyway, with and without the (sip.) to no avail.

My existing account registers OK with only 3 fields filled (Proxy, Password & User ID)

I think my only chance is to find someone who has an SPA 3102 with an FVD account.

I have it working on the mobile app so will settle for that meanwhile.

[#6]

@dejjones 

Googling found this (which you may have already seen)

http://www.pap2t.com/?show=pomoc  (no https:)

Some way down the page in the section

How do I configure the Linksys PAP2T Gateway with other Betamax / Dellmont services?

it says

Use Auth ID: NO
Auth ID: -

(The only time I've ever used it is when the phone number is substituted for username as described earlier)

Edit: I've never used that device or yours, but I believe they're broadly similar.

[#7]

@RobPN 

@PNnewbie 

@MisterW 

@paul_blitz 

I've just managed to register, and am now able to make calls!!!
I changed "Use DNS SRV" and "DNS SRV Auto Prefix" from "yes" to "no" and that allowed registration.
I have no idea why this works.
I have attached a screenshot of the working config.
Thanks for everyone's help.

[#8]

I changed "Use DNS SRV" and "DNS SRV Auto Prefix" from "yes" to "no" and that allowed registration.
I have no idea why this works.

DNS SRV (service) records are normally used to direct incoming calls. For instance we have an SRV record for our office PBX system which defines a main and a backup pbx. The SRV record is configured in our A & A control panel as the destination for incoming calls, and it means that incoming calls will try the main pbx first and if that doesnt answer will revert to the backup.

Not sure why anything to do with DNS SRV SHOULD affect registration but ...

From here https://community.cisco.com/t5/voice-systems-and-accessories-small-business/spa-3xx-5xx-configuring-...

When DNS SRV is enabled, SPA phone performs DNS SRV query first and performs A/AAAA record lookup if no SRV records were found,

However, If auto-srv prefix parameter is enabled, phone will only try DNS SRV and will not fall back to A record.

So I suspect it was the Auto-srv setting that was preventing the spa3102 resolving the freevoipdeal server url correctly. It was looking for an SRV record on freevoipdeals DNS which probably (quite reasonably!) doesnt exist

[#9]

---

@dejjones wrote:

@RobPN 

@PNnewbie 

@MisterW 

@paul_blitz 

I've just managed to register, and am now able to make calls!!!
I changed "Use DNS SRV" and "DNS SRV Auto Prefix" from "yes" to "no" and that allowed registration.

---

@dejjones 

That, along with a few other "No" settings as people suggested. 

As a simple End User I haven't come across the DNS SRV settings before, but as I said earlier, your device is more comprehensive than the ones I've used.

As an aside, referring to a previous post where I said that FVD (along with others from the same stable) only allow one device to register at a time, if you don't need to receive calls on that account (probably not, unless they're via SIP URI calling or you have a third party DID number pointing at the account) you could try changing 'Make Call Without Reg' back to "Yes".  That will should enable you to register the account in another device which may not have that facility and use it on both.  At least that's the way it works with my DrayTek, thus allowing the account to be registered in my Gigaset N300IP whilst still allowing calls (but with no dial tone presented) from the DrayTek.