Righto. Just wanted to make sure I wasn't the only one. It appears that, according to that issue, Polycom has slated a fix in version 3.2.3. I'm running this in a test environment so no biggie.
Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 3/2/2010 11:22 AM, Carolyn Beeton wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Josh Patten >> Sent: Tuesday, March 02, 2010 11:21 AM >> >> [repost from sipx-users] >> Running 4.1.6-018117 >> >> Is there anything special I have to set on an Audiocodes >> Mediant 1000 gateway to make Shared Call Appearance work with it? >> >> >> I have attached a merge log but it seems pretty obvious what >> the issue is here, just need some insight on how to fix it. >> >> > I suspect a Polycom issue in PolycomSoundPointIP-SPIP_550-UA/3.2.2.0477, > reported in http://track.sipfoundry.org/browse/XTRN-1000 > > The Contact in the Ringing message in frame 47: > <sip:[email protected]:5060;transport=tcp> > > The set which presses Hold sends in frame 106: NOTIFY(sip.rendering=no), > <target uri="sip:[email protected]:5060"> > > This NOTIFY is sent to the other set in frame 109. > > However, the INVITE at frame 156 is sent to > <sip:[email protected];user=phone> - the only > reference to this address. > > Notes in the issue indicates "Polycom issue ID: VOIP-56445" and > "Targeted for Polycom SIP 3.2.3" > > You may have better luck with the older Polycom firmware 3.1.3 > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
