[cisco-voip] Cisco IP Communicator Issue

Thu Feb 4 17:07:19 EST 2010

While I can't speak to the TAC answer-and I apologize that I did not see this-BUT

I suspect the answer is that the MTP command was missing..
See Below----

ephone  16
 device-security-mode none
 video
 mac-address 0000.0000.0006
 ephone-template 16
 codec g729r8 dspfarm-assist
 mtp
 button  1:16

Thanks,
Jim

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Thursday, February 04, 2010 9:47 AM
To: Kim, Hyoun S
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Cisco IP Communicator Issue

For the benefit of the list (and archive) what was the configuration setting that caused this issue?

-Ryan

On Feb 4, 2010, at 9:29 AM, Kim, Hyoun S wrote:

I ended up contacting TAC about the issue and they nailed it down to a configuration setting on the CIPC ephone on my router.  Who knew it was as simple as that?

Thanks for the input guys.

Hyoun Kim
Network Administrator I
Charter Media - East Division
640 Broadmor Blvd, Suite 80
Murfreesboro, TN 37129

Email: Hyoun.Kim at chartercom.com<mailto:Hyoun.Kim at chartercom.com>
Office: 615.217.6245
Fax: 615.217.6255

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kim, Hyoun S
Sent: Thursday, January 28, 2010 10:23 AM
To: Bill Talley; Cristobal Priego
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Cisco IP Communicator Issue

That gives me a good place to start.  Since you guys think it's a routing issue, do you think it's because my IP phones are on an isolated network?  You can't even ping the IP range that the phones use unless you're on the CME router itself.

Hyoun Kim
Network Administrator I
Charter Media - East Division
640 Broadmor Blvd, Suite 80
Murfreesboro, TN 37129

Email: Hyoun.Kim at chartercom.com<mailto:Hyoun.Kim at chartercom.com>
Office: 615.217.6245
Fax: 615.217.6255

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bill Talley
Sent: Wednesday, January 27, 2010 6:48 PM
To: Cristobal Priego
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Cisco IP Communicator Issue

I agree with those suggesting routing issues.  Sounds like the default gateway for your internal IP phones may be sending the the return rtp traffic back a different route.

Sent from my iPhone

On Jan 27, 2010, at 6:29 PM, Cristobal Priego <cristobalpriego at gmail.com<mailto:cristobalpriego at gmail.com>> wrote:
most of the times one way audio issues are related to routing problems than an issue with the CME, CCM or the phone.
and its more common to have a one way audio issue when a vpn tunnel is involved. could you please check your routing table.
what i'd check is the routing table or whatever you have on the vpn. it looks like the traffic coming from your office to your ipc is getting lost somewhere that's why they can hear you but you can't hear them
2010/1/27 Steve G <smgustafson at gmail.com<mailto:smgustafson at gmail.com>>
make sure that your VPN knows about the phone subnet so that rtp knows how to get to the office phone.
On Wed, Jan 27, 2010 at 3:07 PM, Kim, Hyoun S <Hyoun.Kim at chartercom.com<mailto:Hyoun.Kim at chartercom.com>> wrote:
We have a Cisco CME/CUE setup in our office and I'm trying to work on a solution for those people who are on the road, but still need access to their local office phone.

I installed the Cisco IP Communicator and used the corporate VPN to allow connections back to our office.  On the CME, I created a new ephone and associated with the same ephone-dn that the user's physical phone resides on.

I tested the following scenarios using the IP Communicator:

1.       Placed a call from an external phone (like a cell phone) to the DN.  The phone rang & the  call was connected normally.

2.       Placed a call to an external phone from the IP Communicator.  The call was connected normally.

3.       Placed a call to another number internal to the CME.  Incoming audio (recipient could be heard), but outgoing audio (me speaking) did not work.

Is there a reason why I have problems with bullet #3?  The only thing I could think of is the fact that the actual physical Cisco phones are on their own private network, separate from the corporate network.  But even then, I could make/receive calls from outside phones.

<image001.jpg>
________________________________
Hyoun Kim * Network Administrator I - East Division
640 Broadmor Blvd * Suite 80 * Murfreesboro, TN 37129
' 615.217.6245 * ' 859.312.6941 * 7 615.217.6255 * * Hyoun.Kim at chartercom.com<mailto:Hyoun.Kim at chartercom.com>

E-MAIL CONFIDENTIALITY NOTICE:

The contents of this e-mail message and

any attachments are intended solely for the

addressee(s) and may contain confidential

and/or legally privileged information. If you

are not the intended recipient of this message

or if this message has been addressed to you

in error, please immediately alert the sender

 by reply e-mail and then delete this message

and any attachments. If you are not the

intended recipient, you are notified that

any use, dissemination, distribution, copying,

or storage of this message or any attachment

is strictly prohibited.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

E-MAIL CONFIDENTIALITY NOTICE:

The contents of this e-mail message and

any attachments are intended solely for the

addressee(s) and may contain confidential

and/or legally privileged information. If you

are not the intended recipient of this message

or if this message has been addressed to you

in error, please immediately alert the sender

 by reply e-mail and then delete this message

and any attachments. If you are not the

intended recipient, you are notified that

any use, dissemination, distribution, copying,

or storage of this message or any attachment

is strictly prohibited.

E-MAIL CONFIDENTIALITY NOTICE:

The contents of this e-mail message and

any attachments are intended solely for the

addressee(s) and may contain confidential

and/or legally privileged information. If you

are not the intended recipient of this message

or if this message has been addressed to you

in error, please immediately alert the sender

 by reply e-mail and then delete this message

and any attachments. If you are not the

intended recipient, you are notified that

any use, dissemination, distribution, copying,

or storage of this message or any attachment

is strictly prohibited.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100204/1565aaa3/attachment.html>