Hints working with 1.4

Hi Guys,

anyone know how to get hints working with asterisk 1.4 i know its changed from 1.2.

so far ive:

added exten => 1234,hint,SIP/1234 to extensions_custom.conf

and ive added this to sip.conf:

limitonpeers=no
call-limit=50

with no luck of hints updating, anything else i need to do?

these are extentions created in astbill so i need hints working for dynamic users

In the [general] section of sip.conf you write :
allowsubscribe=yes
notifyringing=yes
notifyhold=yes
limitonpeers=yes

In the definition of your client [sip_client] you write :
subscribecontext=hint-context
call-limit=1 ; or 100 whatever
callgroup=1
pickupgroup=1

in your extensions.conf you write :

[hint-context]
exten => 1234,hint,SIP/1234

[internal-phones]
include => hint-context

that works if your sip clients are created in conf files but mine are created in astbill…

here is my fix:

astbill.com/node/1417

[quote=“jonaskellens”]In the [general] section of sip.conf you write :
allowsubscribe=yes
notifyringing=yes
notifyhold=yes
limitonpeers=yes

In the definition of your client [sip_client] you write :
subscribecontext=hint-context
call-limit=1 ; or 100 whatever
callgroup=1
pickupgroup=1

in your extensions.conf you write :

[hint-context]
exten => 1234,hint,SIP/1234

[internal-phones]
include => hint-context[/quote]I do not want to hijack the OP’s thread, but we’d very much like to have a blf/presence watch lamp indicate a SIP/VSP1-TRUNK inuse/idle staus. That’s to say, any use of the trunk (in and out, or one blf in-bound and one blf out-outbound) blinks the lamp or lamps.

Any thoughts or dialplan examples.

With thanks,

[quote=“8f27e956”]I do not want to hijack the OP’s thread, but we’d very much like to have a blf/presence watch lamp indicate a SIP/VSP1-TRUNK inuse/idle staus. That’s to say, any use of the trunk (in and out, or one blf in-bound and one blf out-outbound) blinks the lamp or lamps.
Any thoughts or dialplan examples.
With thanks,[/quote]

Your sip-client which lamps should blink needs to be subscribed to the hint-context.

sip.conf :

[sip_client] subscribecontext=hint-context

in dialplan :

[hint-context] exten => 1234,hint,DAHDI/1

in your phone :
key mode : BLF
UserID : 1234

This should work…

[quote=“jonaskellens”]Your sip-client which lamps should blink needs to be subscribed to the hint-context.

sip.conf :

[sip_client] subscribecontext=hint-context

in dialplan :

[hint-context] exten => 1234,hint,DAHDI/1

in your phone :
key mode : BLF
UserID : 1234

This should work…[/quote]

Thanks; however, the BLF on the GRANDSTREAM 2020 (firmware 1.2.1.4) isn’t lighting – period. In contrast, setting a BLF key to 71 (a parkedcall) works so we know the Grandstream BLF works.

This is a asterisknow 1.5.0 machine and the rest of the dialplan is freePBX based. The asterisk -rx show hints commands returns the following. The 7890 hint is there. It’s status is IDLE no matter the use of the trunk.

