BLF support

Forums

I am running TL ST. TL PBX Manager 6.0.1.71 and asterisk 1.4.18.

There are 35 extensions in total. There are three receptionist using Aastra 57i with Aastra 560M expansion module. All the receptionist want to monitor all the extensions. I configured it that way. It worked for a bit and now there are issues with BLF such as...BLF not working at all, delayed BLF notification and struck BLF. Is 3X32=96 hints supported on asterisk? If yes, is there a better way to do it.

Here's how my configuration looks like.

sip.conf
[general]
allowsubscribe=yes
notifyhold=yes
notifyringing=yes
limitonpeer=yes

[223]
qualify=yes
nat=no
pickupgroup=1
callerid=XXXXX
context=from-inside
call-limit=25
vmexten=223
secret=XXXXXX
host=dynamic
username=223
callgroup=1
subscribecontext=BLF
dtmfmode=inband
type=friend
mailbox=223
disallow=all
allow=ulaw
allow=g729

extensions.conf

[BLF]
exten => 223,hint,SIP/223 ; xxxxx

Any suggestion is appreciated.

Submitted by eeman on Sun, 09/27/2009 Permalink

why did you change the subscribe context to BLF? do you not understand what a context is?

Submitted by duc on Mon, 09/28/2009 Permalink

Hi bansal,

You must use the original context form Thirdlane (from-inisde) if you change it to BLF, each time you modifiy the configuration it will be rewritten. So your BLF on your phone will not subscribe to the right hint.

Tips : try "show hints" and "sip show subscriptions" in the CLI to understand the foundations of BLF.

Submitted by eeman on Mon, 09/28/2009 Permalink

the correct and original subscribecontext is local-extensions which is where the phones get called.

Submitted by duc on Mon, 09/28/2009 Permalink

You're right Erik :-)

My mistake. It's local-extensions and not from inside.

Cheers, Duc.

Submitted by bansal.ojasvi on Mon, 09/28/2009 Permalink

Erik,

Thanks for you response, I do understand what a context is. That's why I changed local-extensions to BLF. When local-extensions wasn't working, I thought of changing it to BLF and hoping that actual BLF would work.

Here's what I get from the verbosity level 3.

Extension Changed 241[BLF] new state Idle for Notify User 221

Extension Changed 241[BLF] new state Idle for Notify User 322 (queued)

Extension Changed 241[BLF] new state Idle for Notify User 222

Although, the server shows its doing BLF, the phones don't receive actual notification.

show hints

241@BLF : SIP/241 State:Idle Watchers 3

sip show subscriptions

192.168.15.137 221 923d6a2b088 328@BLF Idle dialog-info+xml

192.168.15.137 221 4bd2e9661ff 331@BLF Idle dialog-info+xml

192.168.15.137 221 3273c185419 334@BLF Idle dialog-info+xml

192.168.15.137 221 ff7e83f266e 325@BLF Idle dialog-info+xml

192.168.15.137 221 6b7bc6b2b0d 335@BLF Idle dialog-info+xml

192.168.15.137 221 42039b43a7c 323@BLF Idle dialog-info+xml

192.168.15.137 221 0a44030e664 321@BLF Idle dialog-info+xml

192.168.15.137 221 52633af3625 239@BLF Idle dialog-info+xml

192.168.15.137 221 f9b658d4184 240@BLF Idle dialog-info+xml

192.168.15.137 221 22cb90c3ff7 237@BLF Idle dialog-info+xml

192.168.15.137 221 a47d431e32c 236@BLF Idle dialog-info+xml

192.168.15.137 221 b18d57164fa 235@BLF Idle dialog-info+xml

192.168.15.137 221 714a2384164 234@BLF Idle dialog-info+xml

192.168.15.137 221 8d064bf2e68 233@BLF InUse dialog-info+xml

192.168.15.137 221 4332ccd8ac1 232@BLF Idle dialog-info+xml

192.168.15.137 221 62e57277238 231@BLF Idle dialog-info+xml

192.168.15.137 221 6c87b1506fc 230@BLF Idle dialog-info+xml

192.168.15.137 221 01aec3c85a2 229@BLF Idle dialog-info+xml

192.168.15.137 221 6225511fc4d 228@BLF Idle dialog-info+xml

192.168.15.137 221 6d1f60d3eda 241@BLF InUse dialog-info+xml

192.168.15.137 221 ce57e9faee0 226@BLF Idle dialog-info+xml

192.168.15.137 221 7d276573c4a 225@BLF Idle dialog-info+xml

192.168.15.137 221 afdc052cd1c 224@BLF Idle dialog-info+xml

