topic Re: where is callforward all and secondary css for fwdall in the database? in Management

where is callforward all and secondary css for fwdall in the database?

stephan.steiner — Fri, 20 Apr 2018 13:44:42 GMT

I need to bulk load cfwd settings.. unfortunately, the list operation for DNs does not support these tags, so I have to look it up using SQL. I thought I had it, but turns out I was looking at the CSS of the DN proper, not the FWD ALL CSS. The DN is in the NumPlan table, which has a bunch of fkcallingsearchspace_ entries that I can map to the other cfwd settings (busy, busy internal, no answer, no answer int, etc) but for the life of me I can't seem to find the one for forward all. Even if I extract the entire record for the DN I'm looking at, I'm unable to find the pkid of the CSS I've associated as Forward All css.

I also checked the devicenumplanmap table just in case, but it's not there either.

What am I missing here?

Re: where is callforward all and secondary css for fwdall in the database?

Jonathan Els — Fri, 20 Apr 2018 13:55:09 GMT

I did a skim-read, but I think this covers it:

Unified Communications Guerrilla: CUCM SQL Queries: Listing Call Forward All Settings

Re: where is callforward all and secondary css for fwdall in the database?

Jonathan Els — Fri, 20 Apr 2018 13:56:18 GMT

Looks like you need a join on callforwarddynamic for this...

Re: where is callforward all and secondary css for fwdall in the database?

stephan.steiner — Fri, 20 Apr 2018 14:21:07 GMT

Thanks.. I know it would be in some other table, just couldn't point my finger on it.

Re: where is callforward all and secondary css for fwdall in the database?

Jonathan Els — Fri, 20 Apr 2018 14:23:18 GMT

It's not obvious at all Why the split from the rest? Strange...

Re: where is callforward all and secondary css for fwdall in the database?

dstaudt — Fri, 20 Apr 2018 16:49:50 GMT

Great blog series link

Just a bit of background re the *dynamic tables:

- These tables generally support features that drive high-volume transactions, usually user driven features

- The data is de-normalized from the other tables for performance/indexing reasons

- These tables are bi-directionally replicated (most CUCM tables are replicated only from Pub->Sub), so that during times when the Sub may lose connection to the Pub, feature changes made by users (such as CFWD) are persisted on the Sub, and then replicated up to the Pub on eventual reconnection

Re: where is callforward all and secondary css for fwdall in the database?

Jonathan Els — Fri, 20 Apr 2018 17:20:34 GMT

Aha! Makes perfect sense. I should have thought of this. Thank you for weighing in here.