<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I had a similar issue using the older Polycom OS and BLF using the directory and buddy watch (xpidf+xml) that Freeswitch supports really well.</div><div class=""><br class=""></div><div class="">However, after upgrading the Polycom’s and using the newer attendant.resourceList method for BLF, I found that they use the standard dialoginfo supported by OpenSIPS’ presence_dialoginfo module.</div><div class=""><br class=""></div><div class="">Jarrod</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Jan 26, 2016, at 9:59 AM, Newlin, Ben <<a href="mailto:Ben.Newlin@inin.com" class="">Ben.Newlin@inin.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">
<div class="">I know I have used presence extensively with Polycom phones using pidf+xml. I know they support it. Maybe there is some setting in your model specifying the remote server type? If that is set to Microsoft Lync the Polycom may be sending xpidf for compatibility.</div>
<div class=""><br class="">
</div>
<div class="">But Polycom phones absolutely support pidf+xml. We implemented a presence feature last year using only Polycom and SIP SIMPLE.</div>
<div class="">
<div id="MAC_OUTLOOK_SIGNATURE" class="">
<div class=""><br class="">
</div>
<div class="">Ben Newlin</div></div></div></div></div></div></blockquote></div></body></html>