Hi Todd,
the jar posted by George is perfect. Just a few more hints:
- the config file will be published via TFTP (Snom m3 cannot read from HTTP on a port different than 80)
- configure your dhcp server with option 160
- in the option value write "yourConfigServerHostName.yourdomain/". The final slash is necessary.

The phone should pick the config then.
Alberto

Il 26/10/2010 22:56, Todd Hodgen ha scritto:

Alberto, If you send me a copy of the precompiled jar plug-in with instructions, I'll install it on my 4.2.1 system and test it. I've got an M3 that has been waiting to get some exercise for quite a while.

*From:*[email protected] [mailto:[email protected]] *On Behalf Of *Alberto
*Sent:* Tuesday, October 26, 2010 1:42 PM
*To:* sipXecs developer discussions
*Subject:* Re: [sipx-dev] Snom M3 plug-in and Snom bug fix

Hi Tony,
replies below.

Il 26/10/2010 22:20, Tony Graziano ha scritto:

I would like to know if you have a big fat readme how the m3 needs to know the A record for the domain (and needs to point it to sipx) in order for it to work?

Well ... I understood it is able to query for a SRV records. So I just set the domain and it was able to find the server in the domain. Of course my domain is configured with a SRV record in the sipX way.

I did the original wiki for the m3, and while it works fine I find this annoying I have found no good workaround.

    are you suggesting or inferring the default values based on the
    old wiki article? if so that's a good start! Thanks for the patch.

I really didn't know there was a wiki page about it. I'll have a read and see if there is something I've been missing. I started the plug-in from scratch many months ago. Finished it a couple of weeks ago. Didn't find particular obstacles with the phone itself.


I'll play with it after it makes it into a rpm and see what might be better clarified and suggest as I come across anything that might make it easier.

I can provide, if you wish, a precompiled jar plug-in and instruction how to install it. You can test it against sipXecs 4.2.1. Of course I would recomend to avoid a production environment.

On Tue, Oct 26, 2010 at 4:12 PM, Alberto <[email protected] <mailto:[email protected]>> wrote:

Hi all,
after a long time I finally made some improvements in the Snom plug-in.
I fixed a bug that will eventually corrupt the Snom 3x0 address book and I finished a Snom M3 plug-in.

XX-9110 <http://track.sipfoundry.org/browse/XX-9110> and XX-9109 <http://track.sipfoundry.org/browse/XX-9109>

I've been testing it for some weeks already. If someone wants to help beta testing and suggest future features or default values for the Snom plug-in just send me an email.
Thanks
Alberto


_______________________________________________
sipx-dev mailing list
[email protected] <mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-dev/




--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected] <mailto:[email protected]>
Fax: 434.326.5325

Email: [email protected] <mailto:[email protected]>

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected] <mailto:[email protected]>

Helpdesk Contract Customers:
http://support.myitdepartment.net

_______________________________________________
sipx-dev mailing list
[email protected]  <mailto:[email protected]>
List Archive:http://list.sipfoundry.org/archive/sipx-dev/


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to