There was an additional field added to the BLF signaling in SIP 3.1. This parameter is the 'direction' attribute specified in RFC4235. It is used to differentiate between and outgoing and incoming call to a phone; both of which have a BLF state of 'proceeding'. The phone will only 'blink the LED' for proceeding calls which have a direction="recipient"
For more details I recommend that you take a capture of the BLF signaling for a phone dialing out and receiving a call whilst being monitored. I'll leave it to others more knowledgeable than me to assess whether this will impact the sipXecs BLF implementation. Marek -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Mossman Sent: Thursday, September 25, 2008 5:56 AM To: Tony Graziano; [email protected] Subject: Re: [sipX-dev] XCF-2840 (Polycom 3.1 firmware support insipxconfig) and enhanced BLF Tony wrote: > We also got the impression the template was "off" and see this if a phone gets > mismatched configuration files. The configuration files are off somewhat, but I haven't found any major problem. The most significant issue I've found is that the SoundStation IP 6000 output audio is too low. > We use a working demo of the Polycom applications (weather, stock, news headlines) that > scroll the idle display of the microbrowse. I've never exercised this feature, nor EFK. > Our biggest concern was that if the EFK keys or enhanced BLF was not going to > work on 3.10.2 or 3.10.3(4) it should not be offered and should wait for 4.0. I > suspect the RLS server doesn't understand how to interpret some of the new dialogue > sequences from the phone and am wondering if a template fix is going to properly cure > it. I don't think the new Polycom firmware has changed the Dialog Event NOTIFYs sent by the phone, so sipXrls behaviour when consuming these should not have changed. (But, maybe it has changed?) > **No, on 650's. > **Consistently inaccurate for long periods, as in 12-36 hours on a network > with no calls coming on or out (weekend). Wait 12 hours, reboot the phones and > sipx, still no change 12 hours later, etc. You should raise an issue for this. A trace capturing boot up of the phone right through to the point at which BLF indication becomes inaccurate would be most useful. Also ideal if the trace includes messaging to/from the phone whose BLF indication is incorrect. Thanks. -Paul [EMAIL PROTECTED] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
