11-15-2008 01:59 PM - edited 03-15-2019 02:34 PM
DPA 7630 to 6.1(2) reports registration rejected error db config. I have auto registration enabled on subscriber that DA is pointed to.
Worked fine in 4.1(3)
54491 04:15:47 194 W CSSP 11: CallManager connection has gone down
54492 04:15:47 134 W CSSP 14: CallManager connection has gone down
54493 04:15:47 111 W CSSP 12: CallManager connection has gone down
54494 04:15:48 216 W CSSP 5: CallManager connection has gone down
54495 04:15:48 150 W Octel/CM 11: CallManager register reject: Error: DB Config
54496 04:15:49 855 W Octel/CM 14: CallManager register reject: Error: DB Config
54497 04:15:49 190 W Octel/CM 12: CallManager register reject: Error: DB Config
54498 04:15:49 190 W CSSP 25: CallManager connection has gone down
54499 04:15:49 11 W CSSP 1: CallManager connection has gone down
54500 04:15:49 14 W Octel/CM 5: CallManager register reject: Error: DB Config
54501 04:15:49 467 W Octel/CM 1: CallManager register reject: Error: DB Config
54502 04:15:50 210 W CSSP 6: CallManager connection has gone down
11-15-2008 05:01 PM
Which model of Phones in CUCM you have?
DPA version?
11-15-2008 05:35 PM
Just a thought, but have you configure DNS on the CUCM 6.1.2? Previously on CUCM 4.1.3 you may have been using local hosts files to resolve the DPA hostname?
The reason I ask is that the host name is the device name sent to the CallManager with the port number appended to it when the DPA registers its ports with CallManager.
Hope this helps
Allan.
11-17-2008 07:21 AM
I opened a TAC case. The auto-registration was resolved by changing from 1.3(1)ES6.1 to dpa-main.1.3(1)ES9.tar.
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