Linux – Elastix and extensions.conf

asterisklinuxvoip

My VOIP provider required me to add this into /etc/asterisk/extensions.conf:

exten => h,1,Hangup
exten => _00X.,1, Answer
exten => _00X.,n, Set(CALLERID(num)=96354205144239) ;
exten => _00X.,n, Dial(SIP/${EXTEN}@Trunk_Name)
exten => _00X.,n, Hangup

Could you please explain what is this syntax mean and what can it do .?

Also how to add this syntax using Elastix GUI instead of adding it manually into extenisons.conf.

Best Answer

It looks like they are trying to have you set your outgoing Caller ID string to that sequence of digits (which you should probably obscure). It should be sufficient to set your outgoing Caller ID for the outgoing SIP trunk to that value.

Related Solutions

Unable to call through asterisk

Your problem lies with sip.conf. Make sure you're defining the username for your end device:

[2000]
username=2000
secret=2000
type=friend
context=phones
host=dynamic

Asterisk: Dropping calls with an “ast_yyerror”

In an Asterisk $[] expression, undefined variables do not return an implicit empty string or zero. They expand as "nothing" prior to evaluation of the expression, so after the variable is expanded (to nothing), it isn't visible to the expression parser. This causes the error already noted by Pablo Alsina:

GotoIf("IAX2/AtlantaTeliax-10086", "?CLOSED,1")

There are two ways to avoid this:

Always give your variables reasonable defaults before you use them (as Pablo suggested).
In any $[] expression, enclose your variables and literals with double-quotes. This will cause an undefined variable to be handled as an empty string, which can still be used for comparison purposes.

Personally, I try to do both. For example:

exten => START,n,Set(FORCE_CLOSED=FALSE)
exten => START,n,GotoIf($["${FORCE_CLOSED}"="TRUE"]?CLOSED,1)

Note the double-quotes around ${FORCE_CLOSED} and the comparison value. Even if the variable is undefined, the expression will have "" (an empty string) to compare against "TRUE".

Really, you can use any character you like, because it will just be tacked onto the variable expansion. It just gives you a literal value that is guaranteed to be there in case the variable is undefined. I like quotes because it makes the code resemble other programming languages. You could just as easily use something like $[x${FORCE_CLOSED}=xTRUE], which is commonly seen in Bourne shell scripting. The end result is the same.

Best Answer

Related Solutions

Unable to call through asterisk

Asterisk: Dropping calls with an “ast_yyerror”

Related Topic