-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Video Conferencing
- Collaboration & Conferencing Platforms
- BFCP with RPAD port rules are incorrect
Create an account on the HP Community to personalize your profile and ask a question
06-17-2014 09:12 PM
Hi there,
I have noticed an issue with BFCP Content Sharing when traversing the RPAD.
In the official documentation from Polycom it states that you only need to open outbound RTP traffic in one direction
eg. from the RMX Media IP > RPAD Internal NIC in the example of the MCU.
However I have found that BFCP does not work when traversing the RPAD. If you connect via RealPresence Desktop you cannot even press the content button at all via the Internet. After testing further this appears to be because when an inbound call comes into the RPAD we see the client tries and make an inbound UDP connection to the media port range of the RMX via the RPAD. This is obviously denied as the traffic must initiate from the RMX first and then the stateful reply is granted, and this in my view appears to break the BFCP component of the call.
After we opened up the RPAD > RMX Media IP in the opposite direction for media range we are now able to get BFCP to work when traversing the RPAD and can press the content button and share content.
Can Polycom confirm they have tested BFCP through the RPAD when landing a call on the RMX1500? and if so why is this issue occuring?
Note this issue is only exhibited with BFCP, H323 content sharing works.
Solved! Go to Solution.
Accepted Solutions
07-21-2014 01:38 AM
Hi there,
If anyone has this problem where they cannot send SIP content. This is the fix.
- Ensure on your RMX you setup the following system flag with a value of 3.
Flag : NUM_OF_INITIATE_HELLO_MESSAGE_IN_CALL_ESTABLISHMENT
Value : 3 - Ensure that your meeting is setup on DMA or RMX Conference Profile with "FW NAT keep alive" ticked.
Now content for SIP BFCP should work through the RPAD with only the default firewall ports.
Thanks to Billy Jo from Polycom for working on this issue.
07-21-2014 01:38 AM
Hi there,
If anyone has this problem where they cannot send SIP content. This is the fix.
- Ensure on your RMX you setup the following system flag with a value of 3.
Flag : NUM_OF_INITIATE_HELLO_MESSAGE_IN_CALL_ESTABLISHMENT
Value : 3 - Ensure that your meeting is setup on DMA or RMX Conference Profile with "FW NAT keep alive" ticked.
Now content for SIP BFCP should work through the RPAD with only the default firewall ports.
Thanks to Billy Jo from Polycom for working on this issue.
Didn't find what you were looking for? Ask the community