CME SIP 503 service unavailable phones not registering
I have an ISR4431 as a CME.
It has been working for a lot of time, but this morning all phones are not registering. The CME is binding IPs to the phones, and the phones are getting the *.cnf file from the CME, but when the phone is traying to register, the CME returns "Status: 503 Service Unavailable".
I put here some parts of the configuration.
CME_I#sh run | sec voice register global voice register global mode cme source-address 172.29.2.249 port 5060 max-dn 200 max-pool 200 load 7811 sip78xx.14-0-1-0001-135 authenticate register timezone 20 tftp-path flash: create profile sync 0008544515015595 auto-register !
CME_I#sh run | sec voice service voip voice service voip ip address trusted list ipv4 172.29.20.249 allow-connections sip to sip fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none trace sip bind control source-interface Loopback0 bind media source-interface Loopback0 registrar server early-offer forced
CME_I#sh run | sec telephony-service telephony-service protocol mode ipv4 sdspfarm units 10 sdspfarm tag 1 conference conference hardware max-ephones 100 max-dn 100 ip source-address 172.29.2.249 port 2000 service profile phonePassword Sc2nea21 service phone pcPort 1 load 6921 sip78xx.14-0-1-0001-135 max-conferences 5 gain -6 transfer-system full-consult create cnf-files version-stamp 7960 Jul 02 2021 08:07:12 CME_I#
CME_I#sh voice register tftp-bind tftp-server url flash:/its/syncinfo.xml alias syncinfo.xml tftp-server url flash:/its/SIPDefault.cnf alias SIPDefault.cnf tftp-server url flash:/its/softkeyDefault_kpml.xml alias softkeyDefault_kpml.xml tftp-server url flash:/its/softkeyDefault.xml alias softkeyDefault.xml tftp-server url flash:/its/skPublicConf_kpml.xml alias skPublicConf_kpml.xml tftp-server url flash:/its/skPublicConf.xml alias skPublicConf.xml tftp-server url flash:/its/skPersonalConf_kpml.xml alias skPersonalConf_kpml.xml tftp-server url flash:/its/skPersonalConf.xml alias skPersonalConf.xml tftp-server url flash:/its/featurePolicyDefault.xml alias featurePolicyDefault.xml tftp-server url flash:/its/SEP701F5387A9A3.cnf.xml alias SEP701F5387A9A3.cnf.xml tftp-server url flash:/its/SEP701F5387ABE5.cnf.xml alias SEP701F5387ABE5.cnf.xml tftp-server url flash:/its/SEP701F5387A9E3.cnf.xml alias SEP701F5387A9E3.cnf.xml tftp-server url flash:/its/SEP701F5387ABF7.cnf.xml alias SEP701F5387ABF7.cnf.xml tftp-server url flash:/its/SEP701F5387AB2C.cnf.xml alias SEP701F5387AB2C.cnf.xml tftp-server url flash:/its/SEP701F5387A9AB.cnf.xml alias SEP701F5387A9AB.cnf.xml tftp-server url flash:/its/SEP701F5387AB35.cnf.xml alias SEP701F5387AB35.cnf.xml tftp-server url flash:/its/SEP701F5387A9A2.cnf.xml alias SEP701F5387A9A2.cnf.xml tftp-server url flash:/its/SEP00279024A695.cnf.xml alias SEP00279024A695.cnf.xml tftp-server url flash:/its/SEP00279024A63A.cnf.xml alias SEP00279024A63A.cnf.xml tftp-server url flash:/its/SEP701F5387A96A.cnf.xml alias SEP701F5387A96A.cnf.xml tftp-server url flash:/its/SEP00279024A6C0.cnf.xml alias SEP00279024A6C0.cnf.xml tftp-server url flash:/its/SEP00279024A69B.cnf.xml alias SEP00279024A69B.cnf.xml tftp-server url flash:/its/SEP00279024A733.cnf.xml alias SEP00279024A733.cnf.xml tftp-server url flash:/its/SEP00279024A6D6.cnf.xml alias SEP00279024A6D6.cnf.xml tftp-server url flash:/its/SEP00279024A6DE.cnf.xml alias SEP00279024A6DE.cnf.xml tftp-server url flash:/its/SEP00279024A72C.cnf.xml alias SEP00279024A72C.cnf.xml tftp-server url flash:/its/SEP00279024A5C5.cnf.xml alias SEP00279024A5C5.cnf.xml tftp-server url flash:/its/SEP00279024A597.cnf.xml alias SEP00279024A597.cnf.xml tftp-server url flash:/its/SEP00279024A61F.cnf.xml alias SEP00279024A61F.cnf.xml tftp-server url flash:/its/SEP00279024A724.cnf.xml alias SEP00279024A724.cnf.xml tftp-server url flash:/its/SEP00279024A68C.cnf.xml alias SEP00279024A68C.cnf.xml
Greetings, Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perf...
Parsec's Cisco UCCE/PCCE CC Connector application for CRM works as a bridge between the CRM and Cisco UCCE/PCCE CC solution.The CRM can be any cloud based CRM like Salesforce (SFDC), ServiceNow ,MS Dynamics or a 3rd party CRM.The CRM user/Agent will have ...
It’s a feature which allows CUCM to determine whether the phone is in its home location or a roaming station.By enabling this feature users can roam from one site to another site and acquire the site-specific settings such as Codecs, MRGL, Call rout...
Cisco just Announced their new Collaboration Toolbox resources portal. You can check it out here https://collabtoolbox.cisco.com/ It has a bunch of tools a partner can find helpful. But if your interested in learning which...