Thirdlane.com logo

Upgrading to Asterisk 1.6

Posted by justdave on Mon, 02/09/2009
Forums
Thirdlane platform General Questions

I see that PBX Manager support Asterisk 1.6 on new installs now...

What kind of gotchas are there if I have an existing PBX Manager installation using 1.4 and I want to upgrade to 1.6? Will PBX Manager update any of the config files that it created itself from 1.4 or do I need to manually update anything? (I assume it's a given that I'll have to update some of my own scripts and so forth that are outside of PBX Manager's control).

Submitted by eeman on Mon, 02/09/2009 Permalink

be aware that agentcallbacklogin doesnt work, so if you use agents you need to find another way.

Submitted by justdave on Mon, 02/09/2009 Permalink

We don't use any agents for anything yet, no call queues. :) Just IVR, lots of extensions, and conference calling (meetme), mostly.

Any other gotchas?

Submitted by eeman on Mon, 02/09/2009 Permalink

isymphony doesnt work with it..

new extended permission set for manager.conf

read = system,call,log,verbose,agent,user,config,dtmf,reporting,cdr,dialplan

write = system,call,agent,user,config,command,reporting,originate

Submitted by Denis Campq on Thu, 02/26/2009 Permalink

Thanks for the heads up on agentcallbacklogin. Any idea on if this will be replaced with another app that will support this capability? I also tried to add the valet parking app to fix MT parking in a previous post, but quickly found that the procedure I used on 1.4 MT wasn't working for me anymore. I don't even know where the source is anymore after installing the new ISO with 1.6. I would also like to kow how to update from 1.6.0.1 to the a newer release. Think this is done with yum update but don't know exactly how or if I should. I am just testing/learning on my Lab MT so I can take chances I would not do with a production system. Obviously I have a lot to learn.

Thanks in advance for your help or advice.

Submitted by eeman on Thu, 02/26/2009 Permalink

well as far as the pbxmanager interface is concerned you will have to add the SIP/exten channels directly to the queues. As far as a replacement for agentcallbacklogin they came up with QueueAddMember