[WXC/VFX] Siemens Gigaset s685 IP setup

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] Siemens Gigaset s685 IP setup

gstarkey

78 posts

Master Geek

#79882 23-Mar-2011 22:32

Have spent hours on this, have read the forums but still cannot get my Siemens Gigaset S685 IP to
register.

First I should say it may be a firewall issue, I am running iptables on a linux box as the firewall, but I am
getting but I am getting "401 Unauthorized" back from pan.wxnz.net. so assume this rules out the firewall

Have set the following:
Authentication Name: set to AuthUser in email
Authentication password: set to AuthPassword in email
Username: set to UserID in email
Display Name: set to 48311343
Domain: pan.wxnz.net
Proxy server address: pan.wxnz.net
Registrar server: pan.wxnz.net

As I said I'm getting "401 Unauthorized" back from pan.wxnz.net.

In another thread sbiddle says you only need to set AuthID, User ID, Password and Registrar Server.
When I set only these the S685 makes no attempt to connect to pan.wxnz.net, nor resolve the name by
DNS, I am packet sniffing.

Any ideas

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#451295 24-Mar-2011 06:31

You have every thing correct by the looks of it except for the password , I have tested the credentials and all is good, just check your password entry and make sure there is not a blank (space) at the end of it ...it should finish with Gf

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

gstarkey

78 posts

Master Geek

#451311 24-Mar-2011 08:29

Thanks that fixed it.

For anyone else trying to configure one of these devices, be aware that I had times where the status on the web interface Settings-> Telephony -> Connections screen did not reflect what I was seeing by packet sniffing. ie saw status of "Server not accessible" just after I had seen a registration fail via packet sniffing.

It also seems that after a change in configuration the S685IP does not always try to connect. This may explain my issue with Thanks that fixed it.

For anyone else trying to configure one of these devices, be aware that I had times where the status on the web interface Settings-> Telephony -> Connections screen did not reflect what I was seeing by packet sniffing. ie saw status of "Server not accessible" just after I had seen a registration fail via packet sniffing.

It also seems that after a change in configuration the S685IP does not always try to connect. This may explain my issue with sbiddle's advice noted above and postings in other threads where odd settings fixed issues.

With the correct setting it took the web page ages (minutes) to change the status to connected, even though packet sniffing showed that it was connected.