OAM Port on BCM50

[pandster]

I am using the standard LAN port on one subnet/vlan for my ip sets and want to use the OAM port for access to callpilot. Has anyone tried using the OAM port for anything except management? I am hoping that as a Linux box the OAM port is just a standard ethernet port and this will work.

 

[option11newby]

Use the OAM port to connect via Element Manager, then when connected, go to Configuration, at the bottom, open Applications, click on Voice Messaging, and on the right hand window, click on Launch Call Pilot

 

[pandster]

I think you are missing the point. What I mean is I want to use it for client to connect to callpilot - not manage callpilot.

 

[option11newby]

Sorry, I mis-interpreted what you said. I thought the OAM port was solely for managing the system.

Sorry for the confusion

 

[biv343]

It is only supported for management. Not to mention only one PC can connect to it.

Why not just access CallPilot via the LAN port? There won't enough traffic for the IP phones to care about.

 

[pandster]

I am doing that just now and yes it should work but I am havin intermitant connection problems to the BCM Call pilot interface. The PC's and Microsoft Server are on vlan 10 and the BCm on vlan 30. Both on subnetted 10.x.x.x private addresses. i have tried routing within the Microsoft Server (quad attached) and also within the Netgear Poe level 3 managed switch but still I am havin problems. i thought one solution would to have been to set up a vlan 10 local lan ip on the BCM and then routing would not be required. Of course had I bought the bcm50e then I would have another port I coulf do this with but hindsight is a wonderful thing and my supplier has informed me there is no upgrade path. I want to do alot with my BCM but unless I can get callpilot to work reliably then I am restricted.