09-03-2003 09:02 AM - edited 03-13-2019 01:27 AM
With CCM 3.3(2)SPC we had several users using IP
Phones (7960/40) at there home offices connected via
Cisco VPN devices quite successfully using SCCP.
However, now that we have upgraded to CCM3.3(3)SR1
the functionality of these VPN based IP Phones has
diminished. The same configurations are present on
our PIXs and VPN concentrator.
--Successes--
VPN IP Phone can call an external number with two
way audio.
VPN IP Phone can host a meetme conference using a
public DN and both external and internal callers can
participate.
VPN IP Phone can receive a call and forward it based
on forwarding rules (like CFAll, CFNA to voicemail,
etc).
--Failure--
VPN IP Phone will ring when an internal or external
call is received (Caller ID is fine), but the VPN
recipient is unable to retrieve - answer the call.
Attempts to pick up the handset, press headset or
the speaker button do not answer the call; though
the headset and speaker button do light up. If a
answer attempt is made - any call forwarding rules
like no answer to voicemail do not work.
Are the 3.3(3)SR1 Phone loads solid? Are there now
additional concerns for VPN based SCCP phones in this
release?
---Thanks---
09-03-2003 01:58 PM
You may want to make sure that softphone is up to the right rev:
Cisco IP SoftPhone - Upgrading the TAPI/TSP on the Client
Perform the following procedure to upgrade the Cisco SoftPhone TAPI/TSP to the version stated above
Procedure
Step 1 From each Cisco Soft phone Client, browse into server running Cisco CallManager Administration and log in with administrative privileges.
TIP: To browse into the server, enter http://
Step 2 From the Application menu, choose Install Plug-ins.
Step 3 Click the Cisco Telephony Service Provider icon associated with the plug-in.
Step 4 Follow the prompts in the window to complete the upgrade.
Step 5 Verify that a basic call works as expected for Cisco SoftPhone.
09-03-2003 02:29 PM
Guess I am a bit confused as I did not know that
having an actual 7960/40 for home offive users
via VPN connection required a TAPI/TSP client
piece.
Are you sure that this is a necessary item?
--- ----- ---
09-03-2003 04:14 PM
No, TAPI is not needed. I think crieman thought you were using softphone.
09-03-2003 04:42 PM
Ran into a very similiar issue....upgrade your PIX to 6.3.3 .....
Solved my issue (had 2 separate sites where this cleared the issue)...
09-03-2003 08:02 PM
I found that 6.3(3) is a solution to the VPN IP
phone user issue when the VPN is terminating at
our PIX.
I am testing 4.0.1.C on the VPN 3005 concentrator
and hope to have success with that software load,
but I have to wait until the morning for actual
user testing for those terminating their VPN
on that device.
Who would have thought that a CCM upgrade would
have such dependancies?!? (grin)
--- Thanks ---
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide