Does anyone have an end-to-end summary of how they have successfully set up the buddy feature including all the relevant Asterisk and Polycom config snippets. All I have been able to do so far is scrounge up bits and peices from the list and Wiki - nothing that covers the entire process... I think a lot of people would benefit from that (myself included)...
<br><br><br><div><span class="gmail_quote">On 10/3/06, <b class="gmail_sendername">Paul Dugas</b> &lt;<a href="mailto:paul@dugas.cc">paul@dugas.cc</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Install went fine.&nbsp;&nbsp;No troubles other than this and it'd be minor if one<br>of the reasons for the update wasn't to expand the number of buddies<br>allowed on the IP601+sidecards we're adding for the attendant.&nbsp;&nbsp;Ugh...<br>
<br>Anyway, directory entries haven't changed:<br><br>&lt;?xml version=&quot;1.0&quot; standalone=&quot;yes&quot;?&gt;^M<br>&lt;!-- $Revision: 1.2 $&nbsp;&nbsp;$Date: 2004/12/21 18:28:05 $ --&gt;&lt;directory&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;item_list&gt;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;item&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;ln&gt;Doe&lt;/ln&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;fn&gt;Jane&lt;/fn&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;ct&gt;1001&lt;/ct&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;sd&gt;1&lt;/sd&gt;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;bw&gt;1&lt;/bw&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/item&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/item_list&gt;<br>&lt;/directory&gt;<br><br>The config entries you referred to are set in my global sip.cfg and<br>apply to all of the units.&nbsp;&nbsp;Looks right to me.
<br><br>Did some sniffing and Asterisk is sending a NOTIFY like so:<br>...<br>&lt;?xml version=&quot;1.0&quot; encoding=&quot;ISO-8859-1&quot;?&gt;<br>&lt;presence xmlns=&quot;urn:ietf:params:xml:ns:pidf&quot;<br>xmlns:pp=&quot;urn:ietf:params:xml:ns:pidf:person&quot;
<br>xmlns:es=&quot;urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status&quot;<br>xmlns:ep=&quot;urn:ietf:params:xml:ns:pidf:rpid:rpid-person&quot;<br>entity=&quot;<a href="mailto:sip:x1002@example.net">sip:x1002@example.net
</a>&quot;&gt;<br>&lt;pp:person&gt;&lt;status&gt;<br>&lt;/status&gt;&lt;/pp:person&gt;<br>&lt;note&gt;Ready&lt;/note&gt;<br>&lt;tuple id=&quot;1001&quot;&gt;<br>&lt;contact priority=&quot;1&quot;&gt;<a href="mailto:sip:1001@example.net">
sip:1001@example.net</a>&lt;/contact&gt;<br>&lt;status&gt;&lt;basic&gt;open&lt;/basic&gt;&lt;/status&gt;<br>&lt;/tuple&gt;<br>&lt;/presence&gt;<br><br>---<br> Extension Changed 1001 new state Idle for Notify User x1002<br>
pbx*CLI&gt;<br><br>Hmmm....<br><br><br><br>On Mon, 2006-10-02 at 22:14 -0400, Scott Higginbotham wrote:<br>&gt; I did the same thing with the Polycom's - upgraded all mine from 1.6.x to<br>&gt; 2.0.1 but I had great success and no problem with the buddy watch / presence
<br>&gt; feature --- if anything, it works a little better.<br>&gt;<br>&gt; Whats your &lt;mac-address&gt;-directory.xml configuration file look like?&nbsp;&nbsp;Did<br>&gt; you make any changes to the &lt;mac-address-phone.cfg file?&nbsp;&nbsp;do you have the
<br>&gt; line of:<br>&gt;<br>&gt; up.useDirectoryNames=&quot;1&quot; feature.1.name=&quot;presence&quot; feature.1.enabled=&quot;1&quot;<br>&gt;<br>&gt; In the config?<br>&gt;<br>&gt; Scott Higginbotham<br>&gt; Systems / Network Operations Manager
<br>&gt; 215.259.2185 or 1.800.835.5710 ext 2185<br>&gt; <a href="mailto:scotth@voicenet.com">scotth@voicenet.com</a><br>&gt;<br>&gt; -----Original Message-----<br>&gt; From: <a href="mailto:asterisk-users-bounces@lists.digium.com">
asterisk-users-bounces@lists.digium.com</a><br>&gt; [mailto:<a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>]On Behalf Of Paul Dugas<br>&gt; Sent: Monday, October 02, 2006 8:01 PM
<br>&gt; To: Asterisk Users Mailing List - Non-Commercial Discussion<br>&gt; Subject: [asterisk-users] Polycom Buddy Watch Broken with 2.0.1<br>&gt; Firmware?<br>&gt;<br>&gt;<br>&gt; I updated a batch of Polycom IP501 phones and an IP601 to the 
2.0.1<br>&gt; firmware to get the new NAT keep-alive feature and the ability to watch<br>&gt; more than a handful of buddy contacts but it appears to have broken the<br>&gt; buddy-watch feature.&nbsp;&nbsp;Is anyone seeing this?&nbsp;&nbsp;Anybody know if it's a
<br>&gt; Polycom problem or something on the Asterisk end?<br>&gt;<br>&gt; I'm running a recent (2 days ago) copy of the 1.2 trunk.&nbsp;&nbsp;In a rather<br>&gt; bone-headed move, I updated the firmware and Asterisk at the same time
<br>&gt; so I'm unable to tell which is the culprit.<br>&gt;<br>&gt; Curious,<br>&gt;<br>&gt; Paul<br>&gt;<br>&gt; --<br>&gt; Paul Dugas, Computer Engineer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Dugas Enterprises, LLC<br>&gt; <a href="mailto:paul@dugas.cc">
paul@dugas.cc</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;phone: 404-932-1355&nbsp;&nbsp;&nbsp;&nbsp; 522 Black Canyon Park<br>&gt; <a href="http://dugas.cc">http://dugas.cc</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;fax: 866-751-6494&nbsp;&nbsp;&nbsp;&nbsp; Canton, GA 30114 USA<br>&gt; --<br>&gt; This e-mail and any attachments are confidential.&nbsp;&nbsp;If you receive
<br>&gt; this message in error or are not the intended recipient, you should<br>&gt; not retain, distribute, disclose or use any of this information and<br>&gt; you should destroy the e-mail and any attachments or copies.
<br>&gt;<br>&gt; _______________________________________________<br>&gt; --Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br>&gt;<br>&gt; asterisk-users mailing list<br>&gt; To UNSUBSCRIBE or update options visit:
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>--<br>Paul Dugas, Computer Engineer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Dugas Enterprises, LLC<br><a href="mailto:paul@dugas.cc">
paul@dugas.cc</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;phone: 404-932-1355&nbsp;&nbsp;&nbsp;&nbsp; 522 Black Canyon Park<br><a href="http://dugas.cc">http://dugas.cc</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;fax: 866-751-6494&nbsp;&nbsp;&nbsp;&nbsp; Canton, GA 30114 USA<br>--<br>This e-mail and any attachments are confidential.&nbsp;&nbsp;If you receive
<br>this message in error or are not the intended recipient, you should<br>not retain, distribute, disclose or use any of this information and<br>you should destroy the e-mail and any attachments or copies.<br><br><br>_______________________________________________
<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br>&nbsp;&nbsp; <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br><br><br><br></blockquote></div><br>