Topic: Maybe errors in the messages log

[compsos]

Hi

We have these entries from a hard phone (Polycom IP320) in the messages log

Jun 28 16:03:50 server in.tftpd[5957]: RRQ from 192.168.220.230 filename bootrom.ld
Jun 28 16:03:50 server in.tftpd[5958]: RRQ from 192.168.220.230 filename 0004f217952f.cfg
Jun 28 16:03:50 server in.tftpd[5959]: RRQ from 192.168.220.230 filename sip.ld
Jun 28 16:03:51 server in.tftpd[5960]: RRQ from 192.168.220.230 filename phone5000.cfg
Jun 28 16:03:51 server in.tftpd[5961]: RRQ from 192.168.220.230 filename sip.cfg
Jun 28 16:03:51 server in.tftpd[5962]: RRQ from 192.168.220.230 filename 0004f217952f-phone.cfg
Jun 28 16:03:51 server in.tftpd[5962]: sending NAK (1, File not found) to 192.168.220.230
Jun 28 16:03:55 server in.tftpd[5963]: RRQ from 192.168.220.230 filename 0004f217952f-directory.xml
Jun 28 16:03:55 server in.tftpd[5964]: WRQ from 192.168.220.230 filename 0004f217952f-app.log
Jun 28 16:03:55 server in.tftpd[5964]: sending NAK (0, Permission denied) to 192.168.220.230

It is the 0004f217952f-phone.cfg & 0004f217952f-app.log files that do not exist. Should they be there or is it caused by a setting on the phones?

Any clues much appreciated.

[SARK devs]

Hello Gordon,

Your Polycom is looking for provisioning data on the SAIL tftp server.  We don't actively support polycom provisioning in SAIL so I'm not surprised it isn't finding what it wants.  Having said that , the provisioning system is extensible and you could create your own Polycom datasets if you wish.  If you're provisioning your phone manually then you can just ignore this stuff I would guess.


Kind Regards

[compsos]

Hi S

Yes rereading the extensive admin manual for the phones it does not mention those files but I guess it is in fact trying to write back log info. Just creating an empty file shutdown the errors but was not sure what it might do to the phone.

We don't actively support polycom provisioning in SAIL

But there is a Polycom choice in the IP devices list.
Is the setup here suitable for all Polycom phones or should I be trying to write a new definition for this model?
Should I just manually build files as per the admin manual and save in the tftboot directory?
And would these files survive upgrades and reconfiguring of Sail?

I can report that we have 1 phone that provisioned but another that is not quite there.

Is there a "recommended" list of hard/soft phones for Sail?

Thank you for the help.

[compsos]

Ah
The app.log file is recording. Now just need to translate it as this is the phone that is not quite right

Code: [Select]

