Hi all,

I have worked out some more detail of what is happening now.....but the
problem is unsolved....

If I run the temporary txt file created by the config server through the
cisco "cfgfmt" utility (same one used by SipX), there are a bunch of
parameters in the file (including the line specific entries) that the
utility rejects, see below: 

[sip ciscoAta]# ./cfgfmt -tgk-ptag.dat cisco_ata18176.txt test.bin

warning: unknown attribute 'L2KeepAlive' @line 31 of cisco_ata18176.txt
warning: unknown attribute 'SecProxy' @line 41 of cisco_ata18176.txt
warning: unknown attribute 'SecProxyTimeOut' @line 42 of
cisco_ata18176.txt
warning: unknown attribute 'SipOutBoundProxy' @line 43 of
cisco_ata18176.txt
warning: unknown attribute 'SessionInterval' @line 47 of
cisco_ata18176.txt
warning: unknown attribute 'MinSessionInterval' @line 48 of
cisco_ata18176.txt
warning: unknown attribute 'CallCmd' @line 54 of cisco_ata18176.txt
warning: unknown attribute 'DialPlanEx' @line 58 of cisco_ata18176.txt
warning: unknown attribute 'ACRDN' @line 59 of cisco_ata18176.txt
warning: unknown attribute 'SyslogIP' @line 63 of cisco_ata18176.txt
warning: unknown attribute 'SyslogCtrl' @line 64 of cisco_ata18176.txt
warning: unknown attribute 'UID0' @line 75 of cisco_ata18176.txt
warning: unknown attribute 'PWD0' @line 76 of cisco_ata18176.txt
warning: unknown attribute 'DisplayName0' @line 77 of cisco_ata18176.txt
warning: unknown attribute 'LoginID0' @line 78 of cisco_ata18176.txt
warning: unknown attribute 'ShortName0' @line 79 of cisco_ata18176.txt

I checked the cisco documentation for both the version of firmware we
use (1.3) and the latest for the 7912 (8.1), and neither uses the
"UID0:......" syntax for the line user id parameter, rather it specifies
"UID:......".

if i use the "ata-ptag.dat" then is does not reject the line specific
parameters, but still does not like others:

[sip ciscoAta]# ./cfgfmt -tata-ptag.dat cisco_ata18176.txt test.bin
warning: unknown attribute 'ServicesUrl' @line 2 of cisco_ata18176.txt
warning: unknown attribute 'DirectoriesUrl' @line 3 of
cisco_ata18176.txt
warning: unknown attribute 'CallForwardNumber' @line 4 of
cisco_ata18176.txt
warning: unknown attribute 'VoiceMailNumber' @line 5 of
cisco_ata18176.txt
warning: unknown attribute 'TimeFormat' @line 6 of cisco_ata18176.txt
warning: unknown attribute 'DateFormat' @line 7 of cisco_ata18176.txt
warning: unknown attribute 'DoNotDisturb' @line 8 of cisco_ata18176.txt
warning: unknown attribute 'BlockCallerId' @line 9 of cisco_ata18176.txt
warning: unknown attribute 'CallWaiting' @line 10 of cisco_ata18176.txt
warning: unknown attribute 'AttendedTransfer' @line 11 of
cisco_ata18176.txt
warning: unknown attribute 'BlindTransfer' @line 12 of
cisco_ata18176.txt
warning: unknown attribute 'Conference' @line 13 of cisco_ata18176.txt
warning: unknown attribute 'BlockAnonymous' @line 14 of
cisco_ata18176.txt
warning: unknown attribute 'AutoLookUp' @line 15 of cisco_ata18176.txt
warning: unknown attribute 'ForwardToVMDelay' @line 16 of
cisco_ata18176.txt
warning: unknown attribute 'CallPrefGuiShow' @line 17 of
cisco_ata18176.txt
warning: unknown attribute 'CallPrefGuiSet' @line 18 of
cisco_ata18176.txt
warning: unknown attribute 'ShortName0' @line 79 of cisco_ata18176.txt

Any ideas?


On Thu, 2008-10-09 at 12:57 +1100, Graeme Allen wrote:

> Sorry, pressed send by accident on last message.
> 
> I am seeing these errors in the sipxconfig.log when I try to provision
> a Cisco 7912 or 7905 handset:
> 
> "2008-10-09 09:43:40,809": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,811": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,813": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,815": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,818": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,820": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,823": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,825": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,842": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.line] not found for MessageSource: Can't find bundle for
> base name ciscoAta.line, locale en_US
> "2008-10-09 09:43:40,845": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,846": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,848": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,849": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,851": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,853": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,855": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,857": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,858": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,861": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> "2008-10-09 09:43:40,863": WARN:ModelMessageSource:213:ResourceBundle
> [ciscoAta.phone] not found for MessageSource: Can't find bundle for
> base name ciscoAta.phone, locale en_US
> 
> Where can I find the files that it is needing?
> 
> Thanks,
> Graeme.
> 
> 
> On Wed, 2008-10-08 at 13:47 +1100, Graeme Allen wrote: 
> 
> > Hi all,
> > 
> > Testing for migration to the new 3.10.2 version of SipX is progressing
> > well, but have run into a problem with 7912 provisioning.
> > 
> > SipX is generating a gk<mac_address) config file in the tftp directory
> > for configured 7912 phones, but, the generated files are missing any
> > line specific configuration
> > 
> > The files do contain the proper custom parameters we set as defined in
> > the phone group, but no config is included for the line configured on
> > the 7912 handset.
> > 
> > Has anyone else had problems with auto provisioning of the 7912 under
> > the new SipX?
> > 
> > 
> > Regards,
> > Graeme.
> > > 
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to