<![CDATA[Presence Updates]]>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
]]>http://localhost:4567/topic/107/presence-updatesRSS for NodeTue, 27 Oct 2026 04:53:48 GMTTue, 15 Sep 2009 20:35:47 GMT60<![CDATA[Reply to Presence Updates on Thu, 17 Sep 2009 18:59:17 GMT]]>I do not recall exactly the case issue I mentioned. Please contact me via the live chat (I am logged on right now). I can send you the updated daemon to see if it fixes the issue or not. Best regards,

]]>http://localhost:4567/post/516http://localhost:4567/post/516Thu, 17 Sep 2009 18:59:17 GMT<![CDATA[Reply to Presence Updates on Thu, 17 Sep 2009 18:22:59 GMT]]>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.

]]>http://localhost:4567/post/515http://localhost:4567/post/515Thu, 17 Sep 2009 18:22:59 GMT<![CDATA[Reply to Presence Updates on Wed, 16 Sep 2009 01:50:25 GMT]]>What asterisk version are you using? What distribution are you using? All I can say is: "it works for me". I fixed a bug some time ago involving case in channel names, I see you have mixed case in the device name, and maybe you are bitten by that bug. It is already fixed in the devel version I believe. If you tell me the distribution you use I can send you an update, that it might also fix the other problem you reported.

Regards,

]]>http://localhost:4567/post/514http://localhost:4567/post/514Wed, 16 Sep 2009 01:50:25 GMT