0101000000|cfg  |4|03|Dir|Parameter dir.local.volatile.4meg missing from sip.cfg, setting default value 0
0101000000|cfg  |3|03|Dir|Local directory will be non-volatile.
0101000000|cfg  |4|03|Dir|Parameter dir.local.nonVolatile.maxSize.4meg missing from sip.cfg, setting default value 2097151
0101000000|cfg  |4|03|Dir|Local directory limit reduced to 51200 bytes, to ensure that we have enough space.
0101000000|cfg  |3|03|Dir|Global directory will be volatile.
0101000000|cfg  |3|03|Dir|Global directory limited to 102400 bytes.
0101000000|copy |3|03|'tftp://server-bel.bament.com.au/0004f217952f-directory.xml' from 'server-bel.bament.com.au(192.168.220.1)'
0101000000|copy |3|03|Download of '0004f217952f-directory.xml' succeeded on attempt 1 (addr 1 of 1)
0101000000|cfg  |4|03|Edit|Local file compressed: /ffs0/local/local-directory_xml.zzz
0101000000|cfg  |3|03|Edit|Loaded compressed file: /ffs0/local/local-directory_xml.zzz
0101000000|ssps |*|03|Initial log entry. Current logging level 4
0101000000|dbuf |*|03|Initial log entry. Current logging level 4
0101000000|copy |3|03|'tftp://server-bel.bament.com.au/0004f217952f-app.log' to 'server-bel.bament.com.au(192.168.220.1)'
0101000000|copy |3|03|Upload of '0004f217952f-app.log' succeeded on attempt 1 (addr 1 of 1)
0101000000|key  |*|03|Initial log entry. Current logging level 4
0101000000|cfg  |3|03|Web|Config web site disabled via config file.
0101000000|ht   |*|03|Initial log entry. Current logging level 4
0101000000|ssps |*|03|Application, comp. 1: Label=PolyDSP Titan Mem1 FS4, Version=1.7.2.0004 10-Oct-07 14:49
0101000000|ssps |*|03|Application, comp. 1: P/N=3150-11580-172.
0101000000|so   |4|03|Warning: soMain: No codecs fully specified, using G711Mu, G711A defaults
0101000000|pps  |*|03|Initial log entry. Current logging level 4
0101000000|sip  |*|03|Initial log entry. Current logging level 4
0101000000|so   |4|03|SoCoreAudio: voice.handset.rxag.adjust.IP_330 not found, using 1
0101000000|so   |4|03|SoCoreAudio: voice.handset.txag.adjust.IP_330 not found, using 9
0101000000|so   |4|03|SoCoreAudioC: voice.rxEq.hs.IP_330.preFilter.enable not found, using 1
0101000000|so   |4|03|SoCoreAudioC: voice.rxEq.hs.IP_330.postFilter.enable not found, using 0
0101000000|so   |4|03|SoCoreAudioC: voice.txEq.hs.IP_330.preFilter.enable not found, using 0
0101000000|so   |4|03|SoCoreAudioC: voice.txEq.hs.IP_330.postFilter.enable not found, using 1
0101000000|so   |4|03|SoCoreAudio: voice.headset.rxag.adjust.IP_330 not found, using 4
0101000000|so   |4|03|SoCoreAudio: voice.headset.txag.adjust.IP_330 not found, using 21
0101000000|so   |4|03|SoCoreAudioC: voice.gain.rx.analog.chassis.IP_330 Not found, using default
0101000000|so   |4|03|SoCoreAudioC: voice.gain.rx.analog.ringer.IP_330 Not found, using default
0101000000|so   |4|03|SoCoreAudioC: voice.gain.tx.analog.chassis.IP_330 Not found, using default
0101000000|so   |4|03|SoCoreAudioC: voice.gain.rx.digital.chassis.IP_330 Not found, using default
0101000000|so   |4|03|SoCoreAudioC: voice.gain.rx.digital.ringer.IP_330 Not found, using default
0101000000|so   |4|03|SoCoreAudioC: voice.gain.tx.digital.chassis.IP_330 Not found, using default
0101000000|so   |4|03|SoCoreAudioC: voice.rxEq.hf.IP_330.preFilter.enable not found, using 1
0101000000|so   |4|03|SoCoreAudioC: voice.rxEq.hf.IP_330.postFilter.enable not found, using 0
0101000000|so   |4|03|SoCoreAudioC: voice.txEq.hf.IP_330.preFilter.enable not found, using 0
0101000000|so   |4|03|SoCoreAudioC: voice.txEq.hf.IP_330.postFilter.enable not found, using 1
0101000000|so   |5|03|[SoCoreAudioC]: Class 1 indicators have no states.
0101000000|so   |5|03|[SoCoreAudioC]: Class 7 indicators have no states.
0101000000|so   |4|03|Warning: Core Audio: dtmf via RTP undefined, using 0.
0101000000|so   |4|03|[SoMediaSessC]: Setting to default value 2^10
0101000000|cfg  |4|03|Edit|Error 0x380003 attempting stat of /ffs0/local/0004f217952f-phone_cfg.zzz
0101000000|cfg  |4|03|Edit|Error 0x380003 attempting stat of /ffs0/local/0004f217952f-phone_cfg.zzz


[SARK devs]

Have a look here

http://www.sonoracomm.com/index.php?option=com_content&task=view&id=104&Itemid=32

Also re your questions...

Should I just manually build files as per the admin manual and save in the tftboot directory?
And would these files survive upgrades and reconfiguring of Sail?

You can build them manually if you wish.  There is a special file type in IPDevices calles a "Descriptor".  Whatever you call a descriptor is the name it will be given on the tftpserver and you can put anything you like into it.

