Hi

Due to problems we are having with the quality of our calls and paging, we are looking at moving out Samsung phone system onto a seperate VLAN. We are using Cisco switches and ITP-5114D phones.

Has anyone had any experience of doing this and can anyone point me in the right direction of a samsung manual covering how to set this up?

Many thanks

Richard

The only change you might need to make in your phone system is the IP address. The setup of the VLAN will be done in your switches and router.

How many phones are we talking about? I've setup over 200 ITP phones on the same network and not had any problems.

What codec are you using for the phones?

We have about 150 phones on the network we are using codec 729

The vlan setup will be done on the switches, but I'm struggling to see how as the pc's plug into the phones and then the phones into the switch. How the switch will differentiate between the devices

You will not be able to create a different VLAN if you are running the data through the phone.

If you want to do VLAN's you will need a seperate data drop at each location. One for the phone and one for the PC.

I do not believe this last post is correct.

The IP phones do have the ability to set up a VLAN within the phone and the Second Ethernet port can be in a different VLAN than the Phone itself.

This does of course require a VLAN capable switch to feed the phone.

The Samsung GPLIM/GSIM combination can provide this feature.

The last time I talked to Samsung, the feature was not available. This might have changed in the last year. I'll put in a ticket and ask if it can be done.

You can only have one untagged VLAN on a network cable as there is nothing in the packet to specify VLANs, but if the switch and devices support 802.1Q then you can have many additional tagged VLANs on the same cable as these have an additional header between the destination/source MAC address and type/length field which specifies which VLAN the packet is associated with.

Certainly if your existing network has alot of broadcast traffic this may be taxing the phones as they have to process each of these broadcasts, even if it is to just drop them. VLANs will reduce the size of the broadcast domain but introduce extra complexity - you will need different IP addresses on each VLAN and routing between them and the outside world as appropriate to your setup.

Have you had a look at the traffic flows on the network, it may be that you have occasional saturation of links between switches so faster links or QoS may be a better solution.

On the latest software for the ITP phones you can log in and set a Vlan ID. Tech Support has a step by step document that shows how to do this.

Wow... that's actually good news! I just plugged in one of my ITP phones, updated the software and what do you know... there's a menu for Network Setup.

That's the one thing that Samsung struggles with... getting updated information to its dealers.

I bought a 48-port Netgear POE switch just to play with setting up VLANs and learn it on my own. Never has something that is so simple - or supposedly simple - been such a pain. Managed switches, bleech. Until someone can really convince me how or why internal IP phones are a better idea than digital, I am sticking to digital sets. Have been very successful in sitting down prospects and explaining to them that going with internal IP phones is just asking for a sack of unnecessary headaches.

That sad, we are all 'against' something we are not comfortable with - and I am not confortable with all-IP systems. Hopefully I'll die before all systems are IP.

Here Here, well at least retired, maybe not dead

Maybe my IT support background helps, but VLAN's for seperating VoIP and normal data arn't that hard to setup.
Maybe netgear make it hard, but on the cisco's (and the GPLIM/GSIM's since the program on them was written by ex cisco engineers) its fairly easy.

But I don't see the need for a fully ip system, other then it makes phone relocation easier (just unplug your phone and plug it in at your new desk)

OK, Ive setup the vlan now.
FYI on Cisco 3500 XL switches I had to set al ports as trunk ports with 802.1Q encapsulation.
I have 3 lans 100 for phones, 110 for data and 120 for management. The default COS on the ports is 0

Once I had updated all phones to be on a suitabl firmware vesion I configured them as follows:

LAN Port 1 100 7 = Enabed On Vlan 100 with COS of 7

PC Port 1 1 1 = Enabled on VLAN 110 with COS of 1

I have set the port the OfficeServ Pluggs into as an access port on VLAN 100 so it only allows traffic from VLAN 100 to pass through.

The voice mil system (which uses our data network t email messages) has been plugged ino an access port on the switch on VLAN 110.

No reportasyet (touch wood) of and clarity problems.

We have however had 1 instance of a page problem. This occurs whn a user tries a page. They press ** to page all users (including a tannoy system) the beeps start but do not finish and the user cannot page. Has anyone seen this error before?

Sorry that should have read

PC Port 1 110 1 = Enabled on VLAN 110 with COS of 1

What MGI card are you using and how many members are in your page group? Do you have the MGI card set to USE under Remote MGI in programming?

I ran into this problem and I had more members in the page group than MGI channels. Reducing the number of members corrected the problem. I don't know if this is your problem, but it's a good place to start.