Context of Queues in thirdlane

which build/version of isymphony are you using? I have isymphony working with Thirdlane PBX in both MTE and single tenant versions.

In order for the context setting to work for isymphony you need to create a feature code extension and assign it to the queue. For example lets say you made a feature code of 520 and assigned it to your queue, then your context would be from-inside-tenant or from-inside.

There is one issue with isymphony where a call comes into a hunt list and gets answered by an isymphony user and redirected to another extension. Apparently the RINGGROUP_TIMEOUT channel variable carries over to the redirected call and will never timeout to voicemail or do any of the other user extension features.

As a workaround I created a from-inside-isymphony context that merely unsets RINGGROUP_TIMEOUT and sends it to from-inside-redir

in isymphony its best to use from-inside as your regular context but from-inside-redir as your redirecting context so that it doesn't send calls through the tl-set-variables2 macro.

Hi Erik,

I am using version 2.0b5 (the current download version from there site). We were testing it with trixbox CE, but have moved testing to thirdlane.

I created the feature code extension for the queue macro and calls are showing up under the queues in iSymphony now. I had all the context's as 'from-internal' including the queues, I have changed the redirecting context as suggested.

I am new to thirdlane (and Asterisk), I don't understand why adding the feature code extension made it now work when it's not used by anything? The queues are accessed via inbound routes.

Thank you very much for all your help.

Regards

Allister

Hi Allister,

Please send me a (reminder) email and I will send you the latest pre-release build for testing.

Erik - thank you so much for covering for me :).

Best regards,

Alex