[VoiceOps] Polycom BLF w/ SBC

[Jay Stewart]

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