You can even dispense with SAIL altogether and just put your own files directly onto the tftpserver.  SAIL is smart enough to avoid trampling on them during a commit.

Is there a "recommended" list of hard/soft phones for Sail?

Not really, you can use whatever you like.  However, we only provision certain phone types (currently SNOM, Aastra, Linksys, Cisco and Grandstream).  The provisoning sub-system is quite open and extensible so it's usually not too difficult to add a new phone or phone type.  The only reason we've not done Polycoms is that they aren't very popular in the UK.


Best

[compsos]

Thanks S

I have tracked the problems down to the sip.cfg file reverting back after committing anything in the web page. Even setting the mode to 444 the panel still overwrites the sip.cfg. Note sure this should be called a bug as it maybe smarter to follow http://www.voip-info.org/wiki/view/Asterisk%40Home+Handbook+Wiki+Chapter+7#722Polycom as it uses just ftp and a set of directories safe from the Sail commit button.

This is the standard Polycom sip.cfg file. http://compsos.com.au/sip.cfg (Sorry about the link but it exceeded the posting limit of 20000 chrs)


Should we put this code in the "descriptor" file with site modifications? Or would it be better in the sip.cfg descriptor?

We used the Polycom phones as they were recommended by ATP. They do seem to be "very adjustable" just not sure I will survive the adjustments!! They are quite a learning curve. But it is interesting.

[SARK devs]

I have tracked the problems down to the sip.cfg file reverting back after committing anything in the web page.

Just delete sip.cfg from IPDEvices.  SAIL won't overwrite anything it doesn't own.   Alternatively, just change what's in sip.cfg to whatever you want and SAIL will look after it for you.

Sorry about the link but it exceeded the posting limit of 20000 chrs

Tell me about it.  You've just discovered the real reason why we never provisioned Polycoms! We did have a go,  but that file is so big it breaks the SME database in some way.  In true hacker fashion, we thought about it for a bit and then put it into the "too hard" draw and forgot about it.

Moreover, the fact that there is no true factory reset on the Polycoms is a pain.  Take a good look at the phone setup when you take it out of the box because that's the last time you'll ever see it that way.  We managed to "Brick" three brand new Polycoms in a day and a half of frenzied "provisioning".  The end result is that we hate these units and we have three "Bricks" sitting on a shelf in the office.

Should we put this code in the "descriptor" file with site modifications? Or would it be better in the sip.cfg descriptor?

The code should really go into the provisioning window for each phone (with our "$" substitute variables which SAIL will fill out each time it generates the provisioning files).

Most SIP phones follow a similar provisioning model...  There is usually some "group" file which contains information which is common to all phones and then a set of specific files (usually named by mac address or serial number) which contains phone-specific info (extension number, display name and so on).  The Descriptor files were intended as an open ended way of creating the common files.  Hoiwever, having said that, you can use them for anything you like.

Let me know how you get on with your Polycoms.  It'd be nice to get the three bricks we have here working. 

 
 
Kind Regards 

[compsos]

Thanks S

You are full of encouragement there!!!!

But the wayward would phone has fired up updated firmware and provisioned by tftp. Just do not touch the commit button.

Just expanded out the

• bootrom zip and the firmware files to tftpboot directory
• replace sip.cnf with sip.polycom and edited to suit
• generated the blank extra macaddress-app.log & macaddress-appFlash.log
• • edited the phone1.cfg & 00000000.cfg files
  • • cp 00000000.cfg macaddress.cfg for each phone
    • • got the phone to restart

      but that file is so big it breaks the SME database in some way

      
      So just delete the sip.cfg descriptor as I guess by the quote the DB will complain about chrs?
      
      What about the ftp option and the files at /home/polycom/? My thinking is that this would be "outside" Sail and maybe not raise any gremlins. Which do you think is the best way to go?
      
      And congratulations Sail is an amazing system.

[SARK devs]

Yeah,

I think I would delete sip.cfg.  You should be OK to use the tftpboot directory for your handbuilt files but it really doesn'y matter if you nominate some other dir and use ftp. As long as it gets the job done and you get your phones up and running.

Let me know how you get on.


Best