Hello Vik,
BLF behaviour is somewhat erratic since major changes done after 15-Oct-2011. I am working with Anthony to track it down (see FS-3794). It happens mostly on our production system rather than the test system, so I am quite limited in testing the fixes and it takes time...
Here is a sample config of phone 11111 doing BLF on 22222:
<reginfo>
<reg reg.1.displayName="Full name" reg.1.address="11111" reg.1.label="11111" reg.1.type="shared" reg.1.auth.userId="11111" reg.1.auth.password="PPPPPP" reg.1.ringType="2" />
<attendant attendant.resourceList.1.address="22222" attendant.resourceList.1.label="22222" />
</reginfo>
Note that ThirdPartyName is not used in the REG section.
Regards, __Yehavi:
2012/2/9 Vik Killa
<vipkilla@gmail.com>
Would anyone be willing to share their working BLF polycom configs?
On Wed, Feb 8, 2012 at 4:56 PM, Anthony Minessale
<
anthony.minessale@gmail.com> wrote:
> It should be working but you can use that data to see why.
> If you enable sip trace too and capture the logs, it can be used to
> check for problems