Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Cisco IP Communicator

Hi all,

Some questions about Cisco IP Communicator Software:

- What do you think about this Software?

- Does it support 802.1q? I think that I need a NIC card working with 802.1q. Is it correct?

Thats a lot.

27 REPLIES

Re: Cisco IP Communicator

IP Communicator is very nice. Depending on your situation, it can be very beneficial - mobile employees, etc. IP Communicator does not support 802.1q natively.

Hope this helps. If so, please rate the post.

Brandon

New Member

Re: Cisco IP Communicator

Hi Brandon,

When you said "Natively" there is some add-one? or all Voice trafic will be in Data Trafic.

Currently I have 2 Vlans, one data and one voice and using Auto-Qos.

What happen with this Software? All trafic in my Data Vlan?

I read that DSCP is supporting but no information about Vlans..

Thanks a lot again for your answer

Re: Cisco IP Communicator

There is no add on. All voice traffic from IPC will be in the data VLAN. Take a look at the following section of the QoS SRND linked below.

Campus QoS Design -> Catalyst 2970/3560/3750 - Untrusted PC + Softphone with Scavenger-Class QoS Model

QoS SRND

http://www.cisco.com/univercd/cc/td/doc/solution/esm/qossrnd.pdf

As also mentioned in this document, you can use the "auto qos voip cisco-softphone" command to generate a baseline QoS config that will take the softphone into account.

Hope this helps. If so, please rate the post.

Brandon

New Member

Re: Cisco IP Communicator

Great Brandon. Thank a lot

New Member

Re: Cisco IP Communicator

Hi Brandon,

Is it already the same behaviour for Cisco IP Communicator with CUCM 7.1 ?

Because I would like to separate the voice and data trafic. Is it possible ?

When I tested 2 VLANs on my computer (Voice Vlan Tagged, Data Vlan native), the IP Communicator registered on CUCM with IP Address of Voice VLAN, but when I do a traces on my PC, I see communication between IP Address of Data VLAN and IP Address of CUCM.

So what is the solution ?

For information, the switch is not a catalyst, but a Nortel swith.

Regards,

Davy

Re: Cisco IP Communicator

It could be that signaling is using the voice VLAN and RTP (audio) traffic is using the data VLAN. Check the setting in IPC under Preferences > Audio > Network > Audio IP Address.

Hope this helps.

Brandon

New Member

Re: Cisco IP Communicator

No the signaling message (SCCP) is using the voice VLAN.

I didn't test audio message (RTP).

But you said before in the post (3. 14 déc. 2007 08:11 En réponse à: fargier ) that all voice traffic from IPC will be in the data VLAN.

So maybe is it normal ?

Davy

New Member

Re: Cisco IP Communicator

Sorry No the signaling message (SCCP) is using the Data VLAN !

Re: Cisco IP Communicator

Signaling is using the data VLAN, but the IPC is registered with CUCM with the voice VLAN IP address? Seems strange.

New Member

Re: Cisco IP Communicator

Yes exactly.

Since I have 2 Vlans on my computer, when I do a "route print" on windows, I have 2 routes 0.0.0.0

One for Voice VLAN and one for Data VLAN

I changed metric for Data VLAN in order to have Data VLAN as the default Gateway for my computer.

Even if I add a specific route to the CUCM network, I have a communication between Data Vlan and CUCM.

What is the best implementation of IPC in order to separate Voice and Data trafic ? Is it possible ?

Did you already realize this kind of configuration with IPC ?

Thanks.

Davy

Re: Cisco IP Communicator

Did you check the setting I mentioned above?

New Member

Re: Cisco IP Communicator

Yes it is good, I have mentionned the right nic associated to voice vlan

Re: Cisco IP Communicator

What happens if you shut down the NIC in the data VLAN? Does IPC register/function properly on the voice VLAN?

New Member

Re: Cisco IP Communicator

If shut down the NIC in the data VLAN, then the registering on CUCM is the same, but in this case IPC function properly on the Voice Vlan.

Re: Cisco IP Communicator

Trying changing the NIC in Preferences > Network > Device Name.

New Member

Re: Cisco IP Communicator

Hi Brandon,

Sorry for the delay, I was on holidays.

I don't understand because in an earlier message, you said :

