miconda at gmail.com
Wed May 7 10:53:32 CEST 2014
If you want to manage blf via kamailio, then you need dialog +
pua_dialoginfo as well. Or look at sca for an alternate specs which i
think is supported by polycom, but not sure about grandstream.
If you manage blf by freeswitch (when all calls are routed to freeswitch
always), then you should just forward subscribes for dialog-info event
On 06/05/14 14:56, Joel White wrote:
> Thank you Olle
> I am looking into it now. I currently have presence presence_xml and
> presence_dialoginfo enabled. I will look into pua today.
> On Tue, May 6, 2014 at 3:12 AM, Olle E. Johansson <oej at edvina.net
> <mailto:oej at edvina.net>> wrote:
> On 05 May 2014, at 19:21, Joel White <joelewhite at gmail.com
> <mailto:joelewhite at gmail.com>> wrote:
> > I am working on enabling presence and bla in a Kamailio +
> FreeSWITCH environment
> > All handsets are Polycom with a handful of Grandstream ATA's
> > I enabled presence and presence_xml
> > I have not got it to work as I keep seeing this meesage in the logs
> > NOTICE: presence [subscribe.c:1030]: handle_subscribe():
> Unsupported presence event call-info
> > When I searched online for this error, the answers I got were
> saying this was a Linksys/Snom message....
> > How do I get presence to work properly?
> By learning how it works ;-)
> SIP has what we call event packages. These are mapping states of
> an object. A server can learn the state internally (through one of
> our PUA* modules) or by getting PUBLISH statements from the object.
> Each event package has a name - presence, dialog and many more.
> To get what you call presence to work you need to select which
> event packages you want to work with, depending on what you want
> to do. If you want to subscribe to certificates, it's
> "certificate", if it's voicemail it's "message-summary". For
> blinking lamps, I would say "dialog" and for buddy-lists and "I'm
> in a meeting" type presence, it's simply "presence". There are
> many vendor-specific packages and solutions for "bla".
> When you've made your choice, select the proper kamailio modules,
> configure all your clients to the same event package if possible
> and things will start working. Now, if a phone use "call-info"
> that's not IETF/IANA specified, and another device use "presence"
> and a third one "dialog" you will not get any interoperability.
> The error message above indicates "call-info" and kamailio says it
> doesn't understand this event package with the current Kamailio
> configuration. Read the docs for all the pua* and presence*
> modules in Kamailio and start solving this puzzle. I would go for
> "dialog" for most of the cases with blinking lamps, but that's my
> personal preference.
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sr-users