Asterisk version is 1.4.21.1 and distribution is Centos 5 - i386. Case is consistent -- for example:
[SIP/7110xb]
type=extension
extension=7110
context=xb1
label=John
mailbox=7110@xb
extenvoicemail=*67110
is the definition related to the UserEvent shown earlier. Assuming you're matching the "Channel:" value with the [SIP/7110xb], there should be no case difference. Of course, you may mean something different.
I'm not getting presence values to update on the clients. For example, two users with FOP2 open in the browsers, one changes their state from Available to DND, neither user sees the state updated on the FOP2 display. If a user reloads the entire FOP2 display session in their browser, the state will show up. Asterisk is generating the UserEvents for the change. What's up here? Bug?
192.168.1.73 <- Event: UserEvent
192.168.1.73 <- Privilege: user,all
192.168.1.73 <- UserEvent: FOP2ASTDB
192.168.1.73 <- Action: UserEvent
192.168.1.73 <- Family: fop2state
192.168.1.73 <- Channel: SIP/7110xb
192.168.1.73 <- Value: Out to lunch
192.168.1.73 <- Server: 0
I'm getting a lot of errors on the fop2 server:
Can't call method "setState" on unblessed reference at script/fop2_server.pl line 2695.
Restarting the server will generally work, but it seems like there is a race condition of events appearing which is causing the internal Perl code to look at uninitialized data.
How should we specify multiple channel values in a button configuration?
[SIP/600]
type=extension
extension=600
context=from-internal
label=John Doe
mailbox=600@default
extenvoicemail=*600@default
channel=IAX2/600,SIP/600.2
or
[SIP/600]
type=extension
extension=600
context=from-internal
label=John Doe
mailbox=600@default
extenvoicemail=*600@default
channel=IAX2/600
channel=SIP/600.2