PON And IP Cameras Problem

We have recently partnered with a client who has deployed a new Passive Optical Network in which cameras are being deployed on a Genetec system. Unfortunately, the process of enrolling the cameras is cumbersome to say the least mostly because the vendor who provided the PON has full control over configuration and the client has little to no visibility or experience configuring this type of network deployment.

We, as the integrator, are left with cameras that are not visible on the network when we attempt to enroll that are "magically" fixed after the PON vendor is notified. Our problem is that the PON vendor is maintaining that the issue is with the camera (Samsung) and not their network, yet they will not share the process that they are following to resolve the issue. We have no access to the network configuration.

My questions are:

  1. What considerations are necessary when designing a Passive Optical Network that will manage not only standard business operations but also a large number of IP cameras?
  2. Are there considerations when enrolling cameras on a PON that is different from a standard network deployment (I really can't imagine what)?
  3. Anyone with experience running IP cameras on a PON have recommendations, words of caution or thoughts to share as we continue to move forward?
Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

*, ******. ** *******, ** *** *** ****** ** *** 'end' *** *** ** ******* ** *** '*****', *.*., *** the ******* ******** ** *** **** ** *** *** *** the *** ******(*) ** *** ****? * ** ******** ** but **** ** ** ****.

"**, ** *** **********, *** **** **** ******* **** *** not ******* ** *** ******* **** ** ******* ** ****** that *** "*********" ***** ***** *** *** ****** ** ********."

**** *** *** *** *******, *** **** *******'* ********* ******** can *** **** ****** **** ** ** *** **** **** if *** ******** ***** *** ** ********* **** *******, ******* cannot *******?

** *** *** ******* ***** ******, ** *** ******* ****** feedback.

** *******:

***, *** *** ****** ** ** *** "***" *** *** IP ******* *** ** *** "*****" *** ** *** ******* Optical *******.

**** *******, *** **** *** ** *** **** *** ****** with *** *** ********* **** *** ** **** ****** **** ping ** ** *** ******* **** ******* ************.

** ****** **** ***** ********** *** ** ********* ** *** the ******* ************* ***. ** ******* **** *** ****** ** not ******* *** ***** *********, ** ******** *** ******** *** ports *** ** *** ******* **** *** **** *** ********* it ** ** ***** **** *** ****** *************.

****: ** **** ******** * "****" ****** ** *** ******* vendor *** **** ** *** ** ***** "***" *****, ** course, ***** ******* ****. ** *** **** *** ****** *** another "****" ****** **** *** ******** ******** ** *** ******'* network ** **** *** **** ***** ** ***** ***.

*** ****** ** ******* ***-**** *** ***-*****.

** *** ****** **** * ****** ***** ** ** ""*********" ***** ***** *** *** ****** ** ********", ** ********* to ** **** **** ** * ******* ************* *****. * have *** **** * *** ** ***** ** * ****** make *** **** ******** ********.

*'** ********* **** ** ******* ** *** ** **** **** any ********** ** ******** ****.

**** *******, *** **** *** ** *** **** *** ****** with *** *** ********* **** *** ** **** ****** **** ping ** ** *** ******* **** ******* ************.

********, *** *** *** **'* ********? ******* **** ********** *** not ***** ********* **** *** ****?

** *** ****'* *******, *** ******* **** ** **** ***** IPs, ** **** **** ******* *****. ** ** ***** *****'* work **** * ***** **, *** ******* ** ** ** IP ** ** ********* ****** **** ** ** *** *******. Then **** ****.

If ** ***** ** ** ********* ****** **** *** ** *** *** *******, **** ****** **** ***** **** **'* *** *******.