We have a mixed SCCP and SIP phone environment running on CME 10.5 - recently upgrade to support the SIP only 7841 IP phones.  The SCCP environment is well established and all functionality works as expected. The problem comes with the new SIP phones when they receive a call and it requires transferred to another DN (SIP or SCCP) - the first part of the transfer works but the release does not as part of full-consult.   Quick Summary of the Problem: Incoming Call to 001 > Transfer Softkey > Dial 002 to transfer > Transfer Sofkey (to release - this doesn't work!)    The problem is the call doesn't release to the new DN and the incoming call just hangs on hold on both IP phones. The softkey is visible but no matter how many times the key is pressed it's unresponsive. Maybe I am missing a command on the voice register global configuration. Has anyone seem this problem? Can you help? Assistance appreciated.   voice register global  mode  cme  source-address X.X.X.X port 5060  max-dn 20  max-pool 20  load 7841 sip78xx.10-3-1-12  authenticate register  authenticate realm omniaccess.com  timezone 23  time-format 24  date-format D/M/Y  tftp-path flash:  file text  create profile sync 2089505729701103  ntp-server X.X.X.X mode directedbroadcast ... View more

Fellow Support Community, Any assistance or suggestions you can provide on a issue I have with a GRE tunnel and IPSec. I have a vessel offshore which has a GRE tunnel working between shore and vessel - this works fine and data passes between vessel and corporate LAN ok. The problem comes when I apply the IPSec and ISAKMP parameters to each of the VTIs. tunnel mode ipsec ipv4 tunnel protection ipsec profile VPN_IPSEC_PROFILE These commands and the associated pararameters are tried and tested and working fine for 5 other VPNs which are currently up and passing traffic. The working configuration for each endpoint is below. When the above commands are applied the VPN stays QM_IDLE but no data traffic passes over the tunnel. The VPN provides the connectivty back to corporate LAN so the site is effectively cut off Any suggestions?? ****HUB**** crypto keyring HELIX_VPN_KEYRING pre-shared-key address B.B.B.B key xyz ! crypto isakmp policy 10 encr aes 256 authentication pre-share group 2 crypto isakmp invalid-spi-recovery crypto isakmp profile VPN_ISAKMP_PROFILE    keyring HELIX_VPN_KEYRING    match identity address B.B.B.B 255.255.255.255 ! crypto ipsec transform-set VPN_TS esp-aes 256 esp-sha-hmac crypto ipsec nat-transparency spi-matching ! crypto ipsec profile VPN_IPSEC_PROFILE description ***  VPN IPsec Profile - RH - November 2012 *** set transform-set VPN_TS set pfs group2 set isakmp-profile VPN_ISAKMP_PROFILE ! interface Tunnel128 description *** Vessel VPN Tunnel (JC1RT 01:B.B.B.B) *** ip address 10.0.75.130 255.255.255.252 ip mtu 1400 ip tcp adjust-mss 1360 tunnel source GigabitEthernet0/0.311 tunnel destination B.B.B.B ! interface GigabitEthernet0/0.311 description *** ISP Public Subnet *** encapsulation dot1Q 311 ip address A.A.A.A 255.255.255.248 ! ip route 10.2.88.0 255.255.255.0 10.0.75.129 name JC1_Data_Tu128 ip route 10.2.89.0 255.255.255.0 10.0.75.129 name JC1_Voice_Tu128 ****REMOTE**** crypto keyring VPN_KEYRING vrf Internet   pre-shared-key address A.A.A.A key xyz ! crypto isakmp policy 10 encr aes 256 authentication pre-share group 2 crypto isakmp invalid-spi-recovery crypto isakmp profile VPN_ISAKMP_PROFILE    vrf Internet    keyring VPN_KEYRING    match identity address A.A.A.A 255.255.255.255 Internet ! crypto ipsec transform-set VPN_TS esp-aes 256 esp-sha-hmac crypto ipsec nat-transparency spi-matching ! crypto ipsec profile VPN_IPSEC_PROFILE description *** VPN IPsec Profile - RH - 30/01/13 *** set transform-set VPN_TS set pfs group2 set isakmp-profile VPN_ISAKMP_PROFILE ! interface Tunnel128 description *** Jaya Crystal VPN Tunnel (VPNRTR01:A.A.A.A) *** ip address 10.0.75.129 255.255.255.252 ip mtu 1400 ip tcp adjust-mss 1360 tunnel source FastEthernet0/0.602 tunnel destination A.A.A.A tunnel vrf Internet ! interface FastEthernet0/0.602 description *** Vessel Provided Public IP Demark *** encapsulation dot1Q 602 ip vrf forwarding Internet ip address B.B.B.B 255.255.255.248 ip nat outside ip virtual-reassembly in ! ip route 0.0.0.0 0.0.0.0 10.0.75.130 name Tu128 ... View more

Support Community, We have ASA5510s protecting the company voice networks that are only currently managed via the CLI. I've gone ahead and uploaded the relevant ASDM image to the device, unfortunately I can't log on to the ASDM as we use two-factor authentication. The information I've found so far advises that ASDM is not accessible when using two-factor authentication due to the way Java works, however the items I've been reading are 3/4 years old. Does anyone know if this is possible with the more recent versions of code? Or if there are any workarounds? Images we are using... asa821-k8.bin asdm-635.bin Any assistance anyone can provide is appreciated. Thanks, Ric ... View more

Hello Community, I hope someone might be able to help with an issue I'm seeing on an IOS VPN Tunnel interface which keeps going down and then back up... We have a Cisco 2811 acting as a VPN Hub router on the backbone, which connects to various client sites over VPN. Of the 7 VPNs configured so 6 work well and are generally trouble free. The VPN interface on the other VPN keeps going down ,multiple times throughout the day, just recently the client has been noticing loss of connectivity. The remote router is managed over the VPN so there is always some kind of traffic over it. Does anyone know or be able to help find the answer as to why this is happening. Please see router log below... *Sep  7 06:40:53.631: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to down *Sep  7 06:41:23.991: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to up *Sep  7 15:21:12.541: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to down *Sep  7 15:21:43.013: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to up *Sep  7 23:58:46.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to down *Sep  7 23:59:16.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to up *Sep  8 08:37:07.705: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to down *Sep  8 08:37:38.117: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to up *Sep  8 12:30:37.200: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to down *Sep  8 12:34:05.248: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel111, changed state to up Issue has caused outages a number of times today. See config snippets below, with equivalent on the backbone router... crypto isakmp policy 10 encr aes 256 authentication pre-share group 2 crypto isakmp key 6 [sharedkey] address X.X.X.X no-xauth crypto isakmp invalid-spi-recovery crypto isakmp ccm ! ! crypto ipsec transform-set OPNET_VPN_TS esp-aes 256 esp-sha-hmac ! crypto ipsec profile OPNET_VPN_IPSEC_PROFILE description *** OPNET VPN IPsec Profile - RH - July 2011 *** set transform-set OPNET_VPN_TS set pfs group2 interface Tunnel111 description *** Client OPNET VPN Tunnel (OPNET-VPNHUB-RT1:X.X.X.X) *** bandwidth 2048 ip address 172.32.111.2 255.255.255.252 ip mtu 1400 ip nat outside ip virtual-reassembly ip tcp adjust-mss 1360 tunnel source FastEthernet0/0 tunnel destination X.X.X.X tunnel mode ipsec ipv4 tunnel protection ipsec profile OPNET_VPN_IPSEC_PROFILE I hope someone out there will be able to help. All response appreciated. Regards, Ric ... View more