Skip to main content

Two problems

Posted by chris on Thu, 06/24/2010

MTE 6.0.1.81
Asterisk 1.6.0.28

1. When I create an IAX extension, devices are able to register and calls sent to the extension work fine. However, Queues and Device based huntlists list the extension as IAX/111-tenant instead of IAX2/111-tenant and calls sent to the device fail.

2. When I add an Asterisk command to a huntlist, if it contains an =, that step no longer shows up in the huntlist steps, but it is still counted. The huntlist will show step 2 and step 3 if the command is step 1 for example.

Anybody else running into this?


Submitted by eeman on Thu, 06/24/2010 Permalink

i don't understand #2 but #1 sounds like a flat out bug... I would email alex at thirdlane dot com and title the subject BUG IN IAX DEVICES and explain that its writing out at IAX/exten instead of IAX2/exten

Submitted by chris on Thu, 06/24/2010 Permalink

Thanks, I'll email Alex on #1

On #2.
Step 1: NoOp("prefix ${CALLERID(name)"})
Step 2: Dial Extensions
No Answer: go to voicemail

The above works fine. But

Step 1: SET(CALLERID(name)="prefix ${CALLERID(name)"})
Step 2: Dial Extensions
No Answer: go to voicemail

After saving this version, if I go back to edit the huntlist, all I see is
Step 2: Dial Extensions
No Answer: go to voicemail

It seems to be the equal sign that's causing the problem. The line does get written to the dialplan, but not reloaded into the web portal.