Thirdlane.com logo

custom script and IVR menu?

Posted by Glen.C on Wed, 10/18/2017
Forums
Thirdlane platform General Questions

Thirdlane MTE
Communications manager: 7.4.1.1

So i've created some custom scripts for goto-huntlist and goto-queues in the script library so i can better deal with inbound CLI Text display (our upstream uses PAI and private calls seems to override the text display and set anonymous@anonymous which wipes out the text display so callers dont know which queue or huntlist was rung. Putting exten => s,n,Set(CALLERPRES()=allowed) in the script fixes this).

The scripts work great and are selectable from inbound routes but how do i get them to appear in the IVR menu section under "what to do"?

Screen shot of what i'm talking about

https://imgur.com/a/uHykR

Submitted by mattdarnell on Wed, 10/18/2017 Permalink

Add a feature code that points to the script, be sure the script can be used as a feature code.

Submitted by Glen.C on Thu, 10/19/2017 Permalink

That is an option but i have 59 tenants and a lot of have IVR's, i'd have to create a feature code for each client and then manually change their IVR selections to point to these feature codes.

Is there a cleaner way to achieve this?

Submitted by thirdlane on Sun, 10/22/2017 Permalink

I can't think of a "clean" way to do this, unfortunately. Making changes to our original script is an option - but it is not very clean.

Submitted by Glen.C on Mon, 10/30/2017 Permalink

Hey Alex, Thanks for the response. How would i go about updating the original script. The script in the script library only gives me the "Clone" or "Cancel" Option, there is no "Save" option.

Submitted by Glen.C on Mon, 11/06/2017 Permalink

Hi Aelx,

That's what i've done but those scripts do not appear in the options for an IVR so i'm back to square 1.

Submitted by netriplex on Tue, 11/07/2017 Permalink

Glen,

This is not "clean" way to do this, but this is how I workaround this Thirdlane shortcoming...

Any script you create in thirdlane is available as an Asterisk "context" with the name, macro-[whatever you name the script].

Therefore, if in your IVR, you use the "Command" option and enter into the field, "Goto(macro-[whatever you name the script],s,1)". Now, the issue with doing this, there is another Thirdlane shortcoming in that there is a bug in the Thirdlane GUI that truncates what you enter into the textbox to the first comma, so in the dialplan, it only gets registered as Goto(macro-[whatever you name the script] . So, at this point, you need to manually update the ast_static_config table in the MySQL database to reflect the correct command and then issue a asterisk -rx "dialplan reload" command to put the changes into the dialplan. This will allow you to use any script as a part of the IVR.