Ah -- the Send Profiles to the server seems to have fixed things up. I saw that part of the process in the job status screen was to regenerate IMDB. I can also create other new users and things work as expected now.
I did do a yum update prior to configuring but not prior to the initial setup script. The GUI shows the following version info: 4.6.0. 2012-09-03EDT17:09:20. Attached is the sipxconfig.log you requested in case it provides insight on what may have gone wrong. While I'm here - we are using Polycom firmware 3.2.6.314. Is it suggested that we should move up to 3.2.7? Tony Wyland Messiah College wyl...@messiah.edu -----Original Message----- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Douglas Hubler Sent: Wednesday, September 05, 2012 1:24 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] 4.6 Polycom registration problem Log shows "2012-09-04T20:53:44.422175Z":261:AUTH:ERR:sipxt.vt.messiah.edu:SipRegistrarServer:7f78e2522700:SipRegistrar:"Unable to get credentials for '1...@vt.messiah.edu', realm='vt.messiah.edu', user='1910/0004f21b526d'" Questions: ============ 1.) Did you run yum update after installing ISO to update all rpms, sipx and otherwise? 2.) Does sending server profiles "fix" issue? System/Servers/{select server} , Press "Send Profiles" button 3.) Can you send along sipxconfig.log? On Wed, Sep 5, 2012 at 1:14 PM, Wyland, Tony <wyl...@messiah.edu> wrote: > I'm thinking I am missing something stupid here but didn't figure it out > quite yet. I have been unsuccessful at getting a Polycom 335 to register > with a 4.6 test server. Attached is an interesting snippet from > sipregistrar.log that sounds like some kind of database lookup problem > perhaps. This is the phone attempting to register with line 1 extension > 1910. The user was created and assigned to the phone with virtually no > modification from the defaults. The phone device was created by the > auto-provision service. In fact the phone registers just fine before having > a line assigned to it. Here is what was done to get to this point: > > > > * Install new 4.6 server from the ISO followed by a yum update > > * Created a new test domain and made this server the 1st server. > DNS entries were created for the test domain and the DNS Advisor reports all > is well. > > * Added all of the Telephony Services, Instant Messaging, and Phone > Auto-Provisioning services > > * Boot up a Polycom 335 with a cleared config in the test domain. > It found the server, was auto-provisioned, and was registered. > > * Changed voicemail dial plan to 4 digits and extension 1900 > > * Created a user 1910 with password and PIN > > * Assigned user 1910 to line 1 on the polycom device and did a Send > Profile > > * Phone reboots, comes up with 1910 on the display for Line 1 but is > not able to register > > * Changed LOG level for SipRegistrar to INFO level and obtain the > attached snippet during a phone reboot. > > * Blew away the server and tried a 2nd round just in case .... Same > results. > > > > Thoughts? > > > > Tony Wyland > > Messiah College > > wyl...@messiah.edu > > > > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