[code]trixbox1CLI> show hints
trixbox1
CLI>
-= Registered Asterisk Dial Plan Hints =-
7890@myhint-context : SIP/VN1-OUT State:Idle Watchers 0
7979@ext-local : Local/7979@out State:Unavailable Watchers 0
7000@ext-local : SIP/7000&Custom:DND7 State:Idle Watchers 0
5880@ext-local : SIP/5880&Custom:DND5 State:Idle Watchers 0
3444@ext-local : SIP/3444&Custom:DND3 State:Idle Watchers 0
2585@ext-local : SIP/2585&Custom:DND2 State:Unavailable Watchers 0
2121@ext-local : SIP/2121&Custom:DND2 State:Idle Watchers 0
0007@ext-local : SIP/0007&Custom:DND0 State:Idle Watchers 0
0003@ext-local : DAHDI/3&Custom:DND00 State:Unavailable Watchers 0
6001@ext-meetme : MeetMe:6001 State:Unavailable Watchers 0
*767979@ext-dnd-hints : Custom:DEVDND7979 State:Unavailable Watchers 0
*767000@ext-dnd-hints : Custom:DEVDND7000 State:Unavailable Watchers 0
*765880@ext-dnd-hints : Custom:DEVDND5880 State:Unavailable Watchers 0
*763444@ext-dnd-hints : Custom:DEVDND3444 State:Unavailable Watchers 0
*762585@ext-dnd-hints : Custom:DEVDND2585 State:Unavailable Watchers 0
*762121@ext-dnd-hints : Custom:DEVDND2121 State:Unavailable Watchers 0
*760007@ext-dnd-hints : Custom:DEVDND0007 State:Unavailable Watchers 0
*760003@ext-dnd-hints : Custom:DEVDND0003 State:Unavailable Watchers 0
*217979@ext-findmefollow : Custom:FOLLOWME7979 State:Unavailable Watchers 0
*217000@ext-findmefollow : Custom:FOLLOWME7000 State:Unavailable Watchers 0
*215880@ext-findmefollow : Custom:FOLLOWME5880 State:Unavailable Watchers 0
*213444@ext-findmefollow : Custom:FOLLOWME3444 State:Unavailable Watchers 0
*212585@ext-findmefollow : Custom:FOLLOWME2585 State:Unavailable Watchers 0
*212121@ext-findmefollow : Custom:FOLLOWME2121 State:Unavailable Watchers 0
*210007@ext-findmefollow : Custom:FOLLOWME0007 State:Unavailable Watchers 0
*210003@ext-findmefollow : Custom:FOLLOWME0003 State:Unavailable Watchers 0
75@park-hints : park:75@parkedcalls State:Idle Watchers 0
74@park-hints : park:74@parkedcalls State:Idle Watchers 0
73@park-hints : park:73@parkedcalls State:Idle Watchers 0
72@park-hints : park:72@parkedcalls State:Idle Watchers 0
71@park-hints : park:71@parkedcalls State:Idle Watchers 0

  • 31 hints registered[/code]
    Close but not quite … anything else needed?

Thanks,

Ok the BLF lamp now lights. An asterisk -rx reload wasn’t sufficient. An all-out amportal restart was needed, in combination, with post-restart reboot of the Grandstream. Sorry about that :blush:

However, the lamp – while now lite – is NOT changing with the sip/trunk’s use. The “show hints” status is also stuck as “Idle.”

Thanks,

Can you post what appears on the Asterisk CLI ?
A change of status on a ‘hinted’ channel is posted on the CLI.
You should see something like : Extension Changed 11[BLF-group] new state Idle for Notify User 50 (this is an example from my system)

Just to see if a change of state is reported for you specific extension that is subscribed to it.

Hello, again, will BLF/HINT work with a Queue? I’ve tried the following “hints,” without luck. The BLF does NOT change when the queue has a caller in it. The show hints does not show any status change.

-= Registered Asterisk Dial Plan Hints =- 93999@myhint-context : Queue:3999@ext-queue State:Unavailable Watchers 0 93998@myhint-context : Queues:3999@ext-queu State:Unavailable Watchers 0 3999@myhint-context : 3999 State:Unavailable Watchers 1 7890@myhint-context : SIP/VN2-OUT State:Idle Watchers 1

[myhint-context] exten => 97890,hint,SIP/VN1-OUT&SIP/VN2-OUT exten => 97891,hint,SIP/MS-PEER ; exten => 93998,hint,Queues:3999 exten => 93999,hint,Queue:3999@ext-queues exten => 95555,hint,DISA:1@disa

The department’s Manager would like to “see” when the support queue has pending callers.

Presently, the above queue (nor disa) config’s attempts actually work (i.e. do not work).

Thanks,
/S

BTW, jonaskellens …

It took us a while to figure out the placement of the keywords, in order to get the sip trunk blf indicator working – given our asterisk+freePBX setup – we had to use/edit …

[code]/etc/asterisk/sip_custom_post.conf

VN1-OUT
call-limit=100
subscribecontext=myhint-context

where [VN1-OUT] is the sip-trunk peer[/code]

Now, on my Grandstream 2020, I can “see” when/if the trunk is in use – in- and -out-going calls, ringing, and holds flash at different rates.

Very cool.

Thanks, jonaskellens !