HI All, Has anyone ever had luck with getting Polycom BLF to work through a non-Broadworks SBC? We're looking at internally moving to a SEMS based SBC.. However we've had 0 luck so far with getting any BLF from Polycom to function... Thanks David -- [image: Ringfree Communications, Inc] <http://ringfree.biz/> David Wessell / President 828-575-0030 x101/ david at ringfree.biz Ringfree Communications, Inc Office: 828-575-0030 / Fax: 888-243-7830 PO BOX 1994 Hendersonville, NC 28793 http://ringfree.biz This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
On 04/27/2015 01:03 PM, David Wessell wrote:
HI All,
Has anyone ever had luck with getting Polycom BLF to work through a non-Broadworks SBC?
We're looking at internally moving to a SEMS based SBC.. However we've had 0 luck so far with getting any BLF from Polycom to function...
This is still a PBX-level feature, and any "SBC" should just pass the relevant subscriptions and notifications through. SBCs do not provide any application-level functionality that relates to handsets or user experience. -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Watch out for the size of the BFL packets. They could very well not fit through the SBC if it is configured improperly or by default. I am quite sure ACME default breaks it while Metaswitch Perimeta's default works. Matt ________________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Alex Balashov <abalashov at evaristesys.com> Sent: Monday, April 27, 2015 1:05 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom BLF w/ SBC On 04/27/2015 01:03 PM, David Wessell wrote:
HI All,
Has anyone ever had luck with getting Polycom BLF to work through a non-Broadworks SBC?
We're looking at internally moving to a SEMS based SBC.. However we've had 0 luck so far with getting any BLF from Polycom to function...
This is still a PBX-level feature, and any "SBC" should just pass the relevant subscriptions and notifications through. SBCs do not provide any application-level functionality that relates to handsets or user experience. -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Two thoughts - 1. For Polycom there used to be the restriction of using TCP vs. UDP for signalling and there were still BLF list size limitations. I think though that this was an issue with the phone not handling fragmented packets and was corrected in later software. What model of phones and what version of firmware are you running? 2. Like Matt said, it could be a packet size issue. On the Acme SBC you had to change a default setting (max allowed packet size maybe?) to get it working, is there a similar setting on your SBC? Have you looked at the XS logs to make sure the AS is seeing the subscribes or sending the notifies, or have you done a packet capture to see if the subscriptions and notifies are making it to and through the SBC? Rob -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Matthew Yaklin Sent: Monday, April 27, 2015 1:36 PM To: Alex Balashov; voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom BLF w/ SBC Watch out for the size of the BFL packets. They could very well not fit through the SBC if it is configured improperly or by default. I am quite sure ACME default breaks it while Metaswitch Perimeta's default works. Matt ________________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Alex Balashov <abalashov at evaristesys.com> Sent: Monday, April 27, 2015 1:05 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom BLF w/ SBC On 04/27/2015 01:03 PM, David Wessell wrote:
HI All,
Has anyone ever had luck with getting Polycom BLF to work through a non-Broadworks SBC?
We're looking at internally moving to a SEMS based SBC.. However we've had 0 luck so far with getting any BLF from Polycom to function...
This is still a PBX-level feature, and any "SBC" should just pass the relevant subscriptions and notifications through. SBCs do not provide any application-level functionality that relates to handsets or user experience. -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Definitely turn on TCP for testing. Depending on the functionality of the SBC in question, we've seen discrepancies between BroadWorks supports SBC's and BLF. For PolyCom Make sure your SBC Outbound Proxy Port is set in addition to your registration address, and pending your deployment, they match values: reg.X.server.1.address="%PROXY%" reg.X.outboundProxy.address="%PROXY%" You may need to tweek the attendant uri field as well: attendant.uri="%BWBLF-USER-1%" --> Was "%BWBLF-URI-1%" Jay Stewart NextOS Sr. Systems Administrator (480) 426-0099 | jstewart at nextiva.com 8800 E. Chaparral Road, Suite 300 | Scottsdale, AZ 85250 -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Rob Dawson Sent: Monday, April 27, 2015 11:53 AM To: Matthew Yaklin; Alex Balashov; voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom BLF w/ SBC Two thoughts - 1. For Polycom there used to be the restriction of using TCP vs. UDP for signalling and there were still BLF list size limitations. I think though that this was an issue with the phone not handling fragmented packets and was corrected in later software. What model of phones and what version of firmware are you running? 2. Like Matt said, it could be a packet size issue. On the Acme SBC you had to change a default setting (max allowed packet size maybe?) to get it working, is there a similar setting on your SBC? Have you looked at the XS logs to make sure the AS is seeing the subscribes or sending the notifies, or have you done a packet capture to see if the subscriptions and notifies are making it to and through the SBC? Rob -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Matthew Yaklin Sent: Monday, April 27, 2015 1:36 PM To: Alex Balashov; voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom BLF w/ SBC Watch out for the size of the BFL packets. They could very well not fit through the SBC if it is configured improperly or by default. I am quite sure ACME default breaks it while Metaswitch Perimeta's default works. Matt ________________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Alex Balashov <abalashov at evaristesys.com> Sent: Monday, April 27, 2015 1:05 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom BLF w/ SBC On 04/27/2015 01:03 PM, David Wessell wrote:
HI All,
Has anyone ever had luck with getting Polycom BLF to work through a non-Broadworks SBC?
We're looking at internally moving to a SEMS based SBC.. However we've had 0 luck so far with getting any BLF from Polycom to function...
This is still a PBX-level feature, and any "SBC" should just pass the relevant subscriptions and notifications through. SBCs do not provide any application-level functionality that relates to handsets or user experience. -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On 4/27/15 10:03 AM, David Wessell wrote:
HI All,
Has anyone ever had luck with getting Polycom BLF to work through a non-Broadworks SBC?
We are using Sansay SBCs, Polycom phones with BLF, and Broadworks. No issues with the SBCs, but make sure that if you have a SIP ALG or NAT box it needs to be able to reassemble large UDP SIP fragmented packets. Adtran 3120 is a problem, for example. Adtran TA900e series are fine. In some cases if the CPE isn't under your control, changing transport to TCP will resolve the issue. BLFs are chatty and if you have several on a phone you may be looking at three or even four 1500-byte fragments per message. -- Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
participants (6)
-
abalashov＠evaristesys.com -
david＠ringfree.biz -
jay＠west.net -
jstewart＠nextiva.com -
myaklin＠firstlight.net -
rdawson＠force3.com