Jump to content

SoHo auto provisioning issues


Pablo
 Share

Recommended Posts

In my office, I had snom ONE running on Windows 7 (64-bit) for several months w/one remote phone (in home office). I was able to work around NAT issues by following the route-table instructions in wiki article; the remote phone auto provisioned; and everything worked wonderfully. I recently purchased snom SoHo, to swap out Windows 7 machine and now I cannot get the remote phone (snom 360) to auto-provision. I've retraced my steps, over and over, to make sure that I did not inadvertently change/modify anything else when I deployed the snom SoHo; and I can not find a solution. In the office, my snom 300 is able to auto-provision w/o any issues (just like it did w/the Win7 machine).

Log from PBX:

 

[5] 2012/10/04 00:25:42:Did not write snom_360.xml to file system because there is no user associated with this file

[5] 2012/10/04 00:28:30:Last message repeated 2 times

[8] 2012/10/04 00:28:30:PnP: Using the credentials of 45@pbx.pcatty.com for file snom_3xx.xml

 

Log from phone:

 

4/10/2012 05:28:27 [NOTICE] PHN: Setting server prio 1, type redirection, url: >http://pbx.pcatty.com/prov/snom360.htm<4/10/2012 05:28:27 [NOTICE] PHN: Fetching URL: http://pbx.pcatty.com:80/prov/snom360.htm4/10/2012 05:28:29 [NOTICE] LID: Opening TCP socket on port 75474/10/2012 05:28:29 [NOTICE] LID: Opening TCP socket on port 8434/10/2012 05:28:29 [FATAL ] PHN: Phone::uboot_version:1.1.3-s4/10/2012 05:28:29 [NOTICE] PHN: read_xml_settings: found setting-files XML header4/10/2012 05:28:29 [NOTICE] PHN: read_xml_settings: found one byte encoding: 14/10/2012 05:28:29 [NOTICE] PHN: read_setting_file_list: added URL: http://pbx.pcatty.com:80/snom_3xx_fw.xml?model=snom3604/10/2012 05:28:29 [NOTICE] PHN: read_setting_file_list: added URL: https://pbx.pcatty.com:443/snom_3xx_phone.xml?model=snom3604/10/2012 05:28:29 [NOTICE] PHN: read_setting_file_list: added URL: https://pbx.pcatty.com:443/snom_3xx_fkeys.xml?model=snom3604/10/2012 05:28:29 [NOTICE] PHN: read_setting_file_list: added URL: https://pbx.pcatty.com:443/snom_web_lang.xml?model=snom3604/10/2012 05:28:29 [NOTICE] PHN: read_setting_file_list: added URL: https://pbx.pcatty.com:443/snom_gui_lang.xml?model=snom3604/10/2012 05:28:29 [NOTICE] PHN: Config setup: found xml style settings4/10/2012 05:28:29 [NOTICE] PHN: last prov successful:1; uri: >http://pbx.pcatty.com/prov/snom360.htm<; default uri: >http://provisioning.snom.com/snom360/snom360.php?mac={mac}<4/10/2012 05:28:29 [NOTICE] PHN: Fetching URL: http://pbx.pcatty.com:80/prov/snom360-000413297E34.htm4/10/2012 05:28:30 [NOTICE] PHN: webclient::handle_challenge: http server is asking for credentials!4/10/2012 05:28:30 [NOTICE] PHN: webclient::handle_challenge: resending request !4/10/2012 05:28:30 [NOTICE] PHN: read_xml_settings: found setting-files XML header4/10/2012 05:28:30 [NOTICE] PHN: read_xml_settings: found one byte encoding: 14/10/2012 05:28:30 [NOTICE] PHN: Config setup: found xml style settings4/10/2012 05:28:30 [NOTICE] PHN: last prov successful:1; uri: >http://pbx.pcatty.com/prov/snom360.htm<; default uri: >http://provisioning.snom.com/snom360/snom360.php?mac={mac}<4/10/2012 05:28:30 [NOTICE] PHN: Fetching URL: http://pbx.pcatty.com:80/snom_3xx_fw.xml?model=snom3604/10/2012 05:28:32 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm4/10/2012 05:28:32 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 1, state: 294/10/2012 05:28:35 [NOTICE] PHN: Fetching URL: http://login.htm:804/10/2012 05:28:37 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm4/10/2012 05:28:37 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 2, state: 294/10/2012 05:28:40 [NOTICE] PHN: Fetching URL: http://login.htm:804/10/2012 05:28:42 [NOTICE] PHN: TPL: Socket 16 idle/connect timeout4/10/2012 05:28:42 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm4/10/2012 05:28:42 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 3, state: 294/10/2012 05:28:45 [NOTICE] PHN: Fetching URL: http://login.htm:804/10/2012 05:28:46 [NOTICE] PHN: TPL: Socket 19 idle/connect timeout4/10/2012 05:28:46 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm4/10/2012 05:28:46 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 4, state: 294/10/2012 05:28:49 [NOTICE] PHN: Fetching URL: http://login.htm:804/10/2012 05:28:49 [NOTICE] PHN: TPL: Socket 20 idle/connect timeout4/10/2012 05:28:51 [NOTICE] PHN: TPL: Socket 23 idle/connect timeout4/10/2012 05:28:51 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm4/10/2012 05:28:51 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 5, state: 294/10/2012 05:28:54 [NOTICE] PHN: Fetching URL: http://login.htm:804/10/2012 05:28:54 [NOTICE] PHN: TPL: Socket 24 idle/connect timeout4/10/2012 05:28:55 [NOTICE] PHN: TPL: Socket 27 idle/connect timeout4/10/2012 05:28:55 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm4/10/2012 05:28:55 [NOTICE] PHN: Config setup: return code 400; giving up on >http://login.htm:80<4/10/2012 05:28:55 [NOTICE] PHN: Skipping prio 2 setting server, type pnp, url: ><4/10/2012 05:28:55 [NOTICE] PHN: Skipping prio 3 setting server, type dhcp, url: ><4/10/2012 05:28:55 [NOTICE] PHN: Skipping prio 4 setting server, type tr69, url: ><

Any, and all, ideas will be greatly appreciated!

Link to comment
Share on other sites

I would upgrade the soho 1st and make sure your using the same static IP you have for your windows 7, Make sure that your port forwarding mechanism for the soho are correctly set. You can also try putting the soho on a DMZ and then use the access list to protect the soho from friendly scanners.

 

 

I went ahead and upgraded the SoHo via the Software Update url under the System Tab. Under the Status tab, the version displayed is: 4.5.0.1090 Epsilon Geminids (snom ONE mini). On the phone's log, there's an entry that reads:

 

4/10/2012 15:15:37 [NOTICE] PHN: Fetching URL: http://pbx.pcatty.co...nom360

4/10/2012 15:15:38 [iNFO ] PHN: WEBCLIENT: redirect (http://pbx.pcatty.co...l?model=snom360) to (http://login.htm:80)

 

Why is the phone trying to redirect to http://login.htm:80? Could this be the problem, b/c further down in the phone's log, I found:

 

4/10/2012 15:15:40 [DEBUG0] DNS: Not adding empty response for a login.htm (ttl=900)

4/10/2012 15:15:40 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm

4/10/2012 15:15:40 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 1, state: 29

4/10/2012 15:15:43 [NOTICE] PHN: Fetching URL: http://login.htm:80

...

4/10/2012 15:15:45 [DEBUG0] DNS: Not adding empty response for a login.htm (ttl=900)

4/10/2012 15:15:45 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm

4/10/2012 15:15:45 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 2, state: 29

4/10/2012 15:15:48 [NOTICE] PHN: Fetching URL: http://login.htm:80

...

4/10/2012 15:15:49 [DEBUG0] DNS: Not adding empty response for a login.htm (ttl=900)

4/10/2012 15:15:49 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm

4/10/2012 15:15:49 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 3, state: 29

4/10/2012 15:15:52 [NOTICE] PHN: Fetching URL: http://login.htm:80

...

4/10/2012 15:15:54 [DEBUG0] DNS: Not adding empty response for a login.htm (ttl=900)

4/10/2012 15:15:54 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm

4/10/2012 15:15:54 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 4, state: 29

4/10/2012 15:15:57 [NOTICE] PHN: Fetching URL: http://login.htm:80

...

4/10/2012 15:15:58 [DEBUG0] DNS: Not adding empty response for a login.htm (ttl=900)

4/10/2012 15:15:58 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm

4/10/2012 15:15:58 [NOTICE] PHN: Config setup: return code 400; requeueing >http://login.htm:80<; attempt: 5, state: 29

4/10/2012 15:16:01 [NOTICE] PHN: Fetching URL: http://login.htm:80

...

4/10/2012 15:16:03 [DEBUG0] DNS: Not adding empty response for a login.htm (ttl=900)

4/10/2012 15:16:03 [ALERT ] PHN: webclient: Could not resolve host during provisioning login.htm

4/10/2012 15:16:03 [NOTICE] PHN: Config setup: return code 400; giving up on >http://login.htm:80<Why is the phone looking for http://login.htm:80?

 

Given that the phone is being set up in a remote site, should the phone not be trying to redirect to http://pbx.pcatty.com/login.htm:80?

Link to comment
Share on other sites

Great... and now this just happened to me:

Office PBX (via e-mail): The IP address 99.111.114.6 has been blacklistedfor 60 minutes because there were 4 unsuccessful authentication attempts (sip).

 

REGISTER sip:pbx.pcatty.com SIP/2.0

Via: SIP/2.0/TLS 99.111.114.6:4331;branch=z9hG4bK-hdfa3ht34r9m;rport

From: "Home" <sip:74@pbx.pcatty.com>;tag=spk2aw804n

To: "Home" <sip:74@pbx.pcatty.com>

Call-ID: 506de7c5b4e0-e0sqhzf3x6ye

CSeq: 1 REGISTER

Max-Forwards: 70

Contact: <sip:74@99.111.114.6:4331;transport=tls;line=4fvqnifv>;q=1.0;reg-id=1;+sip.instance="<urn:uuid:30f947f2-2522-4545-8c59-000413297E34>";audio;mobility="fixed";duplex="full";description="snom360";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom360/8.7.3.10

Allow-Events: dialog

X-Real-IP: 99.111.114.6

Supported: path, gruu

Expires: 3600

Content-Length: 0

This is after I, earlier today, added my network to the Access List: 99.111.114.0/23 (my home office). Any ideas on what could possibly going on?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...