This post is at: ForumGeneral Questions
13 posts / 0 new
Last post
KevinH
KevinH's picture
Joined: 2010/03/31
Points: 10

I have an MTE setup and I am having some odd problems that all seem to be stemming from a system-wide phone reboot around 2-3AM. For the life of me I cannot find anyone with a similar problem with or without TL.
Anyone have any ideas on what could be causing it, where to configure/change it or if I'm just going insane and it's all in my head?
Thank you in advance for any feedback!

Kevin

eeman
eeman's picture
Joined: 2007/11/06
Points: 170

its configured to do that, they look for changes and if there is a change they reboot. If they reboot without a change to any of their files its likely because its on older firmware.

by default every single phone is sharing the same file local-settings.cfg (polycom_local.cfg in the provisioning templates) which means any time you add/alter ANY phone the date/time of this file changes.. which means a reboot of all your phones.

the configuration setting that does the 3am reboot (on by default) is:

prov.polling.enabled="1"
prov.polling.time="03:00"

I customize my configurations so that each tenant creates its own tenantname-settings.cfg file that polycom_local.cfg is copied into. This allows each tenant to have a separate global settings file for the tenant that you can alter without changing it for all tenants. This also means that if tenant C does a provisioning update, tenant L isnt going to see one of his files altered.

Erik Smith
dCAP
Thirdlane/Asterisk Support available
esmith.bgnv@gmail.com

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 220

Perhaps we should do a diff on the common file in the template and the provisioning directories and not update the file in case they are the same. Your thoughts?

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

eeman
eeman's picture
Joined: 2007/11/06
Points: 170

i just use the ${TENANT} variable.. its a whole hell of a lot easier.

Erik Smith
dCAP
Thirdlane/Asterisk Support available
esmith.bgnv@gmail.com

eeman
eeman's picture
Joined: 2007/11/06
Points: 170

example...

polycom_mac

CONFIG_FILES="${mac}-registration.cfg, ${TENANT}-settings.cfg, phone1.cfg, sip.cfg"

models.txt

output_2=${TENANT}-settings.cfg

Erik Smith
dCAP
Thirdlane/Asterisk Support available
esmith.bgnv@gmail.com

KevinH
KevinH's picture
Joined: 2010/03/31
Points: 10

Thank you very much Erik, this is exactly what we needed to know!
This helps in a way I cannot put into words.
I do not intend to change the way it works right now, as having the phones reboot at night does seem to be the lesser of two evils but this helps me track down some related issues.

Kevin

jimellis
jimellis's picture
Joined: 2010/11/16
Points: 0

I have a couple of questions:

1) is there a way to create a ${TENANT}-settings.cfg every time a new tenant is added automatically?
2) where is a safe place to store the ${TENANT}-settings.cfg... for example would /etc/asterisk/provisioning/tenantcfgs/ be safe from updates?

Assuming I understand the Polycom Cfg hierarchy properly, i could place any non tenant specific files in the sip.cfg or phone1.cfg directly, correct?

One last question, is it possible to do tenant level overrides for the dialplan.xml used in Cisco. I would assume i would just call the same variables and make sure the file paths match up. Lastly my only concern is the safe way to do it so that we don't have a mess when we upgrade.

I appreciate your thoughts.

Jim

dozment
dozment's picture
Joined: 2007/11/20
Points: 0

I use the same approach as Eric with tenant-specific cfg files. Works great.

Jim,

Yes, there is. Go to System Settings/Event Hooks. You can have Thirdlane call scripts at various points. I use After Created to call /etc/asterisk/Scripts/makeNewTenant.

makeNewTenant looks basically like this:

#!/bin/sh
TENANT=$1
mkdir /home//$TENANT
cp /etc/asterisk/user_provisioning/tenant-settings-Template.cfg /home//tenant-settings-$T
ENANT.cfg

eeman
eeman's picture
Joined: 2007/11/06
Points: 170

Assuming I understand the Polycom Cfg hierarchy properly, i could place any non tenant specific files in the sip.cfg or phone1.cfg directly, correct?

HELL NO you don't want to do this :-) ... you don't EVER want to mess with those two files. Thats why I created the 4 file design from the beginning. These two files need to be unaltered and they MUST match the ones issued with the version of firmware you are using. If you upgrade from 3.1.3 to 3.2.3 you MUST copy over the new sip.cfg and phone1.cfg files or bad things can happen (like what happened going from 1.6.7 to 2.1.2). Anything you want to alter in either of these files goes in the polycom_local.cfg template.

Erik Smith
dCAP
Thirdlane/Asterisk Support available
esmith.bgnv@gmail.com

dozment
dozment's picture
Joined: 2007/11/20
Points: 0

Exactly right. Don't change the default cfg files.

jimellis
jimellis's picture
Joined: 2010/11/16
Points: 0

Thanks Eric and Dozment

That's what I thought, the only changes to the default files would be a image that says this phone is provisioned :)

Here is what I am doing..
1) create my template in a safe folder, and MANUALLY save the TENANTNAME-settings.cfg in my FTP Root.
2) modify the models.txt to use ${TENANT}-settings.cfg. in the MAC.cfg creation
3) make sure a ${TENANT}-settings.cfg file is created with all new accounts

I suppose i can do the same in the cisco SIPDefault cfg template with respect tot he dialplan.xml -> ${TENANT}-dialplan.xml.

moshe
moshe's picture
Joined: 2008/11/30
Points: 0

off topic what is the latest Polycom stable firmware, recently some phone are crashing in the middle of calls (in the middle of a 3way call and another call comes in it crashes and restarts or if i set the call waiting to ring instead of the default beep if a call comes in while making a outgoing call, it just restarts

so before starting to spend much time over it i want to try to upgrade the firmware currently running on sip ver 3.2.2.0477 bootram 4.1.2.0037

any thoughts

thanks

eeman
eeman's picture
Joined: 2007/11/06
Points: 170

stay within the 3.2.x version of sip.. the 3.3 version completely changed the entire provisioning structure.

Erik Smith
dCAP
Thirdlane/Asterisk Support available
esmith.bgnv@gmail.com