that shouldn't cause a network error with the phone though... On Mon, Jul 30, 2012 at 4:22 PM, Tony Graziano <[email protected] > wrote:
> I am not familiar with snom syntax. The MOH uri standard should be: > > [email protected] is the typical uri for polycom phones, which use a > broadworks uri standard. > > I don't know which is the 4.4 or 4.6 in the email you sent. obviously if > the system was using the hostname and had doublequotes, all bets are off. > > I am not sure what your ultimate aim is, we have 4.4 in production with no > real issues. 4.6 is being actively worked on. if you are trying to press > something into production, 4.4 would be "safe" at this time. > > On Mon, Jul 30, 2012 at 3:48 PM, Kurt Albershardt <[email protected]> wrote: > >> Diffs are below -- first two are expected but don't know much about the >> MOH URI. >> >> >> On Jul 30, 2012, at 13:45 , Tony Graziano wrote: >> >> I don't use snom's but if you could compare the two sipx generated config >> files to see what is different between them, if anything, it would be worth >> the look. >> >> On Mon, Jul 30, 2012 at 3:42 PM, Kurt Albershardt <[email protected]> wrote: >> >>> Still no luck getting these to register with 4.6 >>> >>> Phones are showing "network failure" in the registration status and >>> seeing timeouts reaching the sipx box. >>> >>> Network config (including DNS) in phones is the same as when they pull >>> configs from 4.4 (seen via phone HTTP interface in both cases.) >>> >>> >>> >>> On Jul 15, 2012, at 23:27 , Kurt Albershardt wrote: >>> >>> On Jul 15, 2012, at 17:12 , Tony Graziano wrote: >>> >>> I think the thing you are leaving out is the phone config generated by >>> sipx can load a different DNS setting than what you intended, which is why >>> I suggested this deployment option to avoid a conflicting configuration on >>> the UA itself. >>> >>> OK, that helps. >>> >>> I'll take another a look at the Snom XML configs. When I diffed them on >>> Friday I found only these differences: >>> >>> <ntp_server perm="R"></ntp_server> <ntp_server perm="R">pool.ntp.org >>> </ntp_server> >>> >>> <user_pass idx="1" perm="R">123456789012</user_pass> <user_pass >>> idx="1" perm="R">12355678</user_pass> >>> >>> <user_moh idx="1" perm="R">sip:[email protected] >>> </user_moh> <user_moh idx="1" perm="R">sip:[email protected] >>> </user_moh> >>> >>> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~ > > Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab > 2013! > <http://sipxcolab2013.eventbrite.com/?discount=tony2013> > > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected].**net<[email protected]> > > Helpdesk Customers: > http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net> > Blog: http://blog.myitdepartment.net > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro> www.ezuce.com ------------------------------------------------------------------------------------------------------------ There are 10 kinds of people in the world, those who understand binary and those who don't.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