192.168.15.137 221 8bf4dee6f3a 223@BLF Idle dialog-info+xml

192.168.15.136 322 feb4f087b1f 328@BLF Idle dialog-info+xml

192.168.15.136 322 2297cf3b5c8 335@BLF Idle dialog-info+xml

192.168.15.136 322 3f4e2a937b6 334@BLF Idle dialog-info+xml

192.168.15.136 322 d286f34be20 331@BLF Idle dialog-info+xml

192.168.15.136 322 fd192d264d2 325@BLF Idle dialog-info+xml

192.168.15.136 322 cfa8b998315 323@BLF Idle dialog-info+xml

192.168.15.136 322 f360f2c21dd 321@BLF Idle dialog-info+xml

192.168.15.136 322 4f697fde9c3 239@BLF Idle dialog-info+xml

192.168.15.136 322 08971f69646 240@BLF Idle dialog-info+xml

192.168.15.136 322 c734498205b 237@BLF Idle dialog-info+xml

192.168.15.136 322 971e267fff9 236@BLF Idle dialog-info+xml

192.168.15.136 322 87c5bf531e8 235@BLF Idle dialog-info+xml

192.168.15.136 322 41e8d7d3335 234@BLF Idle dialog-info+xml

192.168.15.136 322 2ec54cbb6f1 233@BLF InUse dialog-info+xml

192.168.15.136 322 830ca532c29 232@BLF Idle dialog-info+xml

192.168.15.136 322 e4a466791af 231@BLF Idle dialog-info+xml

192.168.15.136 322 96ef03014f3 230@BLF Idle dialog-info+xml

192.168.15.136 322 da7b63d612f 229@BLF Idle dialog-info+xml

192.168.15.136 322 6d2890ac8f6 228@BLF Unavailable dialog-info+xml

192.168.15.136 322 496aa5fb5b4 241@BLF InUse dialog-info+xml

192.168.15.136 322 5a4ef474a80 226@BLF Idle dialog-info+xml

192.168.15.136 322 77aaadd3e4c 225@BLF Idle dialog-info+xml

192.168.15.136 322 c69a0068545 224@BLF Idle dialog-info+xml

192.168.15.136 322 3c6ff9c7f8f 223@BLF Idle dialog-info+xml

192.168.15.126 222 fa6d6170b3b 331@BLF Idle dialog-info+xml

192.168.15.126 222 7fce86f4e58 328@BLF Idle dialog-info+xml

192.168.15.126 222 660944b8952 334@BLF Idle dialog-info+xml

192.168.15.126 222 7275bbd39db 321@BLF Idle dialog-info+xml

192.168.15.126 222 505b92bb03b 325@BLF Idle dialog-info+xml

192.168.15.126 222 5dc40eb855a 335@BLF Idle dialog-info+xml

192.168.15.126 222 34296dc00c1 323@BLF Idle dialog-info+xml

192.168.15.126 222 834d9031042 239@BLF Idle dialog-info+xml

192.168.15.126 222 e5ffce23ecc 240@BLF Idle dialog-info+xml

192.168.15.126 222 bcfa845069d 237@BLF Idle dialog-info+xml

192.168.15.126 222 48e0a2abe38 236@BLF Idle dialog-info+xml

192.168.15.126 222 a58d1d625c4 235@BLF Idle dialog-info+xml

192.168.15.126 222 8b33b220736 234@BLF Idle dialog-info+xml

192.168.15.126 222 42999cb0aa9 233@BLF InUse dialog-info+xml

192.168.15.126 222 db99fb31bb0 232@BLF Idle dialog-info+xml

192.168.15.126 222 8aa909f725d 231@BLF Idle dialog-info+xml

192.168.15.126 222 312d7afe2cc 230@BLF Idle dialog-info+xml

192.168.15.126 222 ea8e35d53d6 229@BLF Idle dialog-info+xml

192.168.15.126 222 322e67d1e1a 228@BLF Unavailable dialog-info+xml

192.168.15.126 222 1e4b2a4164c 241@BLF InUse dialog-info+xml

192.168.15.126 222 1345b9fea07 226@BLF Idle dialog-info+xml

192.168.15.126 222 f052e6c0162 225@BLF Idle dialog-info+xml

192.168.15.126 222 4c341b5c5b6 224@BLF Idle dialog-info+xml

192.168.15.126 222 f58febdecac 223@BLF Idle dialog-info+xml

72 active SIP subscriptions (221, 222 and 322 are the receptionists monitoring other extensions)

why did you change the

BLF context

the correct and original

You're right !

Erik, Thanks for you