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?
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'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. On Tue, Oct 26, 2010 at 4:12 PM, Alberto <[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] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
