why two different models for PST and EST?

I like to keep them seperate easier for me to organize and find things in them, But you are correct they can be consolidated and would be easier for others.

Thanks

Armando Muniz
ActiveServe Inc.
Miami Florida

i was afraid you didnt know about the third level of hierarchy. By creating a subdirectory in user_provisioning/ named the same name as the tenant, you can move a copy of any of those files into there, modify it, and it will use that template for the same model name. This means you dont needessly need to make an EST and PST timzone versoin of the the same file. Just create a version, and if a customer needs overrides, copy it into their directory to do them :-)

is there any way of getting a higher button count in the drop down for auto provisioning?
the yealink's LCD expansion key module has 39 programable keys on it, but the drop down only goes as high as 25... Also, the first key's number is Zero (0) which is also inaccessable.

Any Work arounds?

Thanks

this has been addressed many times. Currently there will not be any more than 25 buttons. Each and every 'button' has to be coded in perl and then hidden. Your phone requires 39, the Aastra one needs 126, the linksys one supports up to 72, the polycom expands to 42 plus the 6 on the phone. Considering these are always a single phone in the group you could always alter the file manually after its been created and remove it from devices.txt . Another option is to use a PC program like isymphony instead of a physical console. In the future, should the design of the portal change from perl, this could be re-assessed.

i guess i'll just substitute the ${BUTTON} with ${LINE} and use the "Span ___ Lines" field...

thanks for the 411 on that

on your line .cfg files you need to change:

SubscribeMWIExpire = 86400

To

SubscribeMWIExpire = 84600

as that's it's max value and 86400 makes the value out of the range of accepted ones

sounds like someone has lysdexia :)

dyslexics of the world.... UNTIE!

Aksing, in case we could ilpement this in the future version.

120 I think someone once told me

i believe you can put 6x 40 button add on key modules, so 240

@eric - Apologies for dredging up this old thread, but is there a way to do this for just a single extension? I have a single phone / mac that I'd like to have a different configuration than the rest of the tenant.

Any way to do that without a manual workaround?

Thanks a bunch!

@eric - Apologies for dredging up this old thread, but is there a way to do this for just a single extension? I have a single phone / mac that I'd like to have a different configuration than the rest of the tenant.

Any way to do that without a manual workaround?

Thanks a bunch!

Edit: GRR - double apologies for the double post. Captcha got stuck.

if you want a single phone to be different then you would have to provision that phone manually.. but on the up side its not like its making any extra work.

anyone have the Yealink T38G provisioning files?

Yealink T38 Files have been updated

Armando

Thanks!

Hi,

I'm experiencing a problem with the Yealink provisoing files that the phone will take the password and will add a space to it, this is how it looks like,

Label = ${EXTENSION}
DisplayName = ${LABEL}
AuthName = ${USERID}
UserName = ${USERID}
password = ${PASSWORD}

I tried removing the space like
Label = ${EXTENSION}
DisplayName = ${LABEL}
AuthName = ${USERID}
UserName = ${USERID}
password =${PASSWORD}

and it did work for this phone but on the next phone it didn't work without the space, so there is some phones which requires the password and some not.

this is problem I found on Yealink T28 and T22 we didn't test it on the T26/38

you may have a firmware issue, the yealink configs and parser is not supposed to care if there is a space between the value and the equal sign as evident by every other setting in the config.

I have it with the same firmware some times it will work and sometimes it will not.

i have noticed this issue only with hardware version 1.0.0.4, (once 1.0.0.3 didnt have the issue will try some more with the hardware version and update)