Best Practices For Hints Management In Extensions.conf

Home » Asterisk Users » Best Practices For Hints Management In Extensions.conf
Asterisk Users 2 Comments

Hi,

I’m banging my head on FreePBX 2.10 setup with which a SIP hardphone can subscribe to some Freepbx-generated hints and still cannot subscribe to other Freepbx-generated hints (404 Not Found). I would be very curious to learn here a bit more about how Asterisk 1.8
(and above) deals with hint statements.

Is it recommanded to group hint statements together in dedicated context or alternatively use patterns like:
[mysupercontext]
exten => 1234,hint,Custom:Foobar1234
exten => 1234,1,Noop(Dialing 1234)
exten => 1234,n,

What’s the upside-downside of both methods ?

Regards

2 thoughts on - Best Practices For Hints Management In Extensions.conf

  • PS: Another question

    Let my system is configured with 2 hints like this :
    *2711@timeconditions-toggle: Custom:TC11
    State:InUse Watchers 0
    6452@ext-local :
    SIP/6452 State:Unavailable Watchers 0

    Let say I cannot touch the files in which those 2 instructions are set:
    [timeconditions-toggle]
    exten => *2711,hint,Custom:TC11

    [ext-local]
    exten => 6452,hint,SIP/6452

    Then what can I do allow a given SIP phone to successfully subscribe to both hints ?

  • extensions.conf:

    [subscriptions]
    include => timeconditions-toggle include => ext-local

    sip.conf:

    [some-handset]
    subscribecontext=subscriptions

    subscribecontext can be the same as context, or not. Largely a matter of preference and circumstance, I suppose.