"There is no add on. All voice traffic from IPC will be in the data VLAN. Take a look at the following section of the QoS SRND linked below.

Campus QoS Design -> Catalyst 2970/3560/3750 - Untrusted PC + Softphone with Scavenger-Class QoS Model

QoS SRND

http://www.cisco.com/univercd/cc/td/doc/solution/esm/qossrnd.pdf

As also mentioned in this document, you can use the "auto qos voip cisco-softphone" command to generate a baseline QoS config that will take the softphone into account.

Hope this helps. If so, please rate the post."

So you said that is impossible to separate data and voice trafic with IPC. Is it exact ?

Regards,

Davy

Super Bronze

Re: Cisco IP Communicator

Hi Davy

It's a PC application; it's just not practical to have a Windows client machine on multiple subnets at once for several reasons.

Use one IP address, one NIC, allow the CIPC to bind to that NIC, and configure your network to trust and police the ingress voice and signalling traffic in line with what is in the SRND.


Regards


Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: Cisco IP Communicator

Hi,

Thanks you for your answer.

But my network is not a Cisco LAN, but a Nortel LAN.

So I can't apply the QoS command.

Even if there are several problems, for you, is it possible to separate data and voice trafic with IPC ?

With 802.1q on PC for example ?

Regards,

Davy

Super Bronze

Re: Cisco IP Communicator

Hi

Your Nortel switches will presumably support QoS for PC based applications; you would need to research the configuration required in the Nortel docs/forums to identify a similar configuration.

I'm not aware of anyone using CIPC in that fashion; having multiple NICs or dot1q interfaces on a Windows PC is just not a desirable setup. It is virtually guaranteed to cause you all sorts of problems with other applications further down the line. If some other data app ends up using your VVLAN there's a chance that some security or routing issue is going to break that app..

Regards

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: Cisco IP Communicator

Ok.

But with this method, a broacast flood can produce on the network.

Super Bronze

Re: Cisco IP Communicator

A broadcase flood can appear on the network regardless of the config of any one particular host on the network. Can you explain more what you believe the problem is?

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: Cisco IP Communicator

Hi,

In fact, if the IPC trafic is on the same VLAN as the PC trafic, we have no segmentation.

So If we have a problem on the DATA VLAN, it will impact the IPC communication, while it would be not the case if the IPC trafic was in a segmented VLAN.

Regards,

Davy

Super Bronze

Re: Cisco IP Communicator

If you have an endpoint connected to two VLANs via a dot1q trunk, a broadcast storm in either VLAN could cause you problems as they both share the same wire/bandwidth... so you have two potential sources of problems instead of one.

It's beside the point anyway - put your PCs in the data VLAN only, and run the CIPC from the data VLAN on a single IP. That is the standard deployment, and the only supportable deployment I'm aware of.


Regards

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: Cisco IP Communicator

Hi,

[If you have an endpoint connected to two VLANs via a dot1q trunk, a broadcast storm in either VLAN could cause you problems as they both share the same wire/bandwidth... so you have two potential sources of problems instead of one.]

==> Even if I configure QoS on the port and storm control ?

Super Bronze

Re: Cisco IP Communicator

Hi

If you protect the traffic with such measures for one VLAN, what is to stop you protecting the other VLAN? Those measures are not things you can use ONLY on the voice VLAN.

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: Cisco IP Communicator

If you protect the traffic with such measures for one VLAN, what is to stop you protecting the other VLAN?

==> Because the Voice VLAN is the most important, in order to have the telephony service always available, even if a broadcast storm occurs in the Data VLAN.

Thank you for your help.

Super Bronze

Re: Cisco IP Communicator

Hi

Your aim should be to protect legitimate traffic (including voice, but also including data) from excessively bulky or problem traffic. That doesn't mean you protect voice and everything else has to suffer.

Generally (at least on Cisco) your QoS is based on DSCP markings once it is classified, not on VLANs.

If your PC is connected to the data VLAN and a broadcast storm occurs, it's likely that it will experience issues such as high CPU usage that will render the CIPC unusable regardless of whether the RTP is getting through to the PC.

These are all side issues though, the main issues are around the supportability of a large number of Windows PCs running in two VLANs simultaneously.

Best of luck.

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
1651
Views
5
Helpful
27
Replies
CreatePlease login to create content