07-08-2020 05:49 AM
See config below. When configuring a 2nd port on a vg204, it is perpetually unregistered. When I turn on debug sccp events and errors, I see the following in the logs:
Jul 8 08:48:07 EDT: sccp_spi_ha_is_not_ready_to_handle_new_msg: sccp_spi_ha_is_not_ready_to_handle_new_msg
Any help is appreciated.
version 15.7
no service pad
service timestamps debug datetime localtime show-timezone
service timestamps log datetime localtime show-timezone
no service password-encryption
!
hostname hostname-VG204-12
!
boot-start-marker
boot-end-marker
!
!
logging buffered 1000000
no logging console
enable secret 5 <secret>
!
aaa new-model
!
aaa authentication banner ^C
Banner message ^C
aaa authentication login default group tacacs+ local
aaa authorization exec default group tacacs+ local if-authenticated
aaa authorization commands 15 default group tacacs+ local if-authenticated
aaa accounting exec default start-stop group tacacs+
aaa accounting commands 15 default start-stop group tacacs+
!
aaa session-id common
clock timezone EST -5 0
clock summer-time EDT recurring
!
ip domain name domain.com
ip name-server <snip>
ip name-server 1<snip>1
ip cef
no ipv6 cef
!
stcapp ccm-group 1
stcapp
!
stcapp feature access-code
!
stcapp feature speed-dial
!
stcapp supplementary-services
port 0/0
fallback-dn 1234567890
!
voice service voip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback cisco
!
voice-card 0
!
interface FastEthernet0/0
ip address dhcp
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
ip http client source-interface FastEthernet0/0
ip tacacs source-interface FastEthernet0/0
ip ssh source-interface FastEthernet0/0
ip ssh version 2
ip ssh server algorithm encryption aes128-ctr aes192-ctr aes256-ctr
ip ssh client algorithm encryption aes128-ctr aes192-ctr aes256-ctr
!
logging host <snip>
ipv6 ioam timestamp
!
voice-port 0/0
timeouts initial 60
timeouts interdigit 60
timeouts ringing infinity
!
voice-port 0/1
timeouts initial 60
timeouts interdigit 60
timeouts ringing infinity
!
voice-port 0/2
!
voice-port 0/3
!
mgcp
mgcp call-agent <ip> service-type mgcp version 0.1
mgcp behavior rsip-range tgcp-only
mgcp behavior comedia-role none
mgcp behavior comedia-check-media-src disable
mgcp behavior comedia-sdp-force disable
!
mgcp profile default
!
sccp local FastEthernet0/0
sccp ccm <ip> identifier 1 priority 1 version 7.0
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
!
ccm-manager redundant-host <ip>
ccm-manager config server <ip>
ccm-manager sccp local FastEthernet0/0
!
dial-peer voice 999000 pots
service stcapp
port 0/0
07-08-2020 12:51 PM
A coworker replaced the gateway, copied the config, and its registered. Anybody have experience w/ lots of faulty vg204s? (That's what its looking like in our deployment.)
07-08-2020 10:31 PM
By the look of your configuration it doesn’t have a complete configuration for the second port as there is no dial peer for it. You need to have a dial peer that reference the port.
dial-peer voice 999001 pots
service stcapp
port 0/1
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