SnomONE PnP and 7xx

[madis]

I am not able to get 760 phone to provision with SnomONE. SnomONE version is 4.5.0.1090 Epsilon Geminids. Below are logs from server and phone. Tried also with version Alpha but it returned "Not found" to SUBSCRIBE request.

 

####SERVER LOG

 

[9] 2012/07/12 05:42:55: Resolve 38: aaaa udp 192.168.1.125 52297

[9] 2012/07/12 05:42:55: Resolve 38: a udp 192.168.1.125 52297

[9] 2012/07/12 05:42:55: Resolve 38: udp 192.168.1.125 52297

 

####PHONE SIP LOG

 

Sent to udp:224.0.1.75:5060 at 1/1/1970 00:00:44:828 (428 bytes):

 

SUBSCRIBE sip:MAC%3a000413710A1D@localhost SIP/2.0

Via: SIP/2.0/UDP 192.168.1.125:52297;rport

From: <sip:MAC%3a000413710A1D@localhost>;tag=465901635

To: <sip:MAC%3a000413710A1D@localhost>

Call-ID: 407399063@192.168.1.125

CSeq: 1 SUBSCRIBE

Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.7.3.7"

Expires: 0

Accept: application/url

Contact: <sip:192.168.1.125:52297>

Content-Length: 0

 

Received from udp:192.168.1.131:5060 at 1/1/1970 00:00:44:834 (271 bytes):

 

SIP/2.0 404 Unsupported User-Agent

Via: SIP/2.0/UDP 192.168.1.125:52297;rport=52297

From: <sip:MAC%3a000413710A1D@localhost>;tag=465901635

To: <sip:MAC%3a000413710A1D@localhost>;tag=a31e09b77f

Call-ID: 407399063@192.168.1.125

CSeq: 1 SUBSCRIBE

Content-Length: 0

[katerina]

I tested this could not reproduce. Are you sure it is the snom ONE answering and not some other server? Also are you sure your snom ONE version is 4.5.0.1090? Can you post a more detailed snom ONE Log like explained here: http://wiki.snomone.com/index.php?title=Snom_ONE_log ?

[madis]

Maybe I need to generate some configuration files for 7xx before it starts working?

 

Here is copy-paste from server version - Version: 4.5.0.1090 Epsilon Geminids (Win32)

And here is more detailed server log:

 

[5] 2012/07/12 08:36:49: SIP Rx udp:192.168.1.125:43189:

SUBSCRIBE sip:MAC%3a000413710A1D@localhost SIP/2.0

Via: SIP/2.0/UDP 192.168.1.125:43189;rport

From: <sip:MAC%3a000413710A1D@localhost>;tag=1869990681

To: <sip:MAC%3a000413710A1D@localhost>

Call-ID: 944876847@192.168.1.125

CSeq: 1 SUBSCRIBE

Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.7.3.7"

Expires: 0

Accept: application/url

Contact: <sip:192.168.1.125:43189>

Content-Length: 0

 

[9] 2012/07/12 08:36:49: Resolve 1962: aaaa udp 192.168.1.125 43189

[9] 2012/07/12 08:36:49: Resolve 1962: a udp 192.168.1.125 43189

[9] 2012/07/12 08:36:49: Resolve 1962: udp 192.168.1.125 43189

[5] 2012/07/12 08:36:49: SIP Tx udp:192.168.1.125:43189:

SIP/2.0 404 Unsupported User-Agent

Via: SIP/2.0/UDP 192.168.1.125:43189;rport=43189

From: <sip:MAC%3a000413710A1D@localhost>;tag=1869990681

To: <sip:MAC%3a000413710A1D@localhost>;tag=5605b80222

Call-ID: 944876847@192.168.1.125

CSeq: 1 SUBSCRIBE

Content-Length: 0

[Vodia PBX]

How is your pnp.xml file looking like from the web interface from the PBX (admin/web page control/phone pnp/pnp.xml)?

[pbx support]

Make sure that your pnp.xml file has

 <file name="snom_760.xml" encoding="xml">
   <pattern>snom760.htm</pattern>
   <vendor>snom</vendor>
   <anonymous>true</anonymous>
   <protocol>tftp,http,https</protocol>
   <pnp-vendor>snom</pnp-vendor>
   <pnp-model>snom760</pnp-model>
   <pnp-version>^[78]</pnp-version>
   <pnp-content-type>application/url</pnp-content-type>
   <pnp-url>{https-url}/snom760.htm</pnp-url>
 </file>

[madis]

It does not contain any information about 7xx phones. I upgraded from previous version and it only updates executable. Is there a new pnp.xml file available for download?

 

How is your pnp.xml file looking like from the web interface from the PBX (admin/web page control/phone pnp/pnp.xml)?

[pbx support]

If you did not have the pnp.xml customized in the previous version (either from the web page control or keeping a custom pnp.xml under the 'html' folder), upgrade should bring you the new pnp.xml automatically.

 

If you feel it is too "difficult" for figure it out, please find the attached pnp.xml.

pnp.xml

[Vodia support]

Have you modify any pages on the webpage control?

If this is a new installation maybe you can save your domain.tar file under domain and re-install snomONE from scratch.

 

[madis]

I managed to get my 760 provisioned after removing old pnp.xml from html directory. But after that I was not able to attach it to any extension. I had two extensions, which should have been able to use this phone - one with correct mac address binding and one with * binding. SnomONE was not giving it to any of them. I believe that reason lied there:

 

[8] 2012/07/13 04:24:01: HTTP: finding snom_3xx_fw.xml for vendor snom, MAC 000413710A1D

[8] 2012/07/13 04:24:01: PnP: Using the credentials of 829@elion.ee for file snom_3xx_fw.xml

...

[8] 2012/07/13 04:24:01: HTTP: Received request for file snom_820_phone.xml from 192.168.1.125

[7] 2012/07/13 04:24:01: HTTP: Error finding snom_820_phone.xml, Send back 404 Not Found to 192.168.1.125

 

snom_820_phone.xml is the file that should contain all important configuration parameters including identity information. I see this file in web page control listing and even tried to change it hoping it will somehow generate this file but it still did not seem to find it.

 

I got everything working after I set all pnp files to their default values. Then SnomONE somehow also found the snom_820_phone.xml file.

[katerina]

I guess some xml file got messed up there and that's why resetting to default helped.