Is Set_var Allowed With Pjsip_wizard.conf ?

Home » Asterisk Users » Is Set_var Allowed With Pjsip_wizard.conf ?
Asterisk Users 6 Comments


I’ve just discovered PJSIP ‘s support of set_var setting in pjsip.conf. Is this setting also supported in pjsip_wizard.conf ?
On a fresh 13.8.2, it doesn’t seem but I may have missed somthing.


6 thoughts on - Is Set_var Allowed With Pjsip_wizard.conf ?

  • It’s working for me…

    type = wizard endpoint/set_var = xxxxx=ttttttttt

    … trust_id_outbound : true use_avpf : false use_ptime : false user_eq_phone : false voicemail_extension :
    xxxxx : ttttttttt

  • 2016-04-25 18:14 GMT+02:00 George Joseph :

    I was looking for a set_var=xxxxx setting while I should have looked for a xxxxx setting. Thanks for correcting me !

    Anyway, using this set_var capability, how do I access xxxxx’s value in the dialplan ?

    Using lines bellow doesn’t produce anything useful:
    same = n,Verbose(0,xxxxx is ${xxxxx})
    same = n,Verbose(0,CHANNEL(xxxxx) is ${CHANNEL(xxxxx)})
    same = n,Verbose(0,${PJSIP_ENDPOINT(1000,xxxxx)}

    PS: In the above example, 1000 is the name of the PJSIP endpoint (as displayed with pjsip show endpoint 1000)

  • I don’t think you can do it with channel but I actually don’t remember (but I’ll check).

    “same = n,Verbose(0,${PJSIP_ENDPOINT(1000,xxxxx)})” works for me but the final ‘)’ is missing in you example, maybe just a cut and paste error though.

    There’s also an alternate way to specify arbitrary variables…
    @myvariable = myvalue

    You can then retrieve it with ${PJSIP_ENDPOINT(1000,@myvariable)}

    The ‘@’ tells the config to just treat is as an opaque extended variable.

  • 2016-04-25 21:16 GMT+02:00 George Joseph :

    Yes it was a cut and paste error.

    I’ve found the reason why ${PJSIP_ENDPOINT(1000,xxxxx)} didn’t work for me earlier:
    my pjsip_woizard.conf file included a line such as:
    endpoint/set_var = xxxxx =ttttttttt

    Changing it to the one bellow (trailing space), made everything work. endpoint/set_var = xxxxx=ttttttttt

    Originally, my goal was to set something equivalent to (see [1])

  • Ah, yes. Setting existing channel variables that way should work. We even have a test that sets CALLERID that way…