Cisco SPA + BLF behavior
I noticed that on a Cisco SPA500 series phone, when configured to do BLF+SD+CP for an extension, the LED for that line on the SPA does not turn red when the line goes off-hook on another phone. It turns RED when the call is actually in progress (ie after the number has been dialed and it's ringing). This behavior is different than when the same line is configured as a shared line appearance on the SPA, the LED turns red immedialtely when the line goes off hook on another phone. It appears FreeSWITCH is sending the same SIP NOTIFY event in both cases with line showing seized (appearance-index=1;appearance-state=seized), so I'm think this might be a bug in the phone's firmware, which is running the latest version, 7.5.6a. I did try a couple older version and had the same results. Am I missing something or is this the behavior of this phone? Should I bother to open a TAC case with Cisco, the behavior seems buggy to me?
Hello Gabriel, What revision of Freeswitch are you running currently? Best regards, Robert Stevens rstevens@robcoit.com ________________________________ From: freeswitch-users-bounces@lists.freeswitch.org <freeswitch-users-bounces@lists.freeswitch.org> on behalf of Gabriel Kuri <gkuri@ieee.org> Sent: Tuesday, January 13, 2015 2:13 AM To: FreeSWITCH Users Help Subject: [Freeswitch-users] Cisco SPA + BLF behavior I noticed that on a Cisco SPA500 series phone, when configured to do BLF+SD+CP for an extension, the LED for that line on the SPA does not turn red when the line goes off-hook on another phone. It turns RED when the call is actually in progress (ie after the number has been dialed and it's ringing). This behavior is different than when the same line is configured as a shared line appearance on the SPA, the LED turns red immedialtely when the line goes off hook on another phone. It appears FreeSWITCH is sending the same SIP NOTIFY event in both cases with line showing seized (appearance-index=1;appearance-state=seized), so I'm think this might be a bug in the phone's firmware, which is running the latest version, 7.5.6a. I did try a couple older version and had the same results. Am I missing something or is this the behavior of this phone? Should I bother to open a TAC case with Cisco, the behavior seems buggy to me?
The latest "release", 1.4.15. I don't think it's Freeswitch, as I do see the the appropriate SIP NOTIFY messages coming from Freeswitch to tell the phone the line has been taken off hook (seized), but the phone just doesn't change the light to red, until an actual call is in progress. However when the line on the SPA is setup as a shared line appearance, it works fine when a remote phone takes the line off hook, it's seems to be the BLF mode that doesn't work correctly. On Tue, Jan 13, 2015 at 5:06 PM, Robert Stevens <rstevens@robcoit.com> wrote:
Hello Gabriel,
What revision of Freeswitch are you running currently?
Best regards,
Robert Stevens *rstevens@robcoit.com <rstevens@robcoit.com>* ------------------------------ *From:* freeswitch-users-bounces@lists.freeswitch.org < freeswitch-users-bounces@lists.freeswitch.org> on behalf of Gabriel Kuri < gkuri@ieee.org> *Sent:* Tuesday, January 13, 2015 2:13 AM *To:* FreeSWITCH Users Help *Subject:* [Freeswitch-users] Cisco SPA + BLF behavior
I noticed that on a Cisco SPA500 series phone, when configured to do BLF+SD+CP for an extension, the LED for that line on the SPA does not turn red when the line goes off-hook on another phone. It turns RED when the call is actually in progress (ie after the number has been dialed and it's ringing). This behavior is different than when the same line is configured as a shared line appearance on the SPA, the LED turns red immedialtely when the line goes off hook on another phone. It appears FreeSWITCH is sending the same SIP NOTIFY event in both cases with line showing seized (appearance-index=1;appearance-state=seized), so I'm think this might be a bug in the phone's firmware, which is running the latest version, 7.5.6a. I did try a couple older version and had the same results. Am I missing something or is this the behavior of this phone? Should I bother to open a TAC case with Cisco, the behavior seems buggy to me?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
Gabriel Kuri
-
Robert Stevens