Cisco Unified Communications Manager 11.0(1) Database Dictionary

This document describes the data stored in the primary CUCM database for the Cisco Unified Communications Manager 11.0(1) release.

It is automatically generated from the development data dictionary used to create the SQL scripts that install the CCM database.


Table of Contents

    1.0 Table List
    2.0 Table Details
    3.0 Common Table Relationships
    4.0 Schema Changes


Modification History

Rev. Date Originator Comment
1 May 7, 2015 Charlie Munro Cisco UCM 11.0(1) database schema

1.0 Tables

aardialprefixmatrix (182) aarneighborhood (181) alarmconfig (145) alarmmonitorcapabilities (161)
alarmusertext (369) alternatenumber (2582) analogaccess (2) analogaccessport (3)
applicationdialrule (252) applicationuser (230) applicationusercapfmap (353) applicationusercapfmapdynamic (442)
applicationuserdevicemap (297) applicationuserdirgroupmap (238) applicationusernumplanmap (355) appserver (372)
appserverapplicationusermap (407) appserverinfo (373) availdialplan (405) axlchangenotifyclient (540)
axlchangenotifysubscribe (541) batfileinfo (344) batfileinfojobmap (347) batinputdata (345)
batinputdatajobmap (348) batjob (341) batjobresults (346) billingserver (386)
blfdirectedcallpark (426) blfspeeddial (350) blockingcsslookup (582) callerfilterlist (450)
callerfilterlistmember (451) callforwardalloverride (457) callforwarddynamic (434) callforwardhistorydynamic (595)
callingsearchspace (73) callingsearchspacemember (74) callmanager (5) callmanagergroup (6)
callmanagergroupmember (7) callpark (2843) carrierselectcodedetails (1085) carrierselectprofile (1084)
carrierselectprofiletrunkmap (1086) ccaprofile (2583) ccdadvertisingserviceprofile (506) ccdhosteddn (502)
ccdhosteddngroup (501) ccdrequestingserviceprofile (507) cdrmconfig (385) certificate (660)
certificatehashmap (672) certificateprocessnodemap (670) certificateservicecertificatemap (980) certificatetrustrolemap (661)
cmcinfo (304) codeclist (1104) codeclistmember (1105) commondeviceconfig (421)
commonphoneconfig (384) commonphoneconfigxml (550) componentversion (368) confidentialaccesslevel (2113)
confidentialaccesslevelmatrix (2114) corsdomain (2623) credential (446) credentialdynamic (458)
credentialhistory (448) credentialpolicy (447) credentialpolicydefault (459) crsapplication (248)
crsuserclusterspecific (410) cubacountryregionalinfo (1053) cubaproductsupport (597) customannouncement (617)
customannouncementlocale (618) customuserattributedata (545) customuserattributename (544) datetimesetting (10)
defaults (11) defaultucuserprofile (2611) destinationcodecontrol (971) device (1)
deviceaddonmodulemap (167) deviceautoreg (2608) devicecerdynamic (1066) devicefeaturemember (209)
devicehlogdynamic (437) devicemanagementdynamic (2593) devicemanagementinfo (973) devicemobilitydynamic (436)
devicemobilitygroup (423) devicemobilityinfo (427) devicenumplanmap (77) devicenumplanmapendusermap (438)
devicenumplanmapremdestmap (454) devicepool (13) devicepooldevicemobilityinfomap (422) devicepoolroutegroupmap (2131)
deviceprivacydynamic (435) deviceprovidermap (975) devicerelatedversionstamp (626) devicereset (253)
devicesipdevicemap (2156) devicetftpdynamic (465) devicexml16k (937) devicexml4k (934)
devicexml8k (936) dhcpserver (292) dhcpsubnet (293) dialplan (107)
dialplandetails (573) dialplantag (97) dialrules (330) dialrulespatternmap (329)
digitalaccessbri (223) digitalaccesspri (14) digitalaccesst1 (15) digitalaccesst1port (16)
digitdiscardinstruction (105) digitdiscardinstructionmember (100) directorypluginattribute (259) directorypluginconfig (249)
directorypluginconfigdirgroupmap (2143) directorypluginhost (260) directorypluginpoollist (2613) directorypluginroutingdatabase (2132)
directorypluginschedule (261) dirgroup (231) dmmsdevice (416) dnaliassynckeymap (2155)
dnddynamic (440) dntracelogging (972) dpcallrecordserver (688) dpcertificate (1031)
dpdevice (679) dpdeviceaccess (682) dpdevicecallrecordservermap (689) dpdevicegroupmap (681)
dpdevicejobcomponent (683) dpdeviceproductcomponent (680) dpdevicetraceservermap (690) dpemail (685)
dpemaillist (1032) dpemaillistmap (1033) dpftpserver (695) dpgroup (678)
dpjob (684) dpjobemaillistmap (686) dpmailserver (694) dpntpserver (1034)
dptemplate (692) dptemplatecomponentdata (693) dptemplatemetacomponentlist (691) dptraceserver (687)
drfcomponent (288) drfscript (289) e911messages (1081) elingroup (2863)
elingroupmember (2864) elinmappingdynamic (2865) emccdynamic (520) emergencylocidnumber (700)
emergencylocidnumberdynamic (701) emremotedynamic (521) enduser (228) enduserappservermap (376)
endusercapfmap (354) endusercapfmapdynamic (443) enduserdevicemap (229) enduserdirgroupmap (232)
enduserlicense (418) endusermlppauthentication (1067) endusernotification (1058) endusernumplanmap (240)
enterprisenode (2587) enterprisephoneconfigxml (551) enterprisesubcluster (2586) extensionmobilitydynamic (444)
externalcallcontrolprofile (651) facinfo (305) fallbackprofile (642) featureconfig (529)
featurecontrolpolicy (564) featuregrouptemplate (1107) functionrole (233) functionroledirgroupmap (234)
functionroleresourcemap (237) gatekeeper (138) gatewaylayout (178) gatewaynetworkdetail (590)
geolocation (552) geolocationfilter (555) geolocationpolicy (556) geolocationpolicymatrix (557)
globalsetting (589) grtreport (484) grtreportsourcemap (485) grtsource (483)
h323device (18) h323trunkdestination (572) hostedroutepattern (2148) hosteduri (1087)
hosteduricatalog (1079) hosteduricatalogkey (2612) httpinterfaceaddress (2158) httpprofile (2164)
httpprofileuriextension (2165) httpproxyexception (2600) huntpilotqueue (543) imsintegratedmobile (547)
inactiveusers (2845) incomingtransformationprofile (645) infrastructuredevice (2872) installmonitor (212)
interclusterserviceprofile (523) intercomdynamic (490) ipmalineinfo (244) ipmamanagerassistant (242)
ipmastaticdata (243) ipmauser (193) ivruserlocale (455) lbmgroup (534)
lbmhubgroup (548) ldapauthentication (251) ldapauthenticationhost (262) ldapfilter (283)
ldapserverattribute (267) ldapsystemconfig (274) licensedistributionused (362) licenseinfo (394)
licenseserver (359) licensingresourceusage (1074) linegroup (203) linegroupnumplanmap (202)
localestringformatrulemap (2153) location (111) locationmatrix (533) matrix (318)
matrixmember (320) mediamixer (22) mediaresourcegroup (151) mediaresourcegroupmember (152)
mediaresourcelist (153) mediaresourcelistmember (154) mgcp (102) mgcpdevicemember (103)
mgcpslotconfig (143) mlaparameter (221) mlppdomain (277) mobilesmartclientprofile (493)
mobilityprofile (586) modelfeaturemap (84) mohaudiosource (149) mohserver (148)
mohservermulticastinfo (150) mrgmediaaccesspermission (583) networkaccessprofile (2599) nsfinformationelement (192)
nsfprotocolservicemap (191) ntpserver (315) ntpserverdatetimesettingmap (316) numplan (24)
numplanappservermap (389) numplandcpsyn (428) numplandynamic (334) numplansubpatternusagemap (1076)
numplanuri (539) outboundappservercn (390) pagetemplate (653) pagetemplatedetail (654)
patternparametermap (322) personaladdressbook (245) personalphonebook (246) phonebutton (25)
phonetemplate (29) physicallocation (420) pickupgroup (331) pickupgroupendusermap (1077)
pickupgrouplinemap (332) pickupgroupmember (333) pickupgroupprocessnodemapdynamic (610) plugin (122)
pnpselectedlanguage (2606) preferences (286) processconfig (88) processconfigdefaults (101)
processnode (86) processnodeaudit (498) processnoderoleservicemap (1142) processnodesec (398)
processnodesecack (399) processnodeservice (113) productcapabilities (119) productsupportsfeature (180)
provider (974) recordingdynamic (432) recordingprofile (433) region (31)
regionmatrix (32) registrationdynamic (1080) remotecatalogkey (2604) remotecluster (524)
remoteclusterilshostinfo (1106) remoteclusterilsstatus (1078) remoteclusterservicemapdynamic (525) remoteclusteruricatalog (1088)
remotecommoninfo (2137) remotedestination (452) remotedestinationdynamic (481) remotedestinationhistorydynamic (596)
remotedestinationusagemodelmap (2616) remotenumplan (2139) remoteobjectblockrule (2150) remoteobjectpartitionrule (2145)
remoteroutingpattern (2592) remotesyslog (624) remotesyslogappservermap (625) remoteuri (2138)
replicationdynamic (482) resourceprioritydefaultnamespace (472) resourceprioritynamespace (469) resourceprioritynamespacelist (470)
resourceprioritynamespacemap (471) routefilter (106) routefiltercosroutingmap (593) routefiltermember (71)
routegroup (33) routegroupdevicemap (108) routelist (34) routepartition (75)
rtmtprofile (413) rtmtreportingdynamic (511) safccdpurgeblocklearnedroutes (519) safclientcmnodemap (508)
safclientsettings (504) safsecurityprofile (500) safservices (505) safservicetrunkmap (509)
schapplication (977) schscript (978) schscriptexecution (979) schuserclusterinfo (976)
scratch (116) sdpattribute (2110) sdpattributeallowedvalues (2111) sdpattributelist (2109)
secureconfig (474) securityprofile (314) sipdevice (206) sipnormalizationscript (535)
sipnormalizationscriptchunk (536) sipprofile (317) siprealm (393) siptrunkdestination (571)
site (578) siteroutepartitionmember (580) softkeyset (184) softkeytemplate (183)
softkeytemplatedefault (424) softkeytemplateservicemap (278) speeddial (35) spokenname (403)
srst (194) supportsfeatureattributemap (210) tapssecurenumplan (358) tapsuserlocale (357)
telecaster (91) telecasterservice (134) telecasterserviceparameter (135) telecastersubscribedparameter (136)
telecastersubscribedservice (133) testnotify (371) timeperiod (306) timeschedule (307)
timescheduletimeperiodmap (308) todaccess (475) todaccesssetting (476) treecontrolgroupnodes (227)
troubleshootingtrace (370) typeadminboolean (302) typeadminerror (287) typeadminfieldinfo (301)
typeadminfieldinfomap (300) typealarmseverity (160) typeannouncementfile (616) typeannouncements (256)
typeapplication (214) typeapplicationdialrule (391) typeappserver (374) typeappservercontent (375)
typeasn1roseoidencoding (496) typeassignmentmode (2594) typeauthenticationmode (270) typeautoanswer (174)
typebandwidth (37) typebarge (464) typebatfile (400) typebatfilesubclause (401)
typebatfrequency (339) typebatfunction (338) typebatfunctionfieldinfomap (352) typebatjobstatus (343)
typebatresultstatus (351) typebattarget (340) typebatusage (342) typebillingserverprotocol (382)
typebitpos (239) typeblfsdoption (473) typeboolean (38) typebriprotocol (222)
typecalheaders (2585) typecallerfiltermask (449) typecallerid (131) typecallinglineidentification (1100)
typecallingpartyselection (43) typecallstate (185) typecalltreatmentonfailure (622) typecalmode (2115)
typecarrierselectcode (1083) typecertificate (313) typecertificatedistribution (2621) typecertificateoperation (272)
typecertificateservice (981) typecertificatestatus (273) typecertificateverificationlevel (1089) typecfacssactivationpolicy (463)
typechangenotifysubscribe (1027) typeclass (8) typeclockreference (41) typecodec (1103)
typeconfiginputdata (461) typeconfiginputdatagrouping (479) typeconnectedpbx (196) typeconnection (1048)
typeconnectiondevice (1050) typeconnectionusage (1055) typeconnectprotocol (1090) typecosrouting (577)
typecosroutingclassification (1054) typecountry (42) typecredential (445) typecredentialuser (460)
typecsuparam (44) typecubadevice (1049) typecubaproductdisplaygroup (1056) typecubasupportedcountry (592)
typecucmversioninsipheader (2117) typecustomuserattribute (546) typedayofmonth (532) typedayofweek (309)
typedberrors (257) typedevicefeature (208) typedeviceprofile (146) typedeviceprotocol (46)
typedevicesecuritymode (213) typedevicetrustmode (1041) typedialparameter (325) typedialpattern (323)
typedialviaoffice (587) typedigitsending (109) typedistributealgorithm (201) typedndoption (439)
typednusage (241) typedpdeviceprotocol (674) typedpjobfeature (1030) typedpjobstatus (677)
typedpproduct (673) typedptracelevel (675) typedpverificationstatus (676) typedpwebprotocol (697)
typedrfregistered (291) typedrfscript (290) typedscpsetting (2157) typedscpvalue (2885)
typedtmfsignaling (324) typee911locationstate (1109) typee911message (1082) typeeckeysize (2883)
typeencode (47) typeendpointconnection (2869) typeeosuppvoicecall (2622) typefallbackcssselection (641)
typefallbacksensitivitylevel (649) typefdlchannel (126) typefeature (39) typefeatureconfig (528)
typefeaturecontrol (563) typefieldinfo (266) typeforward (48) typeframing (125)
typegatewayusage (1046) typegclear (561) typegeolocationdevice (553) typegkoption (49)
typeglobalnumber (2118) typeglobalsetting (588) typegroupversionstamp (414) typehaserverstate (2634)
typehash (671) typehostedroutepatternpstnrule (2149) typehotspotauthenticationmethod (2617) typehttpprofile (2163)
typehttpprofileuri (2584) typehttpproxy (2601) typehuntalgorithm (226) typeidsauditlevel (497)
typeilssyncstatus (1119) typeinterclusterservice (522) typeipaddressingmode (491) typeipaddressingmodeprefcontrol (492)
typeipmalinemode (387) typeipmatarget (388) typekeepalivetimeinterval (2133) typekeyauthority (404)
typekeyorder (2882) typekeysize (271) typelampblinkrate (132) typelanguage (171)
typelanguagegroup (255) typeldapdirectoryfunction (2134) typeldapprotocol (276) typeldapserver (263)
typeldapserverattr (264) typelicensedresource (1072) typelicensedresourceproductmap (1073) typelicensefeature (360)
typelicenseunit (361) typelicensingmode (599) typelicensingstate (1071) typelogicalpartitionpolicy (554)
typelossynetwork (429) typematrix (319) typematrixvalue (349) typemedia (1102)
typemediapayload (224) typemgcpslotmodule (140) typemgcpvic (141) typemixer (51)
typemobilesmartclient (494) typemodel (79) typemohcodec (156) typemonitor (159)
typemonthofyear (310) typemwlpolicy (175) typenamedisplayformat (598) typenetworklocation (54)
typenodeusage (441) typensfservice (190) typenullrestriction (336) typenumberingplan (121)
typenumplanuritype (2116) typeoperator (55) typeoutboundcallrollover (456) typepacketcapturemode (269)
typeparam (89) typepartitionusage (430) typepattern (326) typepatternhandlingflaginfo (2605)
typepatternprecedence (198) typepatternrouteclass (606) typepatternusage (93) typepersonalphonenumber (247)
typephonecategory (1110) typephonefeature (1064) typephonefeaturecubaproductmap (1065) typephonepersonalization (462)
typephoneservice (487) typephoneservicecategory (489) typephoneservicedisplay (488) typephonetemplateusage (168)
typepickupnotification (419) typepipesize (591) typeplaceholdertag (1120) typeplaceholdertagfieldinfomap (1121)
typepluginusage (123) typeportaluri (2614) typepreemption (199) typepreferredmediasource (2108)
typepresentationbit (56) typeprichanie (57) typepriofnumber (95) typepriprotocol (58)
typeprocessnoderole (1141) typeproduct (117) typeproductconfig (118) typeprotocolside (59)
typeprovider (1047) typeqsig (211) typeqsigvariant (495) typerecordingflag (431)
typerelatedfieldinfo (335) typereleasecausevalue (197) typeremotedestinationusage (2615) typeremoteobject (2144)
typereplicationstatus (1143) typereset (254) typeresethandshake (406) typeresource (235)
typeresourceaction (236) typerevertpriority (425) typeringsetting (186) typerisclass (173)
typerisstatus (282) typeroutingdatabasecachetimer (2135) typersvpoversip (486) typertmtreportingservice (510)
typerule (395) typeruleinfo (396) typesafservice (503) typeschciscotacdestination (531)
typescheduleunit (296) typesdpattributehandling (2112) typesecuritypolicy (327) typeserversecuritymode (643)
typeservice (90) typeservicecategory (187) typeservicegrouping (280) typeservicerestriction (281)
typesilencesuppressionthreshold (60) typesipassertedtype (467) typesipbandwidthmodifier (1045) typesipcodec (205)
typesipidentityblend (1062) typesipprivacy (466) typesiprel1xxoptions (530) typesipreroute (480)
typesipscripterrorhandling (537) typesipsessionrefreshmethod (2105) typesiptrunkcalllegsecurity (1042) typesite (576)
typesoftkey (188) typespa8800port (1052) typesrstoption (195) typessomode (2619)
typestartdialprotocol (114) typestatus (61) typestringformat (2151) typestringformatrule (2152)
typesubclass (392) typesubpatternusage (1075) typesupportsfeature (179) typesyslogmessage (623)
typesystemfeature (96) typetableinfo (265) typetaskstatus (518) typetelnetlevel (397)
typeterminal (139) typetimeofday (311) typetimeschedulecategory (477) typetimezone (62)
typetracelevelgrouping (295) typetracelevelgroups (294) typetransport (204) typetrunk (63)
typetrunkdirection (64) typetrunklevel (65) typetrunkpad (66) typetrunkselectionorder (67)
typetrunkservice (526) typetrustrole (659) typetunneledprotocol (312) typeucproduct (1092)
typeucproductappservermap (1093) typeucproductconnectprotocolmap (1094) typeucservice (1091) typeuridisambiguationpolicy (1061)
typeusageprofilefeature (579) typeuseentity (585) typeuseragentserverheaderinfo (1051) typeuserassociation (328)
typeuserlocale (169) typeusernotificationmessage (1057) typeusernotificationsection (1059) typeuserprofile (356)
typeusntype (2106) typev150sdpfilter (1044) typevideocalltrafficclass (549) typeviprfilterelement (638)
typevmavoidancepolicy (1028) typevpnclientauthentication (662) typewebpage (1114) typewebpagedisplay (1115)
typewebpageinfo (299) typewebpagesection (1116) typewifiauthenticationmethod (2602) typewififrequency (2603)
typewifiusercertificate (2890) typewincharset (172) typewlanprofilechanges (2609) typeyellowalarm (127)
typezerosuppression (124) typezzconfbridge (377) typezzdndcontrol (412) typezzdtmfdblevel (379)
typezznetworkmediatype (381) typezzntpmode (411) typezzpreff (402) typezzuserinfo (378)
ucservice (1095) ucserviceprofile (1097) ucserviceprofiledetail (1098) ucserviceprofiledetailxml (1099)
ucservicexml (1096) ucuserprofile (2607) ucuserprofiledevicemap (1111) ucuserprofilenumplanmap (2146)
usageprofile (574) usageprofileendusermember (584) usageprofileproductspecific (575) usageprofiletelecasterservicemap (581)
usergroup (2846) usergroupmember (2847) usn (1063) usnreplset (1069)
usnsyncservice (2154) usntombstoneuri (1068) vipre164transformation (646) viprexcludeddidpatterngroup (644)
viprfilterelement (633) viprfiltergroup (632) viproffpathserver (647) viprpublisheddidpattern (635)
viprpublisheddidpatterngroup (634) viprserver (630) viprservice (631) viprserviceccmexternalipmap (648)
viprservicedidpatterngroupmap (637) vipruri (639) viprurivalidateddidmap (640) viprvalidateddid (636)
vohserver (2107) voicemessagingpilot (176) voicemessagingprofile (177) vpngateway (663)
vpngatewaycertificatemap (664) vpngroup (665) vpngroupvpngatewaymap (666) vpnprofile (667)
webpagesection (1117) wifihotspotprofile (2618) wirelesslanprofile (2597) wirelesslanprofilegroup (2596)
wirelesslanprofilegroupmember (2598) wsmdevice (415) wwwcookie (72) xmldisplayinstancerulemap (163)

2.0 Table Details

2.1 Table Relationships

pkid is the primary key ID. It is always of type GUID (a 36 character UUID).

Fields that begin with the letters "fk" represent foriegn keys into another table. The name of the field following the "fk" prefix up to but not including an underscore character is the name of the related table. The field in related table is always pkid. and is a GUID.

Fields that begin with the letters "ik" represent internal keys into the same table.

Fields that begin with a "tk" represent an enumerated type. This field is related to a table whose name begins with "Type" and ends with the name of the field following the prefix up to but not including an underscore character. The field in the related table is always "enum" and is an integer.

Some tables do not allow insert or delete. These tables are populated by installation programs and migrated.

Some tables do not allow any modifications at all and are populated by installation only.

Some fields do not allow modification. These fields are populated by triggers in response to changes in other records, or they are set when the record is inserted.

2.2 Field Types

DN
This field is a directory number. This is currently defined as a variable length string of max length 23.
enum
This field is related to another table. The table name begins with "Type" and is followed by the field name without the "tk" prefix.
GUID
This is a globally unique ID. It is represented as a string of length 36 (string representation of UUID).
long
This is an integer stored as signed 4 byte value (+/-2^31-1). Refer to the Check Constraint for limitations on possible values.
string
This is a variable length string. The maximum length will be specified in bytes. The database stores string data using UTF-8 encoding. Refer to the Validation for limitations on characters and length of strings.

2.3 Table Level Rules and Field Details

Unless otherwise indicated, all tables and data are replicated throughout the cluster.

Note for developers

The Data Dictionary source is the same set of CSV files used to create the database. Each table, field, rule, and constraint has an ID next to it (in parentheses) that indicates the source. The codes are always <type>-number. The type codes are as follows:

TI
Table Information from TypeTableInfo.csv
FI
Field Information from TypeFieldInfo.csv
RFI
Related Field Information from TypeRelatedFieldInfo.csv
MFI
Mulit-Field Index from TypeMultiFieldIndex.csv
RI
Rule Information from TypeRuleInfo.csv

For example, RFI-21 is Related Field Info for enum = 21 in TypeRelatedFieldInfo.csv.

Error messages from business rule violations have two components - Error code and SQL Exception. For example, Error: java.sql.SQLException: 37131, SQL State: IX000, Error Code: -746. Error Code -746 indicates an exception based on database rules. If specific error message text is not displayed, it can be found in TypeDbErrors table where SQLException value is the value in the enum column. SQLException values above 25,000 also correlate directly to data dictionary entries at follows:

Legend for Tables

Elements defining a table
Field Name (with links to referenced tables)
Elements defining a field
Elements defining a rule
Multi-column uniqueness (combination of columns is unique)
2.3.1 aardialprefixmatrix (TI-182)
Description:Defines the assigned digits to prepend to dialed digits to specified from and to AAR neighborhoods.
Fields:
2.3.1.1 dialprefix (FI-1117)
Type:string [24]
Default Value:EMPTY
Validation:^[0-9A-D*#+]{0,24}$
Remarks:The prefix digits to use for automated alternate routing within this AAR group.
2.3.1.2 fkaarneighborhood_from (FI-1115)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:Specifies the AAR Neighborhood from which a call is being made. Inserted by trigger.
2.3.1.3 fkaarneighborhood_to (FI-1116)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:Specifies the AAR Neighborhood to which a call is being made. Inserted by trigger.
2.3.1.4 pkid (FI-1114)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:fkaarneighborhood_from + fkaarneighborhood_to is unique. (MFI-55)
Rules:
Rule (RI-1):
Type:Active (Insert)
This table is modified by this rule.
Rule Name:Insert AAR Matrix
Description:On insert of a new AARNeighborhood the matrix must be filled out with records from the new AARNeighborhood to itself and to every existing AARNeighborhood
Test Condition:Insert into AARNeighborhood

 
2.3.2 aarneighborhood (TI-181)
Description:Automated alternate routing (AAR) provides a mechanism to reroute calls through the PSTN or other network by using an alternate number when Cisco CallManager blocks a call due to insufficient location bandwidth.
Fields:
2.3.2.1 name (FI-1113)
Type:string [20] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,20}$
Remarks:Logical name of the AAR group
Rule (RI-1):
Type:Active (Insert)
Rule Name:Insert AAR Matrix
Description:On insert of a new AARNeighborhood the matrix must be filled out with records from the new AARNeighborhood to itself and to every existing AARNeighborhood
Test Condition:Insert into AARNeighborhood
2.3.2.2 pkid (FI-1112)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-1):
Type:Active (Insert)
Rule Name:Insert AAR Matrix
Description:On insert of a new AARNeighborhood the matrix must be filled out with records from the new AARNeighborhood to itself and to every existing AARNeighborhood
Test Condition:Insert into AARNeighborhood
Uniqueness:No multicolumn uniqueness constraints
Rules:
Rule (RI-1):
Type:Active (Insert)
Rule applied when record is inserted.
Rule Name:Insert AAR Matrix
Description:On insert of a new AARNeighborhood the matrix must be filled out with records from the new AARNeighborhood to itself and to every existing AARNeighborhood
Test Condition:Insert into AARNeighborhood

 
2.3.3 alarmconfig (TI-145)
Description:Records alarm settings per node (server) per service per monitor. These records are inserted at install time.
Insert/Delete is not allowed.
Fields:
2.3.3.1 enablealternativelog (FI-5192)
Type:bool
Default Value:FALSE
Remarks:Enable Alternative Logging for the Alarm Settings from Syslog Server.
2.3.3.2 fkprocessnodeservice (FI-810)
Type:guid (Cascade Delete)
Remarks:Specifies the node/service combination for this alarm configuration.
2.3.3.3 monitorstatus (FI-887)
Type:bool
Default Value:FALSE
Remarks:True if this monitor is on.
2.3.3.4 pkid (FI-809)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.3.5 server (FI-886)
Type:string [1280]
Default Value:EMPTY
Remarks:Application managed container for remote syslog destination server information. No DB format support, validation, or special migration.
2.3.3.6 tkalarmseverity (FI-822)
Type:enum
Remarks:The alarm severity.
2.3.3.7 tkmonitor (FI-812)
Type:enum
Remarks:The type of monitor (event log, sys log, etc.) being configured.
Uniqueness:fkprocessnodeservice + tkmonitor is unique. (MFI-28)

 
2.3.4 alarmmonitorcapabilities (TI-161)
Description:Used to determine which monitors are allowed with each service. These records are inserted at install time.
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.4.1 enum (FI-896)
Type:enum (Unique, Indexed, Not Modifiable)
Remarks:A number to identify the record
2.3.4.2 tkmonitor (FI-897)
Type:enum
2.3.4.3 tkservice (FI-898)
Type:enum
Uniqueness:No multicolumn uniqueness constraints

 
2.3.5 alarmusertext (TI-369)
Description:User defined text for alarms
Fields:
2.3.5.1 alarmname (FI-2722)
Type:string [255] (Indexed)
2.3.5.2 catalogname (FI-2721)
Type:string [500]
2.3.5.3 pkid (FI-2720)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.5.4 userdefinedtext (FI-2723)
Type:string [500]
Uniqueness:No multicolumn uniqueness constraints

 
2.3.6 alternatenumber (TI-2582)
Description:Stores the Enterprise and E164 numbers linked to a directory number (from Numplan table).
Fields:
2.3.6.1 dnderived (FI-25567)
Type:string [50] (Indexed, Not Modifiable)
Default Value:EMPTY
Remarks:Derived value of directory number
Rule (RI-2101):
Type:Active (Insert/Update)
Rule Name:Calculate the value of DNDerived.
Description:Use the DNOrMask and parent NumPlan.dnorpattern to calculate the DNDerived. If DNOrMask is NULL, use parent NumPlan.dnorpattern as-is. If DNOrMask contains wildcard, apply it to NumPlan.dnorpattern to generate the DNDerived.
Rule (RI-2101):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Calculate the value of DNDerived.
Description:Use the DNOrMask and parent NumPlan.dnorpattern to calculate the DNDerived. If DNOrMask is NULL, use parent NumPlan.dnorpattern as-is. If DNOrMask contains wildcard, apply it to NumPlan.dnorpattern to generate the DNDerived.
Rule (RI-2103):
Type:Validation (Insert/Update)
Rule Name:AlternateNumber DNOrMask uniqueness
Description:Alternate number must be unique within the Partition
Test Condition:The value of URI must be unique within the Partition.
Rule (RI-2105):
Type:Active (Update)
Rule Name:USN from Alternate Number modification
Description:If the Alternate Number changes, create a USN for new value and create a tombstone for the old value
Test Condition:UPDATE USN to reflect new value and INSERT USN tombstone for the old value
Rule (RI-2113):
Type:Validation (Insert/Update)
Rule Name:Validate consistency of columns for Alternate Number
Description:Cannot change number type of an Alternate Number. Only one AlternateNumber designated as AAR per DN. Only one instance of each number type per DN. May not publish a number twice as the same type. For AAR Alternate Number, get all the advertised URIs attached to my DN, and for each of them, if there is an advertised URI with the same value attached to a different DN, throw an exception.
Test Condition:On INSERT/UPDATE on AlternateNumber validate values of columns
Error Message:Various
2.3.6.2 dnormask (FI-25565)
Type:string [50] (Indexed, Null OK)
Remarks:SIP alternate number, may be a mask.
Rule (RI-2101):
Type:Active (Insert/Update)
Rule Name:Calculate the value of DNDerived.
Description:Use the DNOrMask and parent NumPlan.dnorpattern to calculate the DNDerived. If DNOrMask is NULL, use parent NumPlan.dnorpattern as-is. If DNOrMask contains wildcard, apply it to NumPlan.dnorpattern to generate the DNDerived.
2.3.6.3 doroutebyroutestring (FI-25568)
Type:bool
Default Value:FALSE
Remarks:Indicates whether other clusters may route to this URI or number using route string.
Rule (RI-2104):
Type:Active (Insert)
Rule Name:USN from Alternate Number creation
Description:Create USN for new value of Alternate Number
Test Condition:INSERT into USN
Rule (RI-2105):
Type:Active (Update)
Rule Name:USN from Alternate Number modification
Description:If the Alternate Number changes, create a USN for new value and create a tombstone for the old value
Test Condition:UPDATE USN to reflect new value and INSERT USN tombstone for the old value
Rule (RI-2106):
Type:Active (Delete)
Rule Name:USN from Alternate Number deletion
Description:Create a USN tombstone for the old Alternate Number
Test Condition:INSERT USN tombstone for the old value
Rule (RI-2113):
Type:Validation (Insert/Update)
Rule Name:Validate consistency of columns for Alternate Number
Description:Cannot change number type of an Alternate Number. Only one AlternateNumber designated as AAR per DN. Only one instance of each number type per DN. May not publish a number twice as the same type. For AAR Alternate Number, get all the advertised URIs attached to my DN, and for each of them, if there is an advertised URI with the same value attached to a different DN, throw an exception.
Test Condition:On INSERT/UPDATE on AlternateNumber validate values of columns
Error Message:Various
2.3.6.4 doroutelocal (FI-25569)
Type:bool
Default Value:FALSE
Remarks:Indicates whether the alternate number may be used for routing on the cluster on which it is defined.
Rule (RI-2103):
Type:Validation (Insert/Update)
Rule Name:AlternateNumber DNOrMask uniqueness
Description:Alternate number must be unique within the Partition
Test Condition:The value of URI must be unique within the Partition.
2.3.6.5 fknumplan (FI-25563)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:The directory number to which the alternate number belongs.
Rule (RI-2101):
Type:Active (Insert/Update)
Rule Name:Calculate the value of DNDerived.
Description:Use the DNOrMask and parent NumPlan.dnorpattern to calculate the DNDerived. If DNOrMask is NULL, use parent NumPlan.dnorpattern as-is. If DNOrMask contains wildcard, apply it to NumPlan.dnorpattern to generate the DNDerived.
Rule (RI-2102):
Type:Active (Insert)
Rule Name:Validate DN association of AlternateNumber.
Description:Alternate number can only be associated to directory number or line template.
Rule (RI-2103):
Type:Validation (Insert/Update)
Rule Name:AlternateNumber DNOrMask uniqueness
Description:Alternate number must be unique within the Partition
Test Condition:The value of URI must be unique within the Partition.
Rule (RI-2104):
Type:Active (Insert)
Rule Name:USN from Alternate Number creation
Description:Create USN for new value of Alternate Number
Test Condition:INSERT into USN
Rule (RI-2105):
Type:Active (Update)
Rule Name:USN from Alternate Number modification
Description:If the Alternate Number changes, create a USN for new value and create a tombstone for the old value
Test Condition:UPDATE USN to reflect new value and INSERT USN tombstone for the old value
Rule (RI-2106):
Type:Active (Delete)
Rule Name:USN from Alternate Number deletion
Description:Create a USN tombstone for the old Alternate Number
Test Condition:INSERT USN tombstone for the old value
Rule (RI-2113):
Type:Validation (Insert/Update)
Rule Name:Validate consistency of columns for Alternate Number
Description:Cannot change number type of an Alternate Number. Only one AlternateNumber designated as AAR per DN. Only one instance of each number type per DN. May not publish a number twice as the same type. For AAR Alternate Number, get all the advertised URIs attached to my DN, and for each of them, if there is an advertised URI with the same value attached to a different DN, throw an exception.
Test Condition:On INSERT/UPDATE on AlternateNumber validate values of columns
Error Message:Various
2.3.6.6 fkroutepartition (FI-25564)
Type:guid (Null OK)
Default Value:NULL
Remarks:The partition to which the URI belongs.
Rule (RI-2103):
Type:Validation (Insert/Update)
Rule Name:AlternateNumber DNOrMask uniqueness
Description:Alternate number must be unique within the Partition
Test Condition:The value of URI must be unique within the Partition.
2.3.6.7 isaar (FI-25570)
Type:bool
Default Value:FALSE
Remarks:Indicates whether this number is valid for dialing on the PSTN.
Rule (RI-2104):
Type:Active (Insert)
Rule Name:USN from Alternate Number creation
Description:Create USN for new value of Alternate Number
Test Condition:INSERT into USN
Rule (RI-2105):
Type:Active (Update)
Rule Name:USN from Alternate Number modification
Description:If the Alternate Number changes, create a USN for new value and create a tombstone for the old value
Test Condition:UPDATE USN to reflect new value and INSERT USN tombstone for the old value
Rule (RI-2106):
Type:Active (Delete)
Rule Name:USN from Alternate Number deletion
Description:Create a USN tombstone for the old Alternate Number
Test Condition:INSERT USN tombstone for the old value
Rule (RI-2113):
Type:Validation (Insert/Update)
Rule Name:Validate consistency of columns for Alternate Number
Description:Cannot change number type of an Alternate Number. Only one AlternateNumber designated as AAR per DN. Only one instance of each number type per DN. May not publish a number twice as the same type. For AAR Alternate Number, get all the advertised URIs attached to my DN, and for each of them, if there is an advertised URI with the same value attached to a different DN, throw an exception.
Test Condition:On INSERT/UPDATE on AlternateNumber validate values of columns
Error Message:Various
2.3.6.8 istemplate (FI-25571)
Type:bool (Indexed, Not Modifiable)
Default Value:FALSE
Remarks:Distinguish the Universal Line Template with the real alternate number.
Rule (RI-2102):
Type:Active (Insert)
Rule Name:Validate DN association of AlternateNumber.
Description:Alternate number can only be associated to directory number or line template.
Rule (RI-2102):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Validate DN association of AlternateNumber.
Description:Alternate number can only be associated to directory number or line template.
Rule (RI-2103):
Type:Validation (Insert/Update)
Rule Name:AlternateNumber DNOrMask uniqueness
Description:Alternate number must be unique within the Partition
Test Condition:The value of URI must be unique within the Partition.
Rule (RI-2113):
Type:Validation (Insert/Update)
Rule Name:Validate consistency of columns for Alternate Number
Description:Cannot change number type of an Alternate Number. Only one AlternateNumber designated as AAR per DN. Only one instance of each number type per DN. May not publish a number twice as the same type. For AAR Alternate Number, get all the advertised URIs attached to my DN, and for each of them, if there is an advertised URI with the same value attached to a different DN, throw an exception.
Test Condition:On INSERT/UPDATE on AlternateNumber validate values of columns
Error Message:Various
2.3.6.9 isurgent (FI-25572)
Type:bool (Indexed)
Default Value:FALSE
Remarks:Indicates whether the alternate number is urgent.
2.3.6.10 pkid (FI-25562)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-2103):
Type:Validation (Insert/Update)
Rule Name:AlternateNumber DNOrMask uniqueness
Description:Alternate number must be unique within the Partition
Test Condition:The value of URI must be unique within the Partition.
Rule (RI-2105):
Type:Active (Update)
Rule Name:USN from Alternate Number modification
Description:If the Alternate Number changes, create a USN for new value and create a tombstone for the old value
Test Condition:UPDATE USN to reflect new value and INSERT USN tombstone for the old value
Rule (RI-2106):
Type:Active (Delete)
Rule Name:USN from Alternate Number deletion
Description:Create a USN tombstone for the old Alternate Number
Test Condition:INSERT USN tombstone for the old value
Rule (RI-2113):
Type:Validation (Insert/Update)
Rule Name:Validate consistency of columns for Alternate Number
Description:Cannot change number type of an Alternate Number. Only one AlternateNumber designated as AAR per DN. Only one instance of each number type per DN. May not publish a number twice as the same type. For AAR Alternate Number, get all the advertised URIs attached to my DN, and for each of them, if there is an advertised URI with the same value attached to a different DN, throw an exception.
Test Condition:On INSERT/UPDATE on AlternateNumber validate values of columns
Error Message:Various
2.3.6.11 tkglobalnumber (FI-25566)
Type:enum (Not Modifiable)
Default Value:100
Remarks:Functional classification, applies only to TEL URI.
Rule (RI-2113):
Type:Validation (Insert/Update)
Rule Name:Validate consistency of columns for Alternate Number
Description:Cannot change number type of an Alternate Number. Only one AlternateNumber designated as AAR per DN. Only one instance of each number type per DN. May not publish a number twice as the same type. For AAR Alternate Number, get all the advertised URIs attached to my DN, and for each of them, if there is an advertised URI with the same value attached to a different DN, throw an exception.
Test Condition:On INSERT/UPDATE on AlternateNumber validate values of columns
Error Message:Various
Uniqueness:No multicolumn uniqueness constraints

 
2.3.7 analogaccess (TI-2)
Description:This subclasses the device table for analog access information not in the Device table.
Fields:
2.3.7.1 fkdevice (FI-14)
Type:guid (Unique, Indexed, Cascade Delete)
Migration Source:convert from DeviceName
Remarks:Points to the device record being "subclassed." Device.tkModel must be analog access.
Rule (RI-13):
Type:Validation (Insert/Update)
Rule Name:AnalogAccess device
Description:The records in AnalogAccess table must reference a device using AnalogAccess device protocol
Test Condition:AnalogAccess.fkDevice IN (SELECT pkid FROM Device where tkDeviceProtocol = 3)
Error Message:AnalogAccess table may only reference devices with matching Device Protocol (AnalogAccess).
Remedy:Correct the fkDevice value to refer to an Analog Access device.
2.3.7.2 pkid (FI-13)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.7.3 tktrunkselectionorder (FI-15)
Type:enum
Migration Source:TrunkSelectionOrder
Remarks:IE. Bottom up or top down.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.8 analogaccessport (TI-3)
Description:Analog access ports associtated with an analog access Device.
Fields:
2.3.8.1 attendantdn (FI-22)
Type:dn
DN Type:DN_TYPE_ALL_DIGITS
Default Value:EMPTY
Validation:^[0-9*#+]{0,50}$
Migration Source:AttendantNumber
Remarks:For Ground Start and Loop Start ports, enter the number to which you want incoming calls routed; for example, zero or a directory number for an attendant.
Rule (RFI-4):
Type:Inter-field Condition and Constraint
Test Condition:tkTrunk = 1 OR tkTrunk = 2
DN Type:DN_TYPE_ALL_DIGITS
Constraint:
Validation:[0-9*#]{0,24}
Null Allowed:null
Remarks:Attendant DN has Invalid format. It should contain no more than 24 numbers, * and #. Regular expression used for validation is [0-9*#]{0,24}
2.3.8.2 calleriddn (FI-37)
Type:dn (Null OK)
DN Type:DN_TYPE_MASK
Default Value:NULL
Validation:^[0-9*#+X]{0,32}$
Migration Source:CallerId
Remarks:If specified, use this for the CallerID.
2.3.8.3 e164dn (FI-5280)
Type:string [16]
Default Value:EMPTY
Validation:^(\+)([0-9]{1,15})$
Remarks:E164 Directory Number
2.3.8.4 expecteddigits (FI-26)
Type:long
Check Constraint:(ExpectedDigits >= 0) AND (ExpectedDigits <= 32)
Migration Source:ExpectedDigits
Remarks:Enter the number of digits that are expected on the inbound side of the trunk. For this rarely used field, leave zero as the default value if you are unsure.
2.3.8.5 fkdevice (FI-18)
Type:guid (Indexed, Cascade Delete)
Migration Source:convert from DeviceName
Remarks:device::tModel must be analog access
Rule (RI-14):
Type:Validation (Insert/Update)
Rule Name:AnalogAccessPort device
Description:The records in AnalogAccessPort table must reference a device using AnalogAccess device protocol
Test Condition:AnalogAccessPort.fkDevice IN (SELECT pkid FROM Device where tkDeviceProtocol = 3)
Error Message:AnalogAccessPort table may only reference devices with matching Device Protocol (AnalogAccess).
Remedy:Correct the fkDevice value to refer to an Analog Access device.
2.3.8.6 inboundcalleridenable (FI-36)
Type:bool
Migration Source:InboundCallerIdEnable
Remarks:If true, CallerID is enabled.
2.3.8.7 numdigits (FI-24)
Type:long
Check Constraint:(NumDigits >= 0) AND (NumDigits <= 32)
Migration Source:NumDIgits
Remarks:Enter the number of significant digits to collect. Cisco CallManager counts significant digits from the right (last digit) of the number called. Use this field for the processing of incoming calls and to indicate the number of digits starting from the last digit of the called number that is used to route calls coming into the PRI span. See Prefix DN.
2.3.8.8 pkid (FI-17)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.8.9 portnum (FI-19)
Type:long
Migration Source:PortNum
Remarks:1-8 For Vega; 1 for MGCP_STATION; 1 for MGCP_TRUNK and tkDeviceProtocol=AnalogAccess
2.3.8.10 prefixdn (FI-23)
Type:dn (Null OK)
DN Type:DN_TYPE_ALL_DIGITS
Default Value:NULL
Validation:^[0-9*#+]{0,50}$
Migration Source:Prefix
Remarks:The prefix digits that are appended to the digits that this trunk receives on incoming calls. The Cisco CallManager adds prefix digits after it truncates the number in accordance with the Num Digits setting.
2.3.8.11 sigdigits (FI-25)
Type:bool
Migration Source:SigDigits
Remarks:Obsolete - NumDigits is always used. Flag to allow only certain amount of digits.
2.3.8.12 smdiportnumber (FI-932)
Type:long
Default Value:0
Check Constraint:(SMDIPortNumber >= 0) AND (SMDIPortNumber <= 4096)
Remarks:Use this field for analog access ports that connect to a voice-mail system. Set the SMDI Port Number equal to the actual port number on the voice-mail system to which the analog access port connects.
2.3.8.13 timer1 (FI-30)
Type:long
Check Constraint:Timer1 >= 0
Migration Source:Timer1
Remarks:In Milliseconds
2.3.8.14 timer2 (FI-31)
Type:long
Check Constraint:Timer2 >= 0
Migration Source:Timer2
Remarks:In Milliseconds
2.3.8.15 timer3 (FI-32)
Type:long
Check Constraint:Timer3 >= 0
Migration Source:Timer3
Remarks:In Milliseconds
2.3.8.16 timer4 (FI-33)
Type:long
Check Constraint:Timer4 >= 0
Migration Source:Timer4
Remarks:In Milliseconds
2.3.8.17 timer5 (FI-34)
Type:long
Check Constraint:Timer5 >= 0
Migration Source:Timer5
Remarks:In Milliseconds
2.3.8.18 timer6 (FI-35)
Type:long
Check Constraint:Timer6 >= 0
Migration Source:Timer6
Remarks:In Milliseconds
2.3.8.19 tkcallingpartyselection (FI-39)
Type:enum
Migration Source:CallingPartySelection
Remarks:Source of the calling party number: originator = 1, first redirect = 2, last redirect = 3
2.3.8.20 tkdigitsending (FI-623)
Type:enum
Default Value:0
Remarks:DTFM, MF, etc.
2.3.8.21 tkpresentationbit (FI-40)
Type:enum
Migration Source:PresentationBit
Remarks:CLID presentationBit: allowed = 1, restricted = 2
2.3.8.22 tksilencesuppressionthreshold (FI-38)
Type:enum
Migration Source:SilenceSuppressionThreshold
Remarks:in dbm0
2.3.8.23 tkstartdialprotocol (FI-624)
Type:enum
Default Value:0
Remarks:Immediate, Wink Start, etc.
2.3.8.24 tktrunk (FI-20)
Type:enum
Migration Source:PortType
Remarks:The type of trunk. (Ground Start, Loop Start, DID, POTS, E&M)
2.3.8.25 tktrunkdirection (FI-21)
Type:enum
Migration Source:Direction
Remarks:Inbound, outbound and both are valid Directions. Outbound equates to DOD. Both only allowed on Ground Start (GS)
2.3.8.26 tktrunklevel (FI-306)
Type:enum
Migration Source:was "ApplicationType"
2.3.8.27 tktrunkpad_rx (FI-28)
Type:enum
Migration Source:RxPad
2.3.8.28 tktrunkpad_tx (FI-29)
Type:enum
Migration Source:TxPad
2.3.8.29 unattendedport (FI-2387)
Type:bool (Null OK)
Default Value:FALSE
2.3.8.30 xml (FI-935)
Type:string [24000] (Null OK)
Default Value:NULL
Remarks:Product specific configuration XML not used by CCM
Rule (RI-196):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:AnalogAccessPort.xml validation
Description:Product specific information for each AnalogAccess gateway port needs to be validated before storing in xml column. Validation is now performed using client side script at Admin pages. This involves reading the display instance xml (from scratch table) for the specific product, then for each parameter , read the corresponding rule xml record (scratch table) and validate the parameter value as defined in the rule.
Test Condition:On Insert/Update of AnalogAccess port (FXS gateway port)
Uniqueness:fkdevice + portnum is unique. (MFI-1)

 
2.3.9 applicationdialrule (TI-252)
Description:Holds Dial Rule Info.
Fields:
2.3.9.1 description (FI-1771)
Type:string [200]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%\\&<>]{0,50}$
2.3.9.2 digitsremoved (FI-1774)
Type:long
Default Value:0
Check Constraint:(Digitsremoved >=0) AND (Digitsremoved <=100)
2.3.9.3 name (FI-1770)
Type:string [50] (Unique)
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{1,50}$
2.3.9.4 numbeginwith (FI-1772)
Type:string [50]
Default Value:EMPTY
Validation:^[0-9*#+]{0,50}$
2.3.9.5 numofdigits (FI-1773)
Type:long
Default Value:0
Check Constraint:(numofdigits >=0) AND (numofdigits <=100)
2.3.9.6 pkid (FI-1769)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.9.7 prefix (FI-1775)
Type:string [50]
Default Value:EMPTY
Validation:^[0-9*#+]{0,50}$
2.3.9.8 priority (FI-1776)
Type:long
Default Value:0
2.3.9.9 tkapplicationdialrule (FI-2885)
Type:enum
Remarks:The type of Dial Rule. (Basic, Directory)
Uniqueness:priority + tkapplicationdialrule is unique. (MFI-89)
Constraints:
Rule (RFI-142):
Type:Inter-field Condition and Constraint
Constraint:(Digitsremoved >0) OR (Prefix <> '')
Remarks:Either Prefix pattern must be defined, or Digits to be removed must be > 0

 
2.3.10 applicationuser (TI-230)
Description:Special Application users of CCM system. These users will not show up in a list of users shown to a customer
Fields:
2.3.10.1 aclallowreplace (FI-2590)
Type:bool
Default Value:FALSE
Remarks:Whether SIP header replacement allowed
2.3.10.2 acloobsubscription (FI-2485)
Type:bool
Default Value:FALSE
Remarks:Obsolete
2.3.10.3 acloodrefer (FI-2486)
Type:bool
Default Value:FALSE
2.3.10.4 aclpresencesubscription (FI-2487)
Type:bool
Default Value:FALSE
2.3.10.5 aclunsolicitednotification (FI-2488)
Type:bool
Default Value:FALSE
2.3.10.6 fkmatrix_presence (FI-2508)
Type:guid
Default Value:ad243d17-98b4-4118-8feb-5ff2e1b781ac
Remarks:Pkid for Presence Group Matrix record. This is required for extension mobility. Appuser table does not need this because appuser cannot do extension mobility.
2.3.10.7 isstandard (FI-2047)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:Created during installation.
2.3.10.8 name (FI-1659)
Type:string [50] (Unique, Indexed)
Remarks:Records inserted by install.
Rule (RI-57):
Type:Validation (Insert/Update)
Rule Name:AppUser Name Uniqueness
Description:An AppUser Name cannot be the same as an EndUser UserID
Test Condition:IF (AppUser.Name IN (SELECT userid FROM EndUser)) THEN throw exception
Error Message:AppUser Name already exists as an EndUser. AppUser Name cannot be the same as an EndUser's userid.
Remedy:Provide a unique name for the Application User that is not the same as an EndUser userid.
2.3.10.9 passwordreverse (FI-2388)
Type:string [128] (Null OK)
Default Value:69c4f936f9cdf45f6bbca2570c31215629bb5d6fb97493478b8ff3db6fffbc55
Validation:^[a-fA-F0-9]{0,128}$
Remarks:Used for digest authentication
2.3.10.10 pkid (FI-1658)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-398):
Type:Active (Insert)
Rule Name:Automatically Insert Credential (Password only) record for ApplicationUsers
Description:When an ApplicationUser is inserted, automatically generate Credential record for Password with default policy specified in CredentialPolicyDefault table. Policy is not applied until Credential is updated for the first time.
Test Condition:ON INSERT INTO ApplicationUser:
Rule (RI-2138):
Type:Validation (Delete)
Rule Name:Self-Provisioing App User deletion not allowed
Description:Application User selected in the self provisioning configuration cannot be deleted
Test Condition:On Delete (select count(*) from globalsetting where tkglobalsetting=TypeGlobalSetting.GLOBAL_SETTING_SELF_PROVISIONING_IVR_APPUSER and settingvalue=applicationuser.pkid) < 1
Error Message:This Application User is being used in the Self Provisioing Configuration hence cannot be deleted.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.11 applicationusercapfmap (TI-353)
Description:1-N relation between App User to CAPF
Fields:
2.3.11.1 authenticationstring (FI-2622)
Type:string [50]
Default Value:EMPTY
2.3.11.2 fkapplicationuser (FI-2630)
Type:guid (Indexed, Cascade Delete, Not Modifiable)
Migration Source:ApplicationUser.pkid
2.3.11.3 instanceid (FI-2631)
Type:string [128] (Unique, Indexed, Not Modifiable)
Validation:^[a-zA-Z0-9]{1,128}$
Remarks:To distinguish multiplicity for a single user.
Rule (RI-321):
Type:Validation (Insert/Update)
Rule Name:InstanceID unique across App and EndUserCAPFMaps
Description:InstanceID must be unique across both UserCAPFMap tables (ApplicationUserCAPFMap and EndUserCAPFMap)
Test Condition:ON INSERT/UPDATE IN ApplicationUserCAPFMap OR EndUserCAPFMap IF (SELECT COUNT(*) FROM <table> WHERE lower(InstanceID) = lower(@instanceID)) > 1 THEN throw exception
Error Message:Cannot insert duplicate instance ID in EndUserCAPFMap or ApplicationUserCAPFMap
Remedy:Make sure the instance ID is unique across both the Application and End-User CAPF instances and try again.
2.3.11.4 packetcaptureduration (FI-2621)
Type:long (Null OK)
Default Value:0
2.3.11.5 pkid (FI-2629)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-314):
Type:Active (Delete)
Rule Name:cascade delete in NumPlanASMap
Description:on enduserASMap delete, delete NumPlanASMap
Test Condition:delete enduserASMap record
Rule (RI-373):
Type:Active (Insert)
Rule Name:Insert Dynamic Records for ApplicationUserCAPFMap Table
Description:When an Application User is mapped to a credentials (CAPF record), insert a record for the frequently updated fields
Test Condition:ON INSERT INTO ApplicationUserCAPFMap
2.3.11.6 subjectname (FI-2879)
Type:string [128]
Default Value:EMPTY
Remarks:Subject name of the certificate
2.3.11.7 tkauthenticationmode (FI-2625)
Type:enum
Default Value:2
2.3.11.8 tkcertificate (FI-2627)
Type:enum
Default Value:0
2.3.11.9 tkcertificateoperation (FI-2628)
Type:enum
Default Value:1
Remarks:Certificate Operation
2.3.11.10 tkcertificatestatus (FI-2623)
Type:enum
Default Value:1
2.3.11.11 tkeckeysize (FI-27036)
Type:enum (Null OK)
Default Value:NULL
Remarks:EC Key Size(bits) for ApplicationUserCapfMap table
2.3.11.12 tkkeyorder (FI-27035)
Type:enum
Default Value:1
Remarks:Key Order for ApplicationUserCapfMap table
2.3.11.13 tkkeysize (FI-2626)
Type:enum
Default Value:3
2.3.11.14 tkpacketcapturemode (FI-2620)
Type:enum
Default Value:0
2.3.11.15 upgradefinishtime (FI-2624)
Type:string [50]
Default Value:EMPTY
Uniqueness:fkapplicationuser + instanceid is unique. (MFI-82)

 
2.3.12 applicationusercapfmapdynamic (TI-442)
Description:Frequently updated settings for Application User CAPF settings
Fields:
2.3.12.1 datetimestamp (FI-3311)
Type:long
Default Value:0
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.12.2 fkapplicationusercapfmap (FI-3310)
Type:guid (Unique, Cascade Delete)
2.3.12.3 fkprocessnode (FI-2878)
Type:guid (Cascade Delete, Null OK)
Default Value:NULL
Check Constraint:fkProcessNode != '00000000-1111-0000-0000-000000000000'
Remarks:The server to which this user, with this certificate, has opened a CTI provider.
2.3.12.4 pkid (FI-3309)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.12.5 userstate (FI-3016)
Type:long
Default Value:0
Uniqueness:No multicolumn uniqueness constraints

 
2.3.13 applicationuserdevicemap (TI-297)
Description:Maps controllability between App Users & Devices.
Fields:
2.3.13.1 description (FI-2076)
Type:string [200]
Default Value:EMPTY
Validation:^[^""""]{0,50}$
Remarks:ApplicationUser-entered description of a controlled device (allows Unicode).
2.3.13.2 fkapplicationuser (FI-2078)
Type:guid (Cascade Delete)
2.3.13.3 fkdevice (FI-2077)
Type:guid (Cascade Delete)
2.3.13.4 pkid (FI-2079)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.13.5 tkuserassociation (FI-2390)
Type:enum
Uniqueness:fkdevice + fkapplicationuser + tkuserassociation is unique. (MFI-76)

 
2.3.14 applicationuserdirgroupmap (TI-238)
Description:Similar to UserGroupMap to group ApplicationUser into a DirGroup
Fields:
2.3.14.1 fkapplicationuser (FI-1685)
Type:guid (Cascade Delete)
2.3.14.2 fkdirgroup (FI-1686)
Type:guid (Cascade Delete)
Rule (RI-201):
Type:Validation (Update/Delete)
Rule Name:Standard CCM Super Users Group Restriction
Description:The CCM Super Users Group must contain at least one application user at all times to prevent locking primary administrator out of the system.
Test Condition:ON DELETE FROM ApplicationUserDirGroupMap IF (DirGroup = 'CCM Super User') AND (SELECT COUNT(*) FROM ApplicationUserDirGroupMap = 0) THEN throw exception; ON UPDATE ApplicationUserDirGroupMap IF (DirGroup = 'CCM Super User') AND (old_fkDirGroup <> new_fkDirGroup) THEN throw exception
Error Message:CCM Super User Group must contain at least one application user at all times.
Remedy:Add another Application User to be the CCM Super User before removing the current user.
2.3.14.3 isstandard (FI-2052)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:If standard set true during installation. Standard groups are only modifiable by installations.
2.3.14.4 pkid (FI-1684)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:fkdirgroup + fkapplicationuser is unique. (MFI-75)

 
2.3.15 applicationusernumplanmap (TI-355)
Description:To keep M-N relation between App User & NumPlan
Fields:
2.3.15.1 fkapplicationuser (FI-2645)
Type:guid (Cascade Delete)
2.3.15.2 fknumplan (FI-2646)
Type:guid (Cascade Delete)
2.3.15.3 pkid (FI-2644)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.15.4 tkdnusage (FI-2647)
Type:enum
Uniqueness:No multicolumn uniqueness constraints

 
2.3.16 appserver (TI-372)
Description:Denotes the various Application servers that a CCM communicates with
Fields:
2.3.16.1 administrationurl (FI-3564)
Type:string [255]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9!#$%&'()*+,./:;<=>?@[^_{|}~\\-]{0,255}$
Remarks:Used to create a link to the Administrative application for the AppServer
2.3.16.2 enduserurl (FI-3567)
Type:string [255]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9!#$%&'()*+,./:;<=>?@[^_{|}~\\-]{0,255}$
Remarks:Used to create a link to the EndUser application for the AppServer
2.3.16.3 fkprocessnode (FI-3716)
Type:guid (Null OK)
Default Value:NULL
Remarks:Allows an application server's settings to be associated with a specific server in the cluster
2.3.16.4 ipaddr (FI-2758)
Type:string [15]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9]?[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9]?[0-9])$
Remarks:IP Address of the App server.
2.3.16.5 name (FI-2756)
Type:string [50]
Rule (RI-420):
Type:Validation (Insert/Update)
Rule Name:AppServer.Name with .localdomain restriction
Description:For each type of application server, only one instance can have the .localdomain suffix in the name. For tkAppServer=3, AppServer.Name cannot have duplicate values. AppServer.Name cannot have a value already existing for ProcessNode.Name
Test Condition:ON INSERT/UPDATE IN AppServer: Check that there is only one AppServer entry with .localdomain per tkAppServer type. Check that new AppServer.Name is not equal to any old Appserver.Name for tkAppServer=3.Check that new AppServer.Name is not equal to existing ProcessNode.Name
Error Message:Cannot assign more than one localdomain AppServer record per AppServer type.Cannot not have more than one Cisco Unified Presence Server with the same name as another Cisco Unified Presence Server or a Cisco Unified Communications Manager Server.
Remedy:Check the server name you entered to make sure it does not already exist as an Application Server or Cisco Unified Communications Manager Server
Rule (RI-474):
Type:Validation (Update)
Rule Name:Preserve .localdomain suffix for CUCM BE Unity AppServer
Description:For Business Edition (co-res) install, an AppServer entry for Cisco Unity Connection is created with .localdomain suffix in the name. On update, make sure .localdomain is not removed.
Test Condition:ON UPDATE IN AppServer: IF (old_tkAppServer = APP_SERVER_UNITY_1_X) AND (old_name LIKE ('%.localdomain') AND new_name NOT LIKE ('%.localdomain') THEN throw exception END IF
Error Message:Cannot remove the .localdomain suffix for Cisco Unity Connection application server
Remedy:Include the .localdomain suffix in the appserver name.
Rule (RI-690):
Type:Validation (Insert/Update)
Rule Name:AppServer Name is not a valid format for RemoteSyslog Server Type
Description:Cisco Unified Communications Manager shall validate that AppServer name for Remote Syslog Server type is generally a valid FQDN (up to 255 characters) or IP Address.
Test Condition:Make sure AppServer Name is ip, hostname or domain name
Remedy:1
Rule (RI-945):
Type:Active (Update/Delete)
Rule Name:Update/Delete on AppServer to sync it up with UCService
Description:On Deletion of a record from AppServer table, set the corresponding fkAppServer field to NULL in UCService table. On an Update on AppServer table with name getting changed, update the hostnameorip field in UCService table to match (only if it does not already match).
Test Condition:ON DELETE FROM AppServer, UPDATE UCService SET fkAppServer = NULL WHERE fkAppServer = AppServer.pkid; ON UPDATE ON AppServer with name getting changed, IF (AppServer.name <> UCService.hostnameorip) THEN UPDATE UCService SET hostnameorip = AppServer.name WHERE fkAppServer = AppServer.pkid;
2.3.16.6 pkid (FI-2755)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-945):
Type:Active (Update/Delete)
Rule Name:Update/Delete on AppServer to sync it up with UCService
Description:On Deletion of a record from AppServer table, set the corresponding fkAppServer field to NULL in UCService table. On an Update on AppServer table with name getting changed, update the hostnameorip field in UCService table to match (only if it does not already match).
Test Condition:ON DELETE FROM AppServer, UPDATE UCService SET fkAppServer = NULL WHERE fkAppServer = AppServer.pkid; ON UPDATE ON AppServer with name getting changed, IF (AppServer.name <> UCService.hostnameorip) THEN UPDATE UCService SET hostnameorip = AppServer.name WHERE fkAppServer = AppServer.pkid;
2.3.16.7 tkappserver (FI-2757)
Type:enum
Rule (RI-420):
Type:Validation (Insert/Update)
Rule Name:AppServer.Name with .localdomain restriction
Description:For each type of application server, only one instance can have the .localdomain suffix in the name. For tkAppServer=3, AppServer.Name cannot have duplicate values. AppServer.Name cannot have a value already existing for ProcessNode.Name
Test Condition:ON INSERT/UPDATE IN AppServer: Check that there is only one AppServer entry with .localdomain per tkAppServer type. Check that new AppServer.Name is not equal to any old Appserver.Name for tkAppServer=3.Check that new AppServer.Name is not equal to existing ProcessNode.Name
Error Message:Cannot assign more than one localdomain AppServer record per AppServer type.Cannot not have more than one Cisco Unified Presence Server with the same name as another Cisco Unified Presence Server or a Cisco Unified Communications Manager Server.
Remedy:Check the server name you entered to make sure it does not already exist as an Application Server or Cisco Unified Communications Manager Server
Rule (RI-474):
Type:Validation (Update)
Rule Name:Preserve .localdomain suffix for CUCM BE Unity AppServer
Description:For Business Edition (co-res) install, an AppServer entry for Cisco Unity Connection is created with .localdomain suffix in the name. On update, make sure .localdomain is not removed.
Test Condition:ON UPDATE IN AppServer: IF (old_tkAppServer = APP_SERVER_UNITY_1_X) AND (old_name LIKE ('%.localdomain') AND new_name NOT LIKE ('%.localdomain') THEN throw exception END IF
Error Message:Cannot remove the .localdomain suffix for Cisco Unity Connection application server
Remedy:Include the .localdomain suffix in the appserver name.
Rule (RI-690):
Type:Validation (Insert/Update)
Rule Name:AppServer Name is not a valid format for RemoteSyslog Server Type
Description:Cisco Unified Communications Manager shall validate that AppServer name for Remote Syslog Server type is generally a valid FQDN (up to 255 characters) or IP Address.
Test Condition:Make sure AppServer Name is ip, hostname or domain name
Remedy:1
Rule (RI-2150):
Type:Validation (Insert)
Rule Name:Cannot Insert IM & Presence node as AppServer
Description:On INSERT of AppServer, it would ensure that it is not inserting IM & Presence node because same is to be added in processnode table with appropriate role.
Test Condition:On Insert
Uniqueness:No multicolumn uniqueness constraints

 
2.3.17 appserverapplicationusermap (TI-407)
Description:This table will hold the relationship on the CCM side between application server and application user used to log into application server
Fields:
2.3.17.1 content (FI-3341)
Type:text (Null OK)
2.3.17.2 fkapplicationuser (FI-3029)
Type:guid (Cascade Delete)
2.3.17.3 fkappserver (FI-3028)
Type:guid (Cascade Delete)
2.3.17.4 pkid (FI-3027)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.18 appserverinfo (TI-373)
Description:Contains info pertaining to App servers
Fields:
2.3.18.1 content (FI-2761)
Type:text (Null OK)
Default Value:NULL
2.3.18.2 fkappserver (FI-2763)
Type:guid (Cascade Delete)
2.3.18.3 pkid (FI-2760)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.18.4 tkappservercontent (FI-2762)
Type:enum
Uniqueness:No multicolumn uniqueness constraints

 
2.3.19 availdialplan (TI-405)
Description:Available DialPlan table
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.19.1 availableversion (FI-3012)
Type:string [15] (Not Modifiable)
Default Value:EMPTY
Remarks:Version number of the Dial Plan installer
2.3.19.2 description (FI-3011)
Type:string [50] (Not Modifiable)
Default Value:EMPTY
Remarks:Description of the Dial Plan (e.g., North American Numbering Plan)
2.3.19.3 dialplan (FI-3010)
Type:string [50] (Not Modifiable)
Default Value:EMPTY
Remarks:Name of the Dial Plan (e.g., NANP)
2.3.19.4 pkid (FI-3009)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.19.5 systemdialplan (FI-3031)
Type:guid (Not Modifiable)
Remarks:Unique ID of the Dial Plan as it appears in the DialPlan table (DialPlan.pkid)
Uniqueness:availableversion + systemdialplan is unique. (MFI-92)

 
2.3.20 axlchangenotifyclient (TI-540)
Description:Lists all applications that can subscribe for AXL Change Notification.
Fields:
2.3.20.1 bitmap (FI-9992)
Type:string [32] (Unique, Null OK)
Validation:^[01]{32}$
Remarks:To store the unique value for each client.
2.3.20.2 clientname (FI-9983)
Type:string [32]
Validation:^[a-zA-Z 0-9._-]{1,32}$
Remarks:Name of the application that can subscribe for Change Notification.
2.3.20.3 networkid (FI-9982)
Type:string [32]
Validation:^[a-zA-Z 0-9._-]{1,32}$
Remarks:NetworkID of Client.
2.3.20.4 pkid (FI-9981)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID for the table.
2.3.20.5 pollingstarttime (FI-9991)
Type:long (Null OK)
Remarks:Time from which Notification will be monitored.
2.3.20.6 subscriberid (FI-9984)
Type:long (Unique, Indexed, Not Modifiable)
Check Constraint:(SubscriberId >= 1) AND (SubscriberId <= 10)
Remarks:Subscription Unique Id whose value would be between 1 and 10.
Uniqueness:networkid + clientname is unique. (MFI-173)

 
2.3.21 axlchangenotifysubscribe (TI-541)
Description:Maps each AXL Change Notify Client to the subscription type.
Fields:
2.3.21.1 fkaxlchangenotifyclient (FI-9988)
Type:guid (Cascade Delete)
Remarks:Unique ID of the AXLChangeNotifyClient.
2.3.21.2 pkid (FI-9987)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID for the table.
2.3.21.3 tkchangenotifysubscribe (FI-9989)
Type:enum
Remarks:Determines the class of Change Notification subscription : 0=User,1=Line,2=Phone.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.22 batfileinfo (TI-344)
Description:Information of BAT Files
Fields:
2.3.22.1 datecreated (FI-2552)
Type:long
Remarks:Date when the file is uploaded
2.3.22.2 enduser (FI-2553)
Type:string [50]
Default Value:EMPTY
Remarks:User who created this job
2.3.22.3 isfilefound (FI-2605)
Type:bool
Default Value:TRUE
Remarks:Date when the file is uploaded
2.3.22.4 name (FI-2547)
Type:string [100]
Validation:^[a-zA-Z 0-9._-]{1,100}$
Remarks:BAT File Name
2.3.22.5 pkid (FI-2546)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.22.6 tkbatfunction (FI-2549)
Type:enum
Remarks:File Transaction
Uniqueness:No multicolumn uniqueness constraints

 
2.3.23 batfileinfojobmap (TI-347)
Description:Mapping of Fileinfo and job
Fields:
2.3.23.1 fkbatfileinfo (FI-2571)
Type:guid (Cascade Delete)
2.3.23.2 fkbatjob (FI-2572)
Type:guid (Cascade Delete)
2.3.23.3 pkid (FI-2570)
Type:guid (Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.24 batinputdata (TI-345)
Description:Input data other than csv files
Fields:
2.3.24.1 data (FI-2557)
Type:string [32000]
Default Value:EMPTY
Remarks:Input Data for BAT Jobs
2.3.24.2 name (FI-2556)
Type:string [50]
2.3.24.3 pkid (FI-2555)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.24.4 tkbatfunction (FI-2607)
Type:enum
Remarks:Type of Input Data
2.3.24.5 tkbatusage (FI-2558)
Type:enum
Remarks:Type of Input Data
Uniqueness:No multicolumn uniqueness constraints

 
2.3.25 batinputdatajobmap (TI-348)
Description:Mapping pf BATInputData and Job
Fields:
2.3.25.1 fkbatinputdata (FI-2574)
Type:guid (Cascade Delete)
2.3.25.2 fkbatjob (FI-2575)
Type:guid (Cascade Delete)
2.3.25.3 pkid (FI-2573)
Type:guid (Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.26 batjob (TI-341)
Description:Job submitted via BAT
Fields:
2.3.26.1 description (FI-2538)
Type:string [400]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%\\&<>]{0,100}$
Remarks:Description of the Job
2.3.26.2 enduser (FI-2649)
Type:string [50]
Default Value:EMPTY
Remarks:User who created this job
2.3.26.3 fkdevice (FI-2535)
Type:guid (Cascade Delete, Null OK)
Remarks:Template Information is provided from this device
2.3.26.4 fkenduser (FI-2663)
Type:guid (Cascade Delete, Null OK)
Remarks:Template Information is provided for this User
2.3.26.5 fkmgcp (FI-2536)
Type:guid (Cascade Delete, Null OK)
Remarks:Template Information is provided from this MGCP
2.3.26.6 fknumplan (FI-2537)
Type:guid (Cascade Delete, Null OK)
Remarks:Template Information is provided from this DNorPattern
2.3.26.7 frequencyjobend (FI-2533)
Type:long (Null OK)
Remarks:Denotes when a recurring job ends
2.3.26.8 jobid (FI-2847)
Type:long (Unique, Indexed)
Remarks:unique ID to track Jobs.
2.3.26.9 pkid (FI-2527)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.26.10 scheduleddatetime (FI-2531)
Type:long
Remarks:Denotes the job schedule time.
2.3.26.11 sequence (FI-2530)
Type:long
Check Constraint:(sequence >= 0) AND (sequence <= 20)
Remarks:A number to resolve job execution order when they are scheduled together.
2.3.26.12 submitdatetime (FI-2532)
Type:long
Remarks:Denotes when the job is submitted
2.3.26.13 tkbatfrequency (FI-2534)
Type:enum
2.3.26.14 tkbatfunction (FI-2528)
Type:enum
2.3.26.15 tkbatjobstatus (FI-2606)
Type:enum
Remarks:Holds the Status of the Job
Uniqueness:No multicolumn uniqueness constraints

 
2.3.27 batjobresults (TI-346)
Description:Results of BAT Jobs
Fields:
2.3.27.1 fkbatjob (FI-2561)
Type:guid (Cascade Delete)
Remarks:Job for which the results are displayed
2.3.27.2 isfilefound (FI-2608)
Type:bool
Default Value:TRUE
Remarks:Status of the Job
2.3.27.3 launchdatetime (FI-2567)
Type:long
Default Value:0
Remarks:Data time when job is started
2.3.27.4 logfilename (FI-2562)
Type:string [100]
Default Value:EMPTY
Remarks:Name of the log file
2.3.27.5 numrecordsfailed (FI-2565)
Type:long
Default Value:0
Remarks:Number of Records Failed
2.3.27.6 numrecordsprocessed (FI-2664)
Type:long
Default Value:0
Remarks:Total Number of Records processed
2.3.27.7 numrecordstotal (FI-2566)
Type:long
Default Value:0
Remarks:Total Number of Records processed
2.3.27.8 pkid (FI-2560)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.27.9 tkbatresultstatus (FI-2568)
Type:enum
Remarks:Status of the Job
Uniqueness:No multicolumn uniqueness constraints

 
2.3.28 billingserver (TI-386)
Description:Off cluster billing server
Fields:
2.3.28.1 directory (FI-2868)
Type:string [255]
Default Value:EMPTY
2.3.28.2 enablecdroffloading (FI-6238)
Type:bool
Default Value:TRUE
Remarks:If set to false, CDRs are not offloaded to that particular billing server
2.3.28.3 hostname (FI-2865)
Type:string [255]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$%&'()*+,./:;<=>?@[^_{|}~\\-]{0,255}$
Remarks:FQDN or IP
2.3.28.4 password (FI-2867)
Type:string [128]
Default Value:EMPTY
2.3.28.5 pkid (FI-2863)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.28.6 preserve (FI-2998)
Type:bool
Default Value:FALSE
2.3.28.7 resendonfailure (FI-3702)
Type:bool
Default Value:TRUE
Remarks:Tells CDRM whether or not to send CDR/CMR fiiles after FTP connection is restored.
2.3.28.8 selorder (FI-2864)
Type:long
Default Value:1
Check Constraint:((selorder >= 1) AND (selorder <=3))
Remarks:order of server
2.3.28.9 tkbillingserverprotocol (FI-2869)
Type:enum
Default Value:0
Remarks:conf Bridge location
2.3.28.10 userid (FI-2866)
Type:string [255]
Default Value:EMPTY
Uniqueness:No multicolumn uniqueness constraints

 
2.3.29 blfdirectedcallpark (TI-426)
Description:Busy lamp monitor entries for Directed Call Park feature
Fields:
2.3.29.1 blfindex (FI-3231)
Type:long
Check Constraint:blfindex > 0
Remarks:This field identifies the Directed Call Park Monitor button on the phone (for example, 1, 2, 3, or 4).
2.3.29.2 fkdevice (FI-3232)
Type:guid (Cascade Delete)
Rule (RI-347):
Type:Documentation (Developer notes only)
Rule Name:BLF Directed CallPark device restriction
Description:Device referenced in BLFDirectedCallPark table should support the Directed Call Park feature; Database does not enforce a hard rule on the relationship between this table and device. Instead the feature is available if a phone has a BLF Directed Call Park button.
Test Condition:No check performed. Feature is available or not depending on whether or not a phone button for the feature is configured on the device.
Rule (RI-421):
Type:Active (Insert/Update/Delete records)
Rule Name:devicerelatedversionstamp versionstamp on direct call park busylampfield
Description:Any operation on direct call park busylampfield, update devicerelatedversionstamp record
Test Condition:update dpark busylampfield
2.3.29.3 fknumplan (FI-3233)
Type:guid (Cascade Delete)
Rule (RI-348):
Type:Validation (Insert/Update)
Rule Name:BLF Directed CallPark number must be a Directed Call Park destination
Description:The NumPlan item referenced in BLFDirectedCallPark table must be a diable Directed Call Park pattern. The pattern must contain only dialable digits (0-9, * and #) and may not contain wildcards (X) or expressions with brackets.
Test Condition:ON INSERT/UPDATE in BLFDirectedCallPark: SELECT tkPatternUsage, DNOrPattern INTO patternUsage, pattern FROM NumPlan WHERE pkid = new_fkNumPLan; IF (patternUsage <> PATTERN_USAGE_DIRECTED_CALL_PARK) OR (re_compare(pattern, "^[0-9*#]+$") <> 1) THEN throw exception;
Error Message:The BLF Directed Call Park number must be a dialable Directed Call Park Destination
Remedy:Make sure the Destination is a dialable Directed Call Park number and try again.
2.3.29.4 label (FI-3234)
Type:string [200]
Default Value:EMPTY
Validation:^[^""""%&<>]{0,50}$
Remarks:The text that appears for the BLF Directed Call Park button (allows Unicode).
2.3.29.5 labelascii (FI-3235)
Type:string [50]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~\\-]{0,50}$
Migration Source:BLF.label if all chars are less than 127
Remarks:A safe version of the BLF Directed Call Park Button Label using only English letters (a to Z) and punctuation.
2.3.29.6 pkid (FI-3236)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Uniqueness:blfindex + fkdevice is unique. (MFI-98)
fkdevice + fknumplan is unique. (MFI-99)

 
2.3.30 blfspeeddial (TI-350)
Description:Keeps line status of internal DNs
Fields:
2.3.30.1 blfdestination (FI-2713)
Type:string [255]
Default Value:EMPTY
Migration Source:Value_
Remarks:This is the number or url that the system dials when the user presses the speed-dial button.
Rule (RI-326):
Type:Validation (Insert/Update)
Rule Name:Check BLF SpeedDial Destination for URI
Description:Destinations can be URIs only if the phone supports the additional feature BLF Speed Dial with URI
Test Condition:ON INSERT/UPDATE IN BusyLampField (IF BLFDestination LIKE '%@%' AND SELECT COUNT(*) FROM ProductSupportsFeature where tkProduct = @product AND tkDeviceProtocol IN (@DeviceProtocol, 99) AND tkSupportsFeature = 62) = 0 THEN throw exception
Error Message:This device does not support URI dialing.
Remedy:Make sure the Destination is numeric and try again.
Rule (RI-896):
Type:Active (Insert/Update)
Rule Name:Encode URIs to minimum percent encoded format.
Description:null
Rule (RI-896):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Encode URIs to minimum percent encoded format.
Description:null
2.3.30.2 blfindex (FI-2596)
Type:long
Migration Source:Index_
Remarks:This field identifies the speed-dial button on the phone (for example, 1, 2, 3, or 4).
2.3.30.3 blfsdoptionbitmask (FI-3529)
Type:long
Default Value:0
Check Constraint:(BLFSDOptionBitmask >= 0) AND (BLFSDOptionBitmask <= 1)
Remarks:A Bitmask comprised of valid combinations of values from TypeBLFSpeedDialOption (0 or 1 in this release)
2.3.30.4 fkdevice (FI-2593)
Type:guid (Indexed, Cascade Delete)
Migration Source:pkid from Device
Rule (RI-313):
Type:Active (Insert/Update/Delete records)
Rule Name:devicerelatedversionstamp versionstamp on busylampfield
Description:Any operation on busylampfield, update devicerelatedversionstamp record
Test Condition:update busylampfield
Rule (RI-326):
Type:Validation (Insert/Update)
Rule Name:Check BLF SpeedDial Destination for URI
Description:Destinations can be URIs only if the phone supports the additional feature BLF Speed Dial with URI
Test Condition:ON INSERT/UPDATE IN BusyLampField (IF BLFDestination LIKE '%@%' AND SELECT COUNT(*) FROM ProductSupportsFeature where tkProduct = @product AND tkDeviceProtocol IN (@DeviceProtocol, 99) AND tkSupportsFeature = 62) = 0 THEN throw exception
Error Message:This device does not support URI dialing.
Remedy:Make sure the Destination is numeric and try again.
2.3.30.5 fknumplan (FI-2855)
Type:guid (Cascade Delete, Null OK)
Default Value:NULL
Remarks:pointer to dn and partionion if null use destination
2.3.30.6 label (FI-2592)
Type:string [120]
Default Value:EMPTY
Validation:^[^""""%&<>]{0,30}$
Migration Source:NULL
Remarks:The text that appears for the BLF Speed Dial button (allows Unicode).
2.3.30.7 labelascii (FI-2597)
Type:string [30]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~\\-]{0,30}$
Migration Source:BLF.label if all chars are less than 127
Remarks:A safe version of the BLF Speed Dial Button Label using only English letters (a to Z) and punctuation.
2.3.30.8 pkid (FI-2594)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Uniqueness:blfindex + fkdevice is unique. (MFI-93)
Constraints:
Rule (RFI-187):
Type:Inter-field Condition and Constraint
Constraint:((BLFDestination = '') AND (fkNumPlan IS NOT NULL)) OR ((BLFDestination <> '') AND (fkNumPlan IS NULL))
Remarks:Either an existing internal DN or an external destination can be specified for BLF Speed Dial, but not both.

 
2.3.31 blockingcsslookup (TI-582)
Description:CUBA: To store a mapping between allowed calls and blocking CSS detailsS
Is not replicated.
Fields:
2.3.31.1 allowcallpark (FI-6049)
Type:bool
Default Value:FALSE
Remarks:check for callpark
2.3.31.2 allowcallpickup (FI-6050)
Type:bool
Default Value:FALSE
Remarks:check for callpickup
2.3.31.3 allowemergencycalls (FI-6048)
Type:bool
Default Value:FALSE
Remarks:check for emergency calls
2.3.31.4 fkcallingsearchspace (FI-6051)
Type:guid
Remarks:Reference to CallingSearchSpace
2.3.31.5 pkid (FI-6046)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique identifier for the record
2.3.31.6 tkcosrouting (FI-6047)
Type:enum
Remarks:reference to cosrouting
Uniqueness:No multicolumn uniqueness constraints

 
2.3.32 callerfilterlist (TI-450)
Description:List of allowed or blocked callers for Mobility
Fields:
2.3.32.1 description (FI-3397)
Type:text
Default Value:EMPTY
Validation:^[^\x00-\x1F\x7F""""]{0,128}$
2.3.32.2 fkenduser (FI-3399)
Type:guid (Cascade Delete, Not Modifiable, Null OK)
Default Value:NULL
Remarks:Owner of CallerFilterList
Rule (RI-387):
Type:Validation (Insert/Update)
Rule Name:CallerFilterList limited to 250 per EndUser
Description:An End-User may create up to 250 CallerFilterLists
Test Condition:ON INSERT INTO CallerFilterList: IF (SELECT COUNT(*) FROM CallerFilterList where fkEndUser = new_fkEndUser) > 250 THEN throw exception
Error Message:Cannot have more than 250 CallerFilterLists for an EndUser
Remedy:Remove some CallerFilterLists or consider combining some lists
2.3.32.3 isallowedtype (FI-3398)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:False = Blocked; True = Allowed
2.3.32.4 name (FI-3396)
Type:string [200] (Indexed)
Validation:^[^""%&\\<>]{0,50}$
2.3.32.5 pkid (FI-3395)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:fkenduser + name is unique. (MFI-102)

 
2.3.33 callerfilterlistmember (TI-451)
Description:Members of CallerFilterLists
Fields:
2.3.33.1 dnmask (FI-3402)
Type:dn
DN Type:DN_TYPE_ALL_DIGITS
Default Value:EMPTY
Validation:^[!0-9*#+X]?[0-9*#+X]{0,46}[!0-9*#+X]?$
Remarks:DN mask (allows 0-9, *, #, mask character X and +). Pattern can start and end with wildcard character (!)
Rule (RFI-155):
Type:Inter-field Condition and Constraint
Test Condition:tkCallerFilterMask = 0
Constraint:(DNMask <> '')
Remarks:Directory Number filter cannot have an empty DN Mask.
Rule (RFI-156):
Type:Inter-field Condition and Constraint
Test Condition:tkCallerFilterMask <> 0
Constraint:(DNMask = '')
Remarks:DN Mask is only used for Directory Number filter (not used with private number or number-not-available filter).
Rule (RI-389):
Type:Validation (Insert/Update)
Rule Name:CallerFilterListMember DNMask must be unique within list
Description:The DNMask values within a CallerFilterList must be unique (if not empty); Number Not Available and Private Number filters do not use a DNMask
Test Condition:ON INSERT/UPDATE INTO CallerFilterListMember:
Error Message:The specified DN Mask already exists for this Caller Filter List.
Remedy:Check the DN Mask and make sure it is unique for this list.
2.3.33.2 fkcallerfilterlist (FI-3403)
Type:guid (Cascade Delete, Null OK)
Default Value:NULL
Rule (RI-386):
Type:Validation (Insert/Update)
Rule Name:CallerFilterListMember limited to 1000 per list
Description:A CallerFilterList may have up to 1000 members.
Test Condition:ON INSERT INTO CallerFilterListMember: IF (SELECT COUNT(*) FROM CallerFilterListMember WHERE fkCallerFilterList = new_fkCallerFilterList) > 1000 THEN throw exception;
Error Message:Cannot have more than 1000 members in a Caller Filter List.
Remedy:Remove some members of the list or combine similar filters using wildcards (* or X) if possible.
Rule (RI-389):
Type:Validation (Insert/Update)
Rule Name:CallerFilterListMember DNMask must be unique within list
Description:The DNMask values within a CallerFilterList must be unique (if not empty); Number Not Available and Private Number filters do not use a DNMask
Test Condition:ON INSERT/UPDATE INTO CallerFilterListMember:
Error Message:The specified DN Mask already exists for this Caller Filter List.
Remedy:Check the DN Mask and make sure it is unique for this list.
Rule (RI-417):
Type:Validation (Insert/Update)
Rule Name:Only one instance of Private or Not Available per Caller Filter List
Description:For any given Caller Filter List, only one (1) instance of Private or Not Available members may exist at any given time. However multiple number of Directory Number masks can be added
Test Condition:update DeviceMobilityDynamic
Error Message:IF (nCount > 1 AND new_tkcallerfiltermask <> 0) THEN throw exception;END IF;
Remedy:Only one instance of Private or Not Selected is allowed for any given Caller Filter List
2.3.33.3 pkid (FI-3400)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.33.4 tkcallerfiltermask (FI-3404)
Type:enum
Default Value:0
Rule (RI-417):
Type:Validation (Insert/Update)
Rule Name:Only one instance of Private or Not Available per Caller Filter List
Description:For any given Caller Filter List, only one (1) instance of Private or Not Available members may exist at any given time. However multiple number of Directory Number masks can be added
Test Condition:update DeviceMobilityDynamic
Error Message:IF (nCount > 1 AND new_tkcallerfiltermask <> 0) THEN throw exception;END IF;
Remedy:Only one instance of Private or Not Selected is allowed for any given Caller Filter List
Uniqueness:No multicolumn uniqueness constraints

 
2.3.34 callforwardalloverride (TI-457)
Description:For DNs where forwarding is ignored allowing calls to ring through while a DN is forwarded (CFwdAll)
Fields:
2.3.34.1 callingpartynumber (FI-3427)
Type:dn
DN Type:DN_TYPE_MASK
Validation:^[0-9A-D*#]{1,48}$
Remarks:Calling Party Number for which calls should not be forwarded
2.3.34.2 fknumplan (FI-3426)
Type:guid (Cascade Delete)
Remarks:NumPlan record for DN to which Override is applied (the forwarded line)
2.3.34.3 pkid (FI-3425)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.35 callforwarddynamic (TI-434)
Description:Frequently updated settings for Call Forward All
Insert/Delete is not allowed.
Fields:
2.3.35.1 cfadestination (FI-183)
Type:string [255] (Null OK)
Default Value:NULL
Migration Source:convert from forward
Remarks:Call Forward All (not a pattern)
Rule (RI-837):
Type:Active (Insert/Update)
Rule Name:Store Most Recent Call Foward History Record
Description:For each NumPlan DN maintain a history of the most 5 recent Call Foward destinations specified.
Test Condition:On Insert or Update of CallFoward Destination for a Numplan record
Rule (RI-890):
Type:Active (Insert/Update)
Rule Name:Encode URIs to minimum percent encoded format.
Description:null
Rule (RI-890):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Encode URIs to minimum percent encoded format.
Description:null
2.3.35.2 cfavoicemailenabled (FI-1080)
Type:bool
Default Value:FALSE
2.3.35.3 datetimestamp (FI-3299)
Type:long
Default Value:0
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.35.4 fkcallingsearchspace_cfa (FI-637)
Type:guid (Null OK)
Default Value:NULL
Remarks:Call Forward All
2.3.35.5 fkcallingsearchspace_scfa (FI-2765)
Type:guid (Null OK)
Default Value:NULL
Migration Source:from CSSforCFA Clause
Remarks:Secondary Call Forward All
2.3.35.6 fknumplan (FI-3298)
Type:guid (Unique, Cascade Delete)
Rule (RI-837):
Type:Active (Insert/Update)
Rule Name:Store Most Recent Call Foward History Record
Description:For each NumPlan DN maintain a history of the most 5 recent Call Foward destinations specified.
Test Condition:On Insert or Update of CallFoward Destination for a Numplan record
2.3.35.7 pkid (FI-3297)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.36 callforwardhistorydynamic (TI-595)
Description:To store the last 5 Call Forward destination DN updates done on a line
Insert/Delete is not allowed.
Fields:
2.3.36.1 datetimestamp (FI-6129)
Type:long
Remarks:Uniform Integer representation of the most recent time that the corresponding DNOrPattern was used as a forward destination for the associated line
2.3.36.2 dnorpattern (FI-6128)
Type:dn (Not Modifiable)
DN Type:DN_TYPE_MASK
Remarks:Indicates the CallForward DN associated with a line for a given timestamp
2.3.36.3 fknumplan (FI-6127)
Type:guid (Indexed, Not Modifiable)
Remarks:Represents the line on which Call Forward was updated. This field is intentionally marked as NOT cascade delete since its a CUBA table
2.3.36.4 pkid (FI-6126)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique identifier for the record
Uniqueness:No multicolumn uniqueness constraints

 
2.3.37 callingsearchspace (TI-73)
Description:For Dial Plan - devices call to a calling search space made up of route partitions.
Fields:
2.3.37.1 clause (FI-695)
Type:memo (Not Modifiable, Null OK)
Default Value:NULL
Remarks:Ordered list of colon separated RoutePartition Names via CallingSearchSpaceMember
Rule (RI-5):
Type:Active (Insert/Update/Delete records)
This field is modified by this rule.
Rule Name:CSS Clause Update on Member Insert/Delete
Description:When a new CSS Member record (new partition) is inserted, or an existing record is modified, the CSS Clause of the referenced CSS (CallingSearchSpaceMember.fkCallingSearchSpace) must be updated to reflect the change
Test Condition:Insert or Update in CallingSearchSpaceMember
Rule (RI-6):
Type:Active (Insert/Update/Delete records)
This field is modified by this rule.
Rule Name:CSS Clause Update on Member Update
Description:If any information about a CSS Member changes (sort order, referenced partition), the CSS Clause must be updated to reflect the change
Test Condition:Updates in CallingSearchSpaceMember
Rule (RI-7):
Type:Active (Insert/Update/Delete records)
This field is modified by this rule.
Rule Name:CSS Clause Update on Route Partition Name Update
Description:If the name of a Route Partition changes, any CSS Clause containing that partition must be updated to reflect the new name
Test Condition:RoutePartition.Name changes
2.3.37.2 description (FI-133)
Type:string [200]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%&<>]{0,50}$
Migration Source:N/A
Remarks:Description for CallingSerachSpace.
2.3.37.3 dialplanwizardgenid (FI-676)
Type:long (Indexed, Null OK)
Default Value:NULL
Remarks:This record created by DialPlanWizard
2.3.37.4 name (FI-132)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
Migration Source:N/A
Remarks:Unique name
2.3.37.5 pkid (FI-131)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-448):
Type:Active (Delete)
Rule Name:Cannot delete pkid of css if useDevicePoolCdpnTransformCSS is false
Description:Cannot delete pkid of css if useDevicePoolCdpnTransformCSS is false
Test Condition:if CSS.pkid=device.fkCallingSearchSpace_CdPNTransform and useDevicePoolCdpnTransformCSS='f' then pkid of CSS cannot be deleted. IF useDevicePoolCdpnTransformCSS='t' THEN update device set fkCallingSearchSpace_CdPNTransform=NULL
Error Message:CSS cannot be deleted until it is first removed from the associated gateway if the useDevicePoolCdpnTransformCSS is false
Rule (RI-450):
Type:Active (Delete)
Rule Name:Cannot delete pkid of css if useDevicePoolCgpnTransformCSS is false
Description:Cannot delete pkid of css if useDevicePoolCgpnTransformCSS is false
Test Condition:if CSS.pkid=device.fkCallingSearchSpace_CgPNTransform and useDevicePoolCgpnTransformCSS='f' then pkid of CSS cannot be deleted. IF useDevicePoolCgpnTransformCSS='t' THEN update device set fkCallingSearchSpace_CgPNTransform=NULL
Error Message:CSS cannot be deleted until it is first removed from the associated phone if the useDevicePoolCgpnTransformCSS is false
2.3.37.6 resettoggle (FI-3124)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
2.3.37.7 tkpartitionusage (FI-3252)
Type:enum (Not Modifiable)
Default Value:99
Check Constraint:tkPartitionUsage!=21
Remarks:Defines use of CSS (Intercom or other)
2.3.37.8 tkreset (FI-3125)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.38 callingsearchspacemember (TI-74)
Description:Lists the RoutePartitions in a Calling Search Space.
Fields:
2.3.38.1 fkcallingsearchspace (FI-135)
Type:guid (Indexed, Cascade Delete, Not Modifiable)
Migration Source:new
Rule (RI-252):
Type:Active (Insert/Update/Delete records)
Rule Name:BuildCSSClause
Description:On insert, update or delete of CSSMember rebuild the css clause for the associated CSS. Maximum length for the clause is 512 characters including the delimiters.
Test Condition:ON INSERT/UPDATE/DELETE IN CallingSearchSpaceMember: CSS Clause = Route Partition Names delimited by colon; IF LENGTH(CSSClause) > 512 THEN throw exception
Error Message:CSS Clause cannot exceed 512 characters
Remedy:Shorten the individual Partition names or use fewer partitions in the Calling Search Space
Rule (RI-367):
Type:Validation (Insert/Update)
Rule Name:Intercom and other CSS/Partition cannot be mixed
Description:Intercom CSS can only contain Intercom Partitions. Non-Intercom CSS can only contain non-Intercom Partitions (partition usage must match for CSS and member partitions)
Test Condition:ON INSERT/UPDATE IN CallingSearchSpaceMember: IF ((SELECT tkPartitionUsage FROM RoutePartition WHERE pkid = new_fkRoutePartition) <> (SELECT tkPartitionUsage FROM CallingSearchSpace WHERE pkid = new_fkCallingSearchSpace)) THEN throw exception
Error Message:Intercom and non-Intercom partitions cannot be mixed
Remedy:Use only Intercom partitions for Intercom CSS, and only non-Intercom partitions for non-Intercom CSS
2.3.38.2 fkroutepartition (FI-136)
Type:guid (Cascade Delete)
Rule (RI-367):
Type:Validation (Insert/Update)
Rule Name:Intercom and other CSS/Partition cannot be mixed
Description:Intercom CSS can only contain Intercom Partitions. Non-Intercom CSS can only contain non-Intercom Partitions (partition usage must match for CSS and member partitions)
Test Condition:ON INSERT/UPDATE IN CallingSearchSpaceMember: IF ((SELECT tkPartitionUsage FROM RoutePartition WHERE pkid = new_fkRoutePartition) <> (SELECT tkPartitionUsage FROM CallingSearchSpace WHERE pkid = new_fkCallingSearchSpace)) THEN throw exception
Error Message:Intercom and non-Intercom partitions cannot be mixed
Remedy:Use only Intercom partitions for Intercom CSS, and only non-Intercom partitions for non-Intercom CSS
2.3.38.3 pkid (FI-134)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.38.4 sortorder (FI-137)
Type:long
Check Constraint:SortOrder >= 0
Remarks:Gaps in SortOrder are allowed - not rebuilt on delete
Rule (RI-6):
Type:Active (Insert/Update/Delete records)
Rule Name:CSS Clause Update on Member Update
Description:If any information about a CSS Member changes (sort order, referenced partition), the CSS Clause must be updated to reflect the change
Test Condition:Updates in CallingSearchSpaceMember
Uniqueness:fkcallingsearchspace + fkroutepartition is unique. (MFI-7)
fkcallingsearchspace + sortorder is unique. (MFI-8)
Rules:
Rule (RI-5):
Type:Active (Insert/Update/Delete records)
Rule applied when record is inserted or updated.
Rule Name:CSS Clause Update on Member Insert/Delete
Description:When a new CSS Member record (new partition) is inserted, or an existing record is modified, the CSS Clause of the referenced CSS (CallingSearchSpaceMember.fkCallingSearchSpace) must be updated to reflect the change
Test Condition:Insert or Update in CallingSearchSpaceMember
Rule (RI-169):
Type:Documentation (Developer notes only)
Rule applied when record is inserted or updated.
Rule Name:CallingSearchSpaceMember - Limited by Clause
Description:Currently the number of members is limited by the length of the CallingSearchSpace.Clause (created when the names of the members are joined by a colon, e.g., Part1:Part2:Part3). This limitation is expected to be removed in a later release and replaced by a fixed maximum number of members.
Test Condition:SELECT LENGTH(Clause) FROM CallingSearchSpace WHERE pkid = @CallingSearchSpaceMember.fkCallingSearchSpace

 
2.3.39 callmanager (TI-5)
Description:Lists every CallManager in the system.
Fields:
2.3.39.1 ctiid (FI-418)
Type:identity (Unique, Not Modifiable)
Migration Source:CallManagerID
Remarks:Trigger set on insert. Try to keep number as small so reuse missing numbers. This value is used by CCM to identify itself to other CCM applications on other servers in the cluster.
Rule (RI-2):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Generate CTI ID value
Description:On insert of a new record generate a unique 32-bit integer value and store the result in the CTI ID field
Test Condition:On Insert
2.3.39.2 description (FI-165)
Type:string [200]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%\\&<>]{0,50}$
Migration Source:CallManagerName (Create record if record does not exist)
Remarks:Description of the Cisco CallManager.
2.3.39.3 ethernetphoneport (FI-166)
Type:long
Default Value:2000
Check Constraint:(EthernetPhonePort >= 1024) AND (EthernetPhonePort <= 49151)
Migration Source:EthernetPhonePort (if no record, read from SCM.ini or default to 2000)
Remarks:Cisco CallManager uses this TCP port to communicate with the Cisco IP Phones on the network. Accept the default port of 2000 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.
Rule (RI-8):
Type:Validation (Insert/Update)
Rule Name:CallManager TCP/IP Port Uniqueness
Description:The TCP/IP Ports used by a CallManager must be unique - two port settings may not have the same value
Test Condition:CallManager.AnalogAccessPort != CallManager.DigitalAccessPort != CallManager.EthernetPhonePort != CallManager.MGCPKeepAlivePort != CallManager.MGCPListenPort
Rule (RI-270):
Type:Active (Insert/Update)
Rule Name:callmanager versionstamp
Description:on change to anything in callmanager table, update device versionstamp
Test Condition:update device
2.3.39.4 fklbmgroup (FI-9967)
Type:guid (Indexed, Null OK)
Default Value:NULL
Remarks:LBMGroup associated to a node. LBMGroup assigment is optional as long as LBM service is running locally on UCM node
2.3.39.5 fkprocessnode (FI-420)
Type:guid (Unique, Cascade Delete)
Check Constraint:fkProcessNode != '00000000-1111-0000-0000-000000000000'
Migration Source:CM's process node recently added
Remarks:Select the server where this Cisco CallManager is installed.
Rule (RI-270):
Type:Active (Insert/Update)
Rule Name:callmanager versionstamp
Description:on change to anything in callmanager table, update device versionstamp
Test Condition:update device
2.3.39.6 mgcpkeepaliveport (FI-635)
Type:long
Default Value:2428
Check Constraint:(MGCPKeepAlivePort >= 1024) AND (MGCPKeepAlivePort <= 49151)
Remarks:Cisco CallManager uses this TCP port to exchange keepalive messages with its associated MGCP gateway. Accept the default port of 2428 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.
Rule (RI-8):
Type:Validation (Insert/Update)
Rule Name:CallManager TCP/IP Port Uniqueness
Description:The TCP/IP Ports used by a CallManager must be unique - two port settings may not have the same value
Test Condition:CallManager.AnalogAccessPort != CallManager.DigitalAccessPort != CallManager.EthernetPhonePort != CallManager.MGCPKeepAlivePort != CallManager.MGCPListenPort
Rule (RI-270):
Type:Active (Insert/Update)
Rule Name:callmanager versionstamp
Description:on change to anything in callmanager table, update device versionstamp
Test Condition:update device
2.3.39.7 mgcplistenport (FI-634)
Type:long
Default Value:2427
Check Constraint:(MGCPListenPort >= 1024) AND (MGCPListenPort <= 49151)
Remarks:Cisco CallManager uses this TCP port to detect messages from its associated MGCP gateway. Accept the default port of 2427 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.
Rule (RI-8):
Type:Validation (Insert/Update)
Rule Name:CallManager TCP/IP Port Uniqueness
Description:The TCP/IP Ports used by a CallManager must be unique - two port settings may not have the same value
Test Condition:CallManager.AnalogAccessPort != CallManager.DigitalAccessPort != CallManager.EthernetPhonePort != CallManager.MGCPKeepAlivePort != CallManager.MGCPListenPort
Rule (RI-270):
Type:Active (Insert/Update)
Rule Name:callmanager versionstamp
Description:on change to anything in callmanager table, update device versionstamp
Test Condition:update device
2.3.39.8 name (FI-164)
Type:string [50] (Unique)
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{1,50}$
Migration Source:Description
Remarks:Name of this CallManager.
2.3.39.9 pkid (FI-163)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-270):
Type:Active (Insert/Update)
Rule Name:callmanager versionstamp
Description:on change to anything in callmanager table, update device versionstamp
Test Condition:update device
Rule (RI-332):
Type:Active (Insert/Update)
Rule Name:Prevent port conflict between CCMs and SIP Tunk Security Profiles
Description:on I/U of SecurityProfile and CCM
Test Condition:prevent bad port combinations
Rule (RI-605):
Type:Active (Insert)
Rule Name:RTMT Reporting Record Insert
Description:On insert of a callmanager record, insert the RTMT reporting records
Test Condition:?
2.3.39.10 resettoggle (FI-3129)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-270):
Type:Active (Insert/Update)
Rule Name:callmanager versionstamp
Description:on change to anything in callmanager table, update device versionstamp
Test Condition:update device
2.3.39.11 sipport (FI-2391)
Type:long
Default Value:5060
Check Constraint:(SIPPort >= 1024) AND (SIPPort <= 49151)
Migration Source:EthernetPhonePort (if no record, read from SCM.ini or default to 2000)
Remarks:Cisco CallManager uses this port to communicate with the Cisco IP Phones on the network for SIP protocol. Accept the default port of 5060 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.
Rule (RI-332):
Type:Active (Insert/Update)
Rule Name:Prevent port conflict between CCMs and SIP Tunk Security Profiles
Description:on I/U of SecurityProfile and CCM
Test Condition:prevent bad port combinations
2.3.39.12 sipsecuredport (FI-2392)
Type:long
Default Value:5061
Check Constraint:(SIPSecuredPort >= 1024) AND (SIPSecuredPort <= 49151)
Remarks:Cisco CallManager uses this port for secured communication with the Cisco IP Phones on the network for SIP protocol. Accept the default port of 5061 unless this port is already in use on your system. Ensure all port entries are unique. Valid port numbers range from 1024 to 49151.
Rule (RI-332):
Type:Active (Insert/Update)
Rule Name:Prevent port conflict between CCMs and SIP Tunk Security Profiles
Description:on I/U of SecurityProfile and CCM
Test Condition:prevent bad port combinations
2.3.39.13 tkreset (FI-3130)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
Uniqueness:No multicolumn uniqueness constraints
Constraints:
Rule (RFI-125):
Type:Inter-field Condition and Constraint
Constraint:( EthernetPhonePort NOT IN ( MGCPKeepAlivePort , MGCPListenPort ) ) AND ( MGCPKeepAlivePort NOT IN ( MGCPListenPort ) )
Remarks:Ports on an IP based system node must be unique.
Rules:
Rule (RI-2):
Type:Active (Insert)
Rule applied when record is inserted.
Rule Name:Generate CTI ID value
Description:On insert of a new record generate a unique 32-bit integer value and store the result in the CTI ID field
Test Condition:On Insert
Rule (RI-168):
Type:Validation (Insert/Update)
Rule applied when record is inserted.
Rule Name:Max 255 CallManagers per Cluster
Description:A Cisco CallManager cluster may have no more than 255 CallManagers defined.
Test Condition:IF ((SELECT COUNT(*) FROM CallManager) > 255) THEN throw exception
Error Message:A Cisco CallManager cluster may have no more than 255 CallManagers defined.

 
2.3.40 callmanagergroup (TI-6)
Description:Used for redundancy and rehoming of devices
Fields:
2.3.40.1 name (FI-170)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
Migration Source:Description, create one if none exist, make default
Remarks:Name of the CallManager group.
2.3.40.2 pkid (FI-169)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-9):
Type:Validation (Insert)
Rule Name:Set CallManager Group TFTP Default
Description:Only one CallManagerGroup can be the default for TFTP; when a CallManagerGroup is made the default, the existing default must be updated to set CallManagerGroup.TFTPDefault to 0
Test Condition:Set CallManagerGroup.TFTPDefault = 1 on Insert or change setting from 0 to 1 on Update
2.3.40.3 resettoggle (FI-3126)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
2.3.40.4 tftpdefault (FI-283)
Type:bool (Not Modifiable)
Default Value:0
Migration Source:DefaultGroup
Remarks:Whether this Cisco CallManager group is the default Cisco CallManager group when auto-registration is enabled. Note : Each Cisco CallManager cluster can have only one default auto-registration group.
Rule (RI-9):
Type:Validation (Insert)
Rule Name:Set CallManager Group TFTP Default
Description:Only one CallManagerGroup can be the default for TFTP; when a CallManagerGroup is made the default, the existing default must be updated to set CallManagerGroup.TFTPDefault to 0
Test Condition:Set CallManagerGroup.TFTPDefault = 1 on Insert or change setting from 0 to 1 on Update
Rule (RI-10):
Type:Validation (Delete)
Rule Name:Delete CallManager Group TFTP Default
Description:There must be a CallManagerGroup TFTP Default in the system at all times. The current default CallManager Group cannot be deleted
Test Condition:Delete record where CallManagerGroup.TFTPDefault = 1
Error Message:Cannot delete the TFTP Default CallManager Group.
Remedy:Make another CallManager Group the TFTP Default before deleting this CallManager Group.
Rule (RI-11):
Type:Validation (Update)
Rule Name:CallManager Group TFTP Default Required
Description:There must be a CallManagerGroup TFTP Default in the system at all times. Cannot set the current default to 0 manually; it is set to 0 by rule when another CallManager Group is made the TFTP Default.
Test Condition:Change CallManagerGroup.TFTPDefault from 1 to 0
Error Message:A Default CallManager Group for TFTP is required. You cannot remove the TFTP Default setting of this CallManager Group.
Remedy:Make another CallManager Group the TFTP Default. The TFTP Default setting for this CallManager Group will automatically be set to false.
2.3.40.5 tkreset (FI-3127)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
Uniqueness:No multicolumn uniqueness constraints
Rules:
Rule (RI-9):
Type:Validation (Insert)
This table is modified by this rule.
Rule Name:Set CallManager Group TFTP Default
Description:Only one CallManagerGroup can be the default for TFTP; when a CallManagerGroup is made the default, the existing default must be updated to set CallManagerGroup.TFTPDefault to 0
Test Condition:Set CallManagerGroup.TFTPDefault = 1 on Insert or change setting from 0 to 1 on Update
Rule (RI-10):
Type:Validation (Delete)
Rule applied when record is deleted.
Rule Name:Delete CallManager Group TFTP Default
Description:There must be a CallManagerGroup TFTP Default in the system at all times. The current default CallManager Group cannot be deleted
Test Condition:Delete record where CallManagerGroup.TFTPDefault = 1
Error Message:Cannot delete the TFTP Default CallManager Group.
Remedy:Make another CallManager Group the TFTP Default before deleting this CallManager Group.
Rule (RI-12):
Type:Validation (Insert/Update)
Rule applied when record is inserted.
Rule Name:CallManager Group limited to 3 CallManagers
Description:The can be no more than three (3) Cisco CallManagers in a CallManager Group
Test Condition:SELECT Count(*) FROM CallManagerGroupMember WHERE fkCallManagerGroup = @CallManagerGroup.pkid > 3
Error Message:A Cisco CallManager Group may not contain more than 3 Cisco CallManagers

 
2.3.41 callmanagergroupmember (TI-7)
Description:Ordered membership of CallManagers in CallManagerGroups
Fields:
2.3.41.1 fkcallmanager (FI-173)
Type:guid (Cascade Delete)
Migration Source:convert from CallManagerGroupList.CallManagerID
2.3.41.2 fkcallmanagergroup (FI-172)
Type:guid (Indexed, Cascade Delete)
Migration Source:convert from CallManagerGroupList.CallManagerGroupID
Rule (RI-12):
Type:Validation (Insert/Update)
Rule Name:CallManager Group limited to 3 CallManagers
Description:The can be no more than three (3) Cisco CallManagers in a CallManager Group
Test Condition:SELECT Count(*) FROM CallManagerGroupMember WHERE fkCallManagerGroup = @CallManagerGroup.pkid > 3
Error Message:A Cisco CallManager Group may not contain more than 3 Cisco CallManagers
2.3.41.3 pkid (FI-171)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-269):
Type:Active (Insert/Update/Delete records)
Rule Name:callmanagergroupmember versionstamp
Description:on change to anything in callmanagergroupmember, update device versionstamp
Test Condition:update callmanager group member
2.3.41.4 priority (FI-174)
Type:long
Check Constraint:Priority >= 0
Migration Source:CallManagerGroupList.Priority
Remarks:CallManager Groups are made up of an ordered list of from one to three CallManagers. This field orders the members of the group. There is no requirment for a member in a group to be at priority 0. Nor is there a requirment that the priorities be sequential within a CallManager Group.
Uniqueness:fkcallmanagergroup + fkcallmanager is unique. (MFI-2)
fkcallmanagergroup + priority is unique. (MFI-3)

 
2.3.42 callpark (TI-2843)
Description:Table for storing CTI ID for ParkDNs
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.42.1 ctiid (FI-26768)
Type:identity (Unique, Not Modifiable)
Check Constraint:(ctiid >= 0) AND (ctiid <= 4194304)
Migration Source:No more CTI ID values available for Call Park. Limit of 4,194,304 IDs Call Park CTI IDs has been exceeded. CTI IDs are reset during upgrade.
Remarks:Serial Unique ID for CTI
2.3.42.2 fknumplan (FI-26767)
Type:guid (Unique, Indexed, Cascade Delete, Not Modifiable)
Remarks:CallPark number in NumPlan
2.3.42.3 pkid (FI-26766)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:generated, new table gets all records in NumPlan
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.43 carrierselectcodedetails (TI-1085)
Description:CUBA: Code details for particular carrier
Is not replicated.
Fields:
2.3.43.1 fkcarrierselectprofile (FI-10145)
Type:guid (Cascade Delete)
Remarks:Reference to Carrier Select Profile entry
2.3.43.2 pkid (FI-10144)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique identifier for the record
2.3.43.3 tkcarrierselectcode (FI-10146)
Type:enum
Default Value:0
Remarks:Reference to TypeCarrierSelectCode
2.3.43.4 value (FI-10147)
Type:long
Remarks:Reference to TypeCarrierSelectCode
Uniqueness:fkcarrierselectprofile + tkcarrierselectcode is unique. (MFI-771)

 
2.3.44 carrierselectprofile (TI-1084)
Description:CUBA: Profiles for different carriers
Is not replicated.
Fields:
2.3.44.1 description (FI-10143)
Type:string [200]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%&<>]{0,50}$
Migration Source:N/A
Remarks:Description for CS Profile.
2.3.44.2 name (FI-10142)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
Migration Source:N/A
Remarks:Unique name
2.3.44.3 pkid (FI-10141)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique identifier for the record
Uniqueness:No multicolumn uniqueness constraints

 
2.3.45 carrierselectprofiletrunkmap (TI-1086)
Description:CUBA: Mapping between Profile and Trunks
Is not replicated.
Fields:
2.3.45.1 fkcarrierselectprofile (FI-10149)
Type:guid (Cascade Delete)
Remarks:Reference to Carrier Select Profile entry
2.3.45.2 fkdevice (FI-10150)
Type:guid (Cascade Delete)
Remarks:indirect from DeviceName
2.3.45.3 pkid (FI-10148)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique identifier for the record
Uniqueness:fkcarrierselectprofile + fkdevice is unique. (MFI-772)

 
2.3.46 ccaprofile (TI-2583)
Description:This profile contains CCA-ID, Softswitch ID, Object Class field, Subscriber Type field, SIP Alias suffix, Sip User Name field suffix made configurable.
Fields:
2.3.46.1 ccaid (FI-25576)
Type:string [32] (Unique)
Validation:^[a-zA-Z 0-9.-]{1,32}$
Remarks:The LDAP server that stores the Directory Number Alias records uses this field to appropriately authorize subsequent updates of the records in the LDAP Database. The Directory Number Alias server will only allow update operations on a record originating from the CUCM cluster that originally added the record by identifying the CUCM Cluster Identifier set in this field.
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
2.3.46.2 ccaprofile_id (FI-25575)
Type:long (Unique, Indexed, Not Modifiable)
Remarks:Unique id to CCAProfile which would be use in numplan table
Rule (RI-2110):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Generate CCProfile ID value
Description:On insert of a new record generate a unique integer value and store the result in the CC_Profile ID field
Test Condition:On Insert
2.3.46.3 objectclass (FI-25578)
Type:string [32]
Validation:^[a-zA-Z 0-9.-]{0,32}$
Remarks:This field when configured specifies the object class in the LDAP Routing database to which the Directory Number record will belong to when the Directory Number is pushed by the DN Alias Sync server
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
2.3.46.4 pkid (FI-25574)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-2110):
Type:Active (Insert)
Rule Name:Generate CCProfile ID value
Description:On insert of a new record generate a unique integer value and store the result in the CC_Profile ID field
Test Condition:On Insert
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
2.3.46.5 primaryccasoftswitchid (FI-25577)
Type:string [32]
Validation:^[a-zA-Z 0-9.-]{1,32}$
Remarks:The LDAP server that stores the Directory Number Alias records uses this field to appropriately authorize subsequent updates of the records in the LDAP Database. The Directory Number Alias server will only allow update operations on a record originating from the CUCM Primary Soft Switch that originally added the record by identifying the CUCM Primary Soft Switch Identifier set in this field.
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
2.3.46.6 secondaryccasoftswitchid (FI-25596)
Type:string [32] (Null OK)
Validation:^[a-zA-Z 0-9.-]{0,32}$
Remarks:The LDAP server that stores the Directory Number Alias records uses this field to appropriately authorize subsequent updates of the records in the LDAP Database. The Directory Number Alias server will only allow update operations on a record originating from the CUCM Secondary Soft Switch that originally added the record by identifying the CUCM Secondary Soft Switch Identifier set in this field.
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
2.3.46.7 sipaliassuffix (FI-25580)
Type:string [32] (Null OK)
Validation:^[a-zA-Z 0-9.@-]{0,32}$
Remarks:This field when configured specifies the prefix that is added to the full Commericial number before it is stored in the SIP Alias field in the LDAP Routing database.
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
2.3.46.8 sipusernamesuffix (FI-25581)
Type:string [32] (Null OK)
Validation:^[a-zA-Z 0-9.@-]{0,32}$
Remarks:This field when configured specifies the prefix that is added to the User ID field before it is stored in the SIPuserName field in the LDAP Routing database.
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
2.3.46.9 subscribertype (FI-25579)
Type:string [32] (Null OK)
Validation:^[a-zA-Z 0-9.@-]{0,32}$
Remarks:This field when configured specifies the Subscriber Type in the LDAP Routing database of the Directory Number when the Directory Number is pushed by the DN Alias Sync server
Rule (RI-2111):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate USNs for CCAProfile
Description:Generate update sequence numbers for table CCAProfile.
Test Condition:On INSERT/UPDATE/DELETE on CCAProfile, generate USN as necessary.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.47 ccdadvertisingserviceprofile (TI-506)
Description:Call Control Discovery Advertising Profile for Call Manager
Fields:
2.3.47.1 fkccdhosteddngroup (FI-3837)
Type:guid (Unique)
Remarks:pkid of Hosted DN Group
Rule (RI-625):
Type:Validation (Insert/Update/Delete)
Rule Name:CCDHostedDNGroup can not be empty for CCD service
Description:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
Test Condition:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
Error Message:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
2.3.47.2 fkdevice_ict (FI-3828)
Type:guid (Null OK)
Default Value:NULL
Remarks:pkid of ICT Trunk
Rule (RFI-270):
Type:Inter-field Condition and Constraint
Test Condition:fkDevice_sip IS NULL
Constraint:fkDevice_ict IS NOT NULL
Remarks:Either SIP trunk or Intercluster trunk or both need to be configured
Rule (RI-600):
Type:Validation (Insert/Update)
Rule Name:Only SAF trunk can be assigned to CCD Service Profile
Description:Only SAF trunk can be assigned to CCD Service Profile
Test Condition:Only SAF Enabled ICT Trunk and CCD SIP Trunk can be added to CCD Service Profile
Error Message:Change ICT Trunk to be SAF Enable or change SIP Trunk Type to CCD before associated the trunk to CCD Service Profile
2.3.47.3 fkdevice_sip (FI-3827)
Type:guid (Null OK)
Default Value:NULL
Remarks:pkid of SIP Trunk
Rule (RI-600):
Type:Validation (Insert/Update)
Rule Name:Only SAF trunk can be assigned to CCD Service Profile
Description:Only SAF trunk can be assigned to CCD Service Profile
Test Condition:Only SAF Enabled ICT Trunk and CCD SIP Trunk can be added to CCD Service Profile
Error Message:Change ICT Trunk to be SAF Enable or change SIP Trunk Type to CCD before associated the trunk to CCD Service Profile
2.3.47.4 fksafservices (FI-3838)
Type:guid (Unique, Indexed, Cascade Delete)
Remarks:pkid of the row in the SAFServices Table
Rule (RI-611):
Type:Validation (Insert/Update)
Rule Name:Invalid SAF Service Type
Description:Invalid SAF Service Type
Test Condition:Invalid SAF Service Type
Error Message:Invalid SAF Service Type
2.3.47.5 pkid (FI-3829)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.47.6 resettoggle (FI-3840)
Type:bool
Default Value:FALSE
Remarks:Reset toggle CCD service
Uniqueness:No multicolumn uniqueness constraints

 
2.3.48 ccdhosteddn (TI-502)
Description:CCD Hosted DN Pattern
Fields:
2.3.48.1 description (FI-3846)
Type:string [512]
Default Value:EMPTY
Validation:^[^%&<>\\""""]{0,128}$
Remarks:Description of the Time Period, up to 128 characters including Unicode
2.3.48.2 fkccdhosteddngroup (FI-3849)
Type:guid (Cascade Delete)
Migration Source:pkid of DN group to which the pattern belongs
Rule (RI-625):
Type:Validation (Insert/Update/Delete)
Rule Name:CCDHostedDNGroup can not be empty for CCD service
Description:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
Test Condition:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
Error Message:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
2.3.48.3 hostedpattern (FI-3847)
Type:dn (Unique)
DN Type:DN_TYPE_ALL_DIGITS
Validation:^[]0-9A-D*#X[^+?!%\\-]{1,50}$
Migration Source:Hostedpattern
Remarks:This is the Dn to be advertized
Rule (RI-624):
Type:Validation (Insert/Update)
Rule Name:Invalid CCD Hosted Pattern
Description:Invalid CCD Hosted Pattern
Test Condition:Invalid CCD Hosted Pattern
Error Message:Invalid CCD Hosted Pattern
2.3.48.4 pkid (FI-3845)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-603):
Type:Validation (Insert)
Rule Name:10000 or less Hosted DN Patterns allowed
Description:Only 10000 or less Hosted DN Patterns allowed
Test Condition:the total number of records can not be greater than 10000 for Hosted DN Patterns
Error Message:Only 10000 or less Hosted DN Patterns allowed in the system
Rule (RI-625):
Type:Validation (Insert/Update/Delete)
Rule Name:CCDHostedDNGroup can not be empty for CCD service
Description:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
Test Condition:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
Error Message:CCD Hosted DN Group needs to associate with at least one Hosted DN if it is associated with CCD service
2.3.48.5 pstnfailoverprependdigits (FI-3848)
Type:string [16]
Default Value:EMPTY
Validation:^(\+)[0-9]{0,15}$|^[0-9]{0,16}$
Migration Source:PSTNfailover Prepend Digits
Remarks:This is a PSTN Failback Prepend Digites
2.3.48.6 pstnfailoverstripdigits (FI-3806)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(PSTNFailoverStripDigits >= 0) AND (PSTNFailoverStripDigits <= 16)
Remarks:PSTN Failover Strip Digits
2.3.48.7 usedforpstnfailover (FI-5170)
Type:bool
Default Value:FALSE
Remarks:Used existing hosted DN for PSTN failover
Uniqueness:No multicolumn uniqueness constraints

 
2.3.49 ccdhosteddngroup (TI-501)
Description:CCD Hosted DN Group
Fields:
2.3.49.1 description (FI-3843)
Type:string [512]
Default Value:EMPTY
Validation:^[^%&<>\\""""]{0,128}$
Remarks:Description is up to 128 characters including Unicode
2.3.49.2 name (FI-3842)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
Remarks:name of the Hosted DN group
2.3.49.3 pkid (FI-3841)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.49.4 pstnfailoverprependdigits (FI-3844)
Type:string [16]
Default Value:EMPTY
Validation:^(\+)[0-9]{0,15}$|^[0-9]{0,16}$
Migration Source:PSTNfailover Prepend Digits
Remarks:This is a PSTN Failback Prepend Digites
2.3.49.5 pstnfailoverstripdigits (FI-3805)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(PSTNFailoverStripDigits >= 0) AND (PSTNFailoverStripDigits <= 16)
Remarks:PSTN Failover Strip Digits
2.3.49.6 usedforpstnfailover (FI-5169)
Type:bool
Default Value:FALSE
Remarks:Used existing hosted DN for PSTN failover
Uniqueness:No multicolumn uniqueness constraints

 
2.3.50 ccdrequestingserviceprofile (TI-507)
Description:Call Control Discovery Receiving Profile for Call Manager
Fields:
2.3.50.1 fkroutepartition (FI-3833)
Type:guid (Null OK)
Remarks:pkid of Route Partition
Rule (RI-606):
Type:Validation (Insert/Update)
Rule Name:CCD Service Profile can only use learned pattern Route Partition
Description: CCD Service Profile can only use learned pattern Route Partition
Test Condition:CCD Service Profile can only use learned pattern Route Partition
Error Message:CCD Service Profile can not use Intercom Route Partition
2.3.50.2 fksafservices (FI-3808)
Type:guid (Unique, Indexed, Cascade Delete)
Remarks:pkid of the row in the SAFServices Table
Rule (RI-611):
Type:Validation (Insert/Update)
Rule Name:Invalid SAF Service Type
Description:Invalid SAF Service Type
Test Condition:Invalid SAF Service Type
Error Message:Invalid SAF Service Type
2.3.50.3 learnedpatternprefix (FI-5168)
Type:dn
DN Type:DN_TYPE_ALL_DIGITS
Default Value:EMPTY
Validation:^[0-9*#+]{0,24}$
Migration Source:LearnedPatternPrefix
Remarks:This is a Prefix
2.3.50.4 pkid (FI-3807)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.50.5 pstnprefix (FI-3835)
Type:dn
DN Type:DN_TYPE_ALL_DIGITS
Default Value:EMPTY
Validation:^[0-9*#+]{0,24}$
Migration Source:PSTNPrefix
Remarks:This is a Prefix
2.3.50.6 resettoggle (FI-3809)
Type:bool
Default Value:FALSE
Remarks:Reset toggle CCD service
Uniqueness:No multicolumn uniqueness constraints

 
2.3.51 cdrmconfig (TI-385)
Description:Similar to process config for CDR
Fields:
2.3.51.1 cdrcmrfiledeletiondisabled (FI-2886)
Type:bool
Default Value:FALSE
2.3.51.2 cdrrepmgrhostaddress (FI-3000)
Type:string [255]
Default Value:EMPTY
Remarks:CDR Repository Manager host IP address string in textual presentation
2.3.51.3 cdrrepmgrhostname (FI-2999)
Type:string [255]
Default Value:EMPTY
Remarks:CDR Repository Manager host name
2.3.51.4 diskallocation (FI-2860)
Type:long
Default Value:500
Check Constraint:((diskallocation >= 500) AND (diskallocation <= 3328))
Remarks:in Megabytes
2.3.51.5 highwatermark (FI-2861)
Type:long
Default Value:80
Check Constraint:((highwatermark >= 70) AND (highwatermark <= 90))
Remarks:percentage
2.3.51.6 lowwatermark (FI-2862)
Type:long
Default Value:40
Check Constraint:((lowwatermark >= 30) AND (lowwatermark <=50))
Remarks:percentage
2.3.51.7 pkid (FI-2856)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.51.8 windowsize (FI-2859)
Type:long
Default Value:30
Check Constraint:((windowsize >= 2) AND (windowsize <= 30))
Remarks:number of days of CDR files to preserve
Uniqueness:No multicolumn uniqueness constraints

 
2.3.52 certificate (TI-660)
Description:Certificate Information
Insert/Delete is not allowed.
Fields:
2.3.52.1 certificate (FI-5395)
Type:string [4096] (Not Modifiable)
Remarks:Certificate
2.3.52.2 ipv4address (FI-5396)
Type:string [15] (Not Modifiable)
Default Value:EMPTY
Remarks:IPv4Address
2.3.52.3 ipv6address (FI-5397)
Type:string [50] (Not Modifiable)
Default Value:EMPTY
Remarks:IPv6Address
2.3.52.4 issuername (FI-5393)
Type:string [255] (Not Modifiable)
Remarks:Name of issuer
2.3.52.5 pkid (FI-5390)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify Certificate record
Rule (RI-714):
Type:Active (Insert)
Rule Name:Insert into certificatehashmapdynamic for each record of hash
Description:On insert on certificatedynamic insert record in certificatehashmapdynamic for each hash
Test Condition:On insert on certificatedynamic
2.3.52.6 serialnumber (FI-5394)
Type:string [42] (Not Modifiable)
Remarks:hex representation of serial number
2.3.52.7 servername (FI-5391)
Type:string [255] (Not Modifiable)
Remarks:Name of the server
2.3.52.8 subjectname (FI-5392)
Type:string [255] (Not Modifiable)
Remarks:Name of subject
2.3.52.9 timetolive (FI-5398)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(TimeToLive >= 0)
2.3.52.10 tkcertificatedistribution (FI-25838)
Type:enum
Default Value:1
Remarks:Type of certificate.
Uniqueness:issuername + serialnumber is unique. (MFI-128)

 
2.3.53 certificatehashmap (TI-672)
Description:Certificate Hash Map
Insert/Delete is not allowed.
Fields:
2.3.53.1 fkcertificate (FI-5458)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:Reference to Certificate record
2.3.53.2 hash (FI-5460)
Type:string [256] (Null OK)
2.3.53.3 pkid (FI-5457)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify certificatehashmapdynamic record
2.3.53.4 tkhash (FI-5459)
Type:enum (Not Modifiable)
Default Value:1
Uniqueness:fkcertificate + tkhash is unique. (MFI-136)

 
2.3.54 certificateprocessnodemap (TI-670)
Description:Certifiacte Process Node Mapping
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.54.1 fkcertificate (FI-5682)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:References Certificate Record
2.3.54.2 fkprocessnode (FI-5683)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:associated processnode
2.3.54.3 ipv4address (FI-5685)
Type:string [15] (Not Modifiable)
Default Value:EMPTY
Remarks:IPv4Address
2.3.54.4 ipv6address (FI-5686)
Type:string [50] (Not Modifiable)
Default Value:EMPTY
Remarks:IPv6Address
2.3.54.5 pkid (FI-5681)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify CertificateProcessNodeMap record
2.3.54.6 servername (FI-5684)
Type:string [255] (Not Modifiable)
Remarks:Name of the server
Uniqueness:No multicolumn uniqueness constraints

 
2.3.55 certificateservicecertificatemap (TI-980)
Description:Maps each certificate service to its respective certificate
Fields:
2.3.55.1 fkcertificate (FI-5730)
Type:guid (Indexed, Cascade Delete)
Remarks:Pkid of the Certificate for the corresponding Certificate Service
2.3.55.2 pkid (FI-5729)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a CertificateServiceCertificateMap record
2.3.55.3 tkcertificateservice (FI-5731)
Type:enum
Remarks:The enum value of Certificate service defined in the TypeCertificateService table
Uniqueness:fkcertificate + tkcertificateservice is unique. (MFI-162)

 
2.3.56 certificatetrustrolemap (TI-661)
Description:Certifiacte Trust Role
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.56.1 fkcertificate (FI-5400)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:Reference to certificate
2.3.56.2 pkid (FI-5399)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify CertificateRoleMapDynamic record
2.3.56.3 tktrustrole (FI-5401)
Type:enum (Not Modifiable)
Remarks:Reference to typetrunstrole
Uniqueness:fkcertificate + tktrustrole is unique. (MFI-129)

 
2.3.57 cmcinfo (TI-304)
Description:Contains the authorization information for Client Meta Code
Fields:
2.3.57.1 code (FI-2127)
Type:string [16] (Unique, Indexed)
Validation:^[0-9]{1,16}$
Remarks:All Digits
2.3.57.2 description (FI-2126)
Type:string [200]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%\\&<>{}\[\]]{0,50}$
2.3.57.3 pkid (FI-2128)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.58 codeclist (TI-1104)
Description:This table documents the existence of a named, ordered list of the codecs supported by the system. Records marked as IsStandard are not eligible for user modification nor are their associated member lists eligible for user change.
Fields:
2.3.58.1 description (FI-10210)
Type:string [400]
Validation:^[^\x00-\x1F""%&<>]{0,100}$
Remarks:Localizable description of the Codec List.
2.3.58.2 isstandard (FI-10211)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:Indicates whether the Codec List is Standard or not. A Standard Codec List is not eligible for user modification nor its associated member lists eligible for a user change. Created during installation. 2 Standard Codec Lists - Lossy,Low-Loss.
2.3.58.3 name (FI-10209)
Type:string [50] (Unique, Indexed)
Validation:^[a-zA-Z 0-9._-]{1,50}$
Remarks:Name of the Codec List supported by the system. Records marked as isStandard are not eligible for user modification nor are their associated member lists eligible for a user change.
2.3.58.4 pkid (FI-10208)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.59 codeclistmember (TI-1105)
Description:This table records the ordered set of codecs for each defined CodecList. Records associated with a CodecList which is NOT IsStandard may be re-ordered.
Fields:
2.3.59.1 fkcodeclist (FI-10213)
Type:guid (Cascade Delete, Null OK)
Default Value:NULL
Remarks:Unique ID of the Codec List. Identifies the Codec to be a Lossy or Low-Loss Codec.
2.3.59.2 pkid (FI-10212)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.59.3 preferenceorder (FI-10215)
Type:long
Remarks:Determines the preference of Codec within a single Codec List. The same Codec in two different lists (Lossy and Low-Loss) can have different preference order in both the lists. The preference order can be changed by the user.
2.3.59.4 tkcodec (FI-10214)
Type:enum (Not Modifiable)
Remarks:Determines the type of Codec. Refers to the Codec supported by the system.
Uniqueness:fkcodeclist + tkcodec is unique. (MFI-773)

 
2.3.60 commondeviceconfig (TI-421)
Description:Used for DeviceMobility. Have user oriented fields.
Fields:
2.3.60.1 calreference (FI-21075)
Type:long
Default Value:-1
Remarks:user can assign confidential access level value to the group of devices
2.3.60.2 fkmlppdomain (FI-1955)
Type:guid (Null OK)
Default Value:NULL
Migration Source:mlppdomainid
Remarks:This is the MLPP domain associated with this profile. If this field is blank, this devices using this profile inherit the MLPP domain from the value set for the MLPP Domain Identifier enterprise parameter.
2.3.60.3 fksoftkeytemplate (FI-1128)
Type:guid (Null OK)
Default Value:NULL
Remarks:This is the softkey template that is associated with the devices using the profile.
2.3.60.4 holdpartynetworkholdmohaudiosourceid (FI-1000)
Type:long (Null OK)
Default Value:NULL
Remarks:This is the audio source to use for music on hold (MOH) when the network initiates a hold action.
2.3.60.5 holdpartyuserholdmohaudiosourceid (FI-999)
Type:long (Null OK)
Default Value:NULL
Remarks:This is the audio source to use for music on hold (MOH) when a user initiates a hold action.
2.3.60.6 name (FI-3229)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
2.3.60.7 pkid (FI-3228)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-346):
Type:Active (Insert/Update)
Rule Name:commondeviceconfig versionstamp
Description:on change to anything in commondeviceconfig table, update device versionstamp
Test Condition:update device
2.3.60.8 resettoggle (FI-3239)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-346):
Type:Active (Insert/Update)
Rule Name:commondeviceconfig versionstamp
Description:on change to anything in commondeviceconfig table, update device versionstamp
Test Condition:update device
2.3.60.9 tkcalmode (FI-21076)
Type:enum (Null OK)
Remarks:user can assign confidential access level mode to the group of devices
2.3.60.10 tkipaddressingmode (FI-3656)
Type:enum
Default Value:2
Remarks:Indicates the IPaddressingMode of device, ipv4, ipv6 or both type of IP addresses
2.3.60.11 tkipaddressingmodeprefcontrol (FI-3657)
Type:enum
Default Value:2
Remarks:Indicates what IP type device should connect to UCM if device has both IP's availab
2.3.60.12 tkpreemption (FI-1298)
Type:enum
Default Value:2
Remarks:This setting specifies whether devices using the profile and capable of preempting calls in progress will use the capability when the devices place an MLPP precedence call. Note : Do not configure a profile with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful.
2.3.60.13 tkreset (FI-3240)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
2.3.60.14 tkstatus_allowipv6autoconfigforphones (FI-3699)
Type:enum
Default Value:2
2.3.60.15 tkstatus_allowipv6duplicateaddressdetection (FI-25645)
Type:enum
Default Value:2
Remarks:Allow Duplicate Address Detection for CommonDeviceConfig.This parameter determines whether the duplicate address detection should be performed on each of the addresses in any identity associations(IAs) it receives in the Reply message before using that address for traffic.
2.3.60.16 tkstatus_ipv6acceptredirectmessages (FI-25646)
Type:enum
Default Value:2
Remarks:Accept Redirect Messages for CommonDeviceConfig.This parameter provides an ability to accept or ignore the redirect messages.
2.3.60.17 tkstatus_ipv6replymulticastechorequest (FI-25647)
Type:enum
Default Value:2
Remarks:Reply Multicast Echo Request for CommonDeviceConfig.This parameter allows the phone to enable or disable the ability to send an Echo Reply message in response to an Echo Request message sent to an IPv6 multicast or anycast address.
2.3.60.18 tkstatus_mlppindicationstatus (FI-1297)
Type:enum
Default Value:2
Remarks:This setting specifies whether devices using the profile and capable of playing precedence tones will use the capability when the devices place an MLPP precedence call. Null means uses enteprise value. Note : Do not configure a profile with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful.
2.3.60.19 tkstatus_viprenabled (FI-5247)
Type:enum
Default Value:2
Remarks:Is ViPR enabled on this device common config
2.3.60.20 tkuserlocale (FI-1036)
Type:enum (Null OK)
Default Value:NULL
Remarks:This is the locale that is associated with the phones and gateways using the profile. The user locale identifies a set of detailed information to support users, including language and font. Note : If this is null, the locale that is specified in the Cisco Unified CallManager clusterwide parameters as Default User Locale applies.
2.3.60.21 usetrustedrelaypoint (FI-3480)
Type:bool
Default Value:FALSE
Remarks:Indicates whether Trusted Relay Point should be used if available
2.3.60.22 versionstamp (FI-3230)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid plus seconds past midnight 1970 are concatenated
Rule (RI-346):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:commondeviceconfig versionstamp
Description:on change to anything in commondeviceconfig table, update device versionstamp
Test Condition:update device
Rule (RI-346):
Type:Active (Insert/Update)
Rule Name:commondeviceconfig versionstamp
Description:on change to anything in commondeviceconfig table, update device versionstamp
Test Condition:update device
Uniqueness:No multicolumn uniqueness constraints

 
2.3.61 commonphoneconfig (TI-384)
Description:Common Profile Information (only applies to SIP intially)
Fields:
2.3.61.1 description (FI-2984)
Type:string [512]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%\\&<>]{0,128}$
2.3.61.2 fkfeaturecontrolpolicy (FI-5716)
Type:guid (Null OK)
Default Value:NULL
Remarks:Feature Control Policy Record
2.3.61.3 fkvpngroup (FI-5441)
Type:guid (Null OK)
Default Value:NULL
Remarks:References VPNGroup Record Null allowed, null by default
2.3.61.4 fkvpnprofile (FI-5442)
Type:guid (Null OK)
Default Value:NULL
Remarks:References VPNProfile Record Null allowed, null by default
2.3.61.5 fkwifihotspotprofile (FI-25825)
Type:guid (Null OK)
Remarks:Reference to WiFi HotspotProfile.
2.3.61.6 isstandard (FI-2986)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:Whether it is standard
2.3.61.7 name (FI-2985)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
2.3.61.8 pkid (FI-2852)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-274):
Type:Active (Insert/Update)
Rule Name:commonphoneconfig versionstamp
Description:on change to anything in commonphoneconfig table, update device versionstamp
Test Condition:update device
Rule (RI-581):
Type:Active (Insert)
Rule Name:Insert XML Records for CommonPhoneConfig Table
Description:When a CommonPhoneConfig record is inserted, insert records for CommonPhoneConfigXML.
Test Condition:ON INSERT INTO CommonPhoneConfig
Rule (RI-947):
Type:Validation (Delete)
Rule Name:Cannot delete Standard Common Phone Profile
Description:Cannot delete Standard Common Phone Profile having pkid=ac243d17-98b4-4118-8feb-5ff2e1b781ac from CommonPhoneConfig
Test Condition:On Delete from CommonPhoneConfig AND IF pkid=ac243d17-98b4-4118-8feb-5ff2e1b781ac THEN THROW EXCEPTION
2.3.61.9 resettoggle (FI-3237)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-274):
Type:Active (Insert/Update)
Rule Name:commonphoneconfig versionstamp
Description:on change to anything in commonphoneconfig table, update device versionstamp
Test Condition:update device
2.3.61.10 sshpassword (FI-3755)
Type:string [200]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{0,200}$
Migration Source:SSH Password
Remarks:SSH Password
2.3.61.11 sshuserid (FI-3756)
Type:string [50]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{0,50}$
Migration Source:SSH UserID
2.3.61.12 tkdndoption (FI-3284)
Type:enum
Default Value:0
Remarks:Type of call handling while DND is enabled (0=Ringer Off, 1=Call Reject); depends on product support
2.3.61.13 tkphonepersonalization (FI-3457)
Type:enum
Default Value:3
2.3.61.14 tkphoneservicedisplay (FI-3627)
Type:enum
Default Value:3
Remarks:Identifies which services are displayed for a button (services, directories, messages): Internal, External, Both, or Default (use Enterprise Parameter value)
2.3.61.15 tkreset (FI-3238)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
2.3.61.16 tkringsetting_dnd (FI-3285)
Type:enum
Default Value:5
Check Constraint:((tkRingSetting_DND = 1) OR (tkRingSetting_DND = 2) OR (tkRingSetting_DND = 5))
2.3.61.17 tkstatus_alwaysuseprimeline (FI-3706)
Type:enum
Default Value:2
Remarks:Determines off-hook behavior of phones with active calls present
2.3.61.18 tkstatus_alwaysuseprimelineforvm (FI-3707)
Type:enum
Default Value:2
Remarks:Determines Voice Message retreival behavior of phones
2.3.61.19 versionstamp (FI-3114)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid plus seconds past midnight 1970 are concatenated
Rule (RI-274):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:commonphoneconfig versionstamp
Description:on change to anything in commonphoneconfig table, update device versionstamp
Test Condition:update device
Rule (RI-274):
Type:Active (Insert/Update)
Rule Name:commonphoneconfig versionstamp
Description:on change to anything in commonphoneconfig table, update device versionstamp
Test Condition:update device
2.3.61.20 zzbackgroundimageaccess (FI-2806)
Type:bool
Default Value:TRUE
Remarks:is background Image Access Enabled
2.3.61.21 zzunlockpassword (FI-2821)
Type:string [15]
Default Value:EMPTY
Remarks:unlock password
Uniqueness:No multicolumn uniqueness constraints

 
2.3.62 commonphoneconfigxml (TI-550)
Description:XML configuration for Common Phone Config
Insert/Delete is not allowed.
Fields:
2.3.62.1 fkcommonphoneconfig (FI-3751)
Type:guid (Unique, Indexed, Cascade Delete)
Rule (RI-591):
Type:Active (Update)
Rule Name:Update CommonPhoneConfig.XML for CommonPhoneConfigXML change
Description:When CommonPhoneConfigXML.XML changed, the CommonPhoneConfig is updated.
Test Condition:ON UPDATE IN CommonPhoneConfigXML: THEN UPDATE CommonPhoneConfig SET versionstamp = versionstampgenerator() where pkid = fkCommonPhoneConfig; END IF;
2.3.62.2 pkid (FI-3750)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.62.3 xml (FI-3752)
Type:string [16000] (Null OK)
Default Value:NULL
Remarks:Product configuration XML not used by CCM
Rule (RI-591):
Type:Active (Update)
Rule Name:Update CommonPhoneConfig.XML for CommonPhoneConfigXML change
Description:When CommonPhoneConfigXML.XML changed, the CommonPhoneConfig is updated.
Test Condition:ON UPDATE IN CommonPhoneConfigXML: THEN UPDATE CommonPhoneConfig SET versionstamp = versionstampgenerator() where pkid = fkCommonPhoneConfig; END IF;
Uniqueness:No multicolumn uniqueness constraints

 
2.3.63 componentversion (TI-368)
Description:RPM versions of components
Fields:
2.3.63.1 fkprocessnode (FI-2716)
Type:guid (Indexed, Cascade Delete)
2.3.63.2 installationcomponent (FI-2717)
Type:string [100]
2.3.63.3 pkid (FI-2715)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.63.4 softwarecomponent (FI-2718)
Type:string [100]
2.3.63.5 version (FI-2719)
Type:string [100]
Uniqueness:No multicolumn uniqueness constraints

 
2.3.64 confidentialaccesslevel (TI-2113)
Description:Access level and Text selection
Fields:
2.3.64.1 enum (FI-21045)
Type:enum (Unique, Indexed)
Remarks:unique identifier for ConfidentialaccessLevel
2.3.64.2 name (FI-21046)
Type:string [16]
Validation:^[]a-zA-Z0-9 !@#$%^&*()_+/=[{}-]{1,16}$
Remarks:Unique name given to this specific Confidential Access Level
Uniqueness:No multicolumn uniqueness constraints

 
2.3.65 confidentialaccesslevelmatrix (TI-2114)
Description:Selection Resultant based upon incoming and outgoing CAL level
Fields:
2.3.65.1 confidentialaccesslevel_in (FI-21048)
Type:enum
Remarks:Incoming confidential access level which would be assigned to device or trunk or line
2.3.65.2 confidentialaccesslevel_out (FI-21049)
Type:enum
Remarks:Outgoing confidential access level which would be assigned to device or trunk or line
2.3.65.3 confidentialaccesslevel_result (FI-21050)
Type:enum
Remarks:Resolved confidential access level from the incoming and outgoing confidential access level
2.3.65.4 enum (FI-21047)
Type:enum (Unique, Indexed)
Remarks:unique identifier for Records of the confidential access level matrix
Uniqueness:No multicolumn uniqueness constraints

 
2.3.66 corsdomain (TI-2623)
Description:Cross-Origin Resource Sharing (CORS)
Fields:
2.3.66.1 description (FI-25845)
Type:string [255]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%\\&<>]{0,50}$
Remarks:Description of the CORS Domain.
2.3.66.2 isfullaccess (FI-25846)
Type:bool
Default Value:FALSE
Remarks:If true then is full access, else read only
2.3.66.3 name (FI-25844)
Type:string [255] (Unique)
Remarks:Specifies the Domain for Cross-Origin Resource Sharing (CORS)
Rule (RI-2160):
Type:Validation (Insert/Update)
Rule Name:CORS Domain field validation
Description:CORS Domain must start with 'http://' or 'https://' and then be followed by a valid FQDN whereas, '*' must not be followed by a valid FQDN. All characters are allowed in FQDN except close angle bracket (>),open angle bracket (<),equal (=),space ( ).
Test Condition:On insert/update of CORSDomain
2.3.66.4 pkid (FI-25843)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.67 credential (TI-446)
Description:Authentication information and policies for App and End Users
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.67.1 cantchange (FI-3349)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:A flag indicating whether the user can set this credential.
2.3.67.2 credentials (FI-3358)
Type:string [288] (Not Modifiable, Null OK)
Default Value:NULL
Migration Source:Binary in CUC; encrypted string App/EndUser.password or PIN
Remarks:The PIN or password, for a user. The credentials are stored in an encrypted format.
2.3.67.3 credmustchange (FI-3350)
Type:bool (Not Modifiable)
Default Value:TRUE
Remarks:A flag indicating whether the user must change their credentials (PIN or password) at the next login.
2.3.67.4 doesntexpire (FI-3352)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:A flag indicating whether this user credential will expire, and therefore the user must change the credential periodically. However, if the credential does not expire (value = "1"), the user still may change the credential (if allowed by CantChange).
2.3.67.5 fkapplicationuser (FI-3347)
Type:guid (Cascade Delete, Not Modifiable, Null OK)
Default Value:NULL
Remarks:The unique identifier of the Application User to which this credential belongs.
Rule (RI-399):
Type:Active (Insert)
Rule Name:Insert Dynamic Records for Credentials
Description:When a credential record gets inserted, create the corresponding record in the CredentialDynamic table
Test Condition:ON INSERT INTO Credential: INSERT INTO CredentialDynamic (pkid, fkCredential) values (newid(), new_pkid)
2.3.67.6 fkcredentialpolicy (FI-3351)
Type:guid (Not Modifiable)
Default Value:9454babf-48d0-4e16-9b80-2d0da4b38750
Remarks:The unique identifier of the CredentialPolicy that is associated with this credential.
2.3.67.7 fkenduser (FI-3346)
Type:guid (Cascade Delete, Not Modifiable, Null OK)
Default Value:NULL
Remarks:The unique identifier of the End User to which this credential belongs.
2.3.67.8 imsinfo (FI-3359)
Type:long (Not Modifiable)
Default Value:0
Remarks:Information used by IMS to encrypt data
2.3.67.9 pkid (FI-3345)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-399):
Type:Active (Insert)
Rule Name:Insert Dynamic Records for Credentials
Description:When a credential record gets inserted, create the corresponding record in the CredentialDynamic table
Test Condition:ON INSERT INTO Credential: INSERT INTO CredentialDynamic (pkid, fkCredential) values (newid(), new_pkid)
2.3.67.10 timeadminlockout (FI-3357)
Type:long (Not Modifiable, Null OK)
Default Value:NULL
Remarks:The date and time that the credential was locked by an administrator.
2.3.67.11 timechanged (FI-3354)
Type:long (Not Modifiable)
Remarks:The date and time when the credentials were last changed. The date and time is recorded in this column whenever a user credential is created or changed.
2.3.67.12 tkcredential (FI-3348)
Type:enum (Not Modifiable)
Default Value:4
Remarks:The type of credential such as password, PIN, Windows or Domino credential.
Uniqueness:fkapplicationuser + fkenduser + tkcredential is unique. (MFI-103)

 
2.3.68 credentialdynamic (TI-458)
Description:Frequently updated settings for Credentials
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.68.1 datetimestamp (FI-3432)
Type:long (Not Modifiable)
Default Value:0
Remarks:Time value for last change (for replication conflict resolution)
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.68.2 fkcredential (FI-3431)
Type:guid (Unique, Cascade Delete, Not Modifiable)
Remarks:Parent record for which this record holds the dynamic settings
2.3.68.3 hackcount (FI-3353)
Type:long (Not Modifiable)
Default Value:0
Remarks:The number of logons attempted that failed due to invalid credentials. The Unity system or external authentication provider determined that the credentials supplied as part of a user logon attempt were invalid.
Rule (RI-2181):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of CredentialDynamic
Description:On Insert/Update of CredentialDynamic values of LastsuccessfulLogintime and hackcount needs to be copied to new columns
Test Condition:ON INSERT/UPDATE INTO CredentialDynamic:SELECT hackcount INTO new_hackcount FROM CredentialDynamic;
2.3.68.4 lastsuccessfulloginip (FI-25959)
Type:string [255] (Not Modifiable, Null OK)
Default Value:NULL
Validation:^[0-9a-zA-Z.:_-]{0,255}$
Remarks:Last successful login IP address
2.3.68.5 lastsuccessfullogintime (FI-3799)
Type:long (Not Modifiable)
Default Value:0
Remarks:Time value for the last successful login reported by IMS
Rule (RI-2181):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of CredentialDynamic
Description:On Insert/Update of CredentialDynamic values of LastsuccessfulLogintime and hackcount needs to be copied to new columns
Test Condition:ON INSERT/UPDATE INTO CredentialDynamic:SELECT hackcount INTO new_hackcount FROM CredentialDynamic;
2.3.68.6 lastunsuccessfulloginip (FI-25960)
Type:string [255] (Not Modifiable, Null OK)
Default Value:NULL
Validation:^[0-9a-zA-Z.:_-]{0,255}$
Remarks:Last un-successful login IP address
2.3.68.7 pkid (FI-3430)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.68.8 previoushackcount (FI-26776)
Type:long (Not Modifiable)
Default Value:0
Remarks:The number of logons attempted that failed due to invalid credentials
Rule (RI-2181):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of CredentialDynamic
Description:On Insert/Update of CredentialDynamic values of LastsuccessfulLogintime and hackcount needs to be copied to new columns
Test Condition:ON INSERT/UPDATE INTO CredentialDynamic:SELECT hackcount INTO new_hackcount FROM CredentialDynamic;
Rule (RI-2181):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:On Active Insert/Update of CredentialDynamic
Description:On Insert/Update of CredentialDynamic values of LastsuccessfulLogintime and hackcount needs to be copied to new columns
Test Condition:ON INSERT/UPDATE INTO CredentialDynamic:SELECT hackcount INTO new_hackcount FROM CredentialDynamic;
2.3.68.9 prevlastsuccessfullogintime (FI-26777)
Type:long (Not Modifiable)
Default Value:0
Remarks:Time value for the previous last successful login reported by IMS
Rule (RI-2181):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of CredentialDynamic
Description:On Insert/Update of CredentialDynamic values of LastsuccessfulLogintime and hackcount needs to be copied to new columns
Test Condition:ON INSERT/UPDATE INTO CredentialDynamic:SELECT hackcount INTO new_hackcount FROM CredentialDynamic;
Rule (RI-2181):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:On Active Insert/Update of CredentialDynamic
Description:On Insert/Update of CredentialDynamic values of LastsuccessfulLogintime and hackcount needs to be copied to new columns
Test Condition:ON INSERT/UPDATE INTO CredentialDynamic:SELECT hackcount INTO new_hackcount FROM CredentialDynamic;
2.3.68.10 timehackedlockout (FI-3355)
Type:long (Not Modifiable, Null OK)
Default Value:NULL
Remarks:The date and time that the credential was locked due to too many hacks. The date and time is recorded in this column whenever a user credential is locked due to too many hacks based on the credential policy.
2.3.68.11 timelastaccessed (FI-3428)
Type:long (Not Modifiable, Null OK)
Default Value:0
Remarks:Time value for the last access of the credential (create, read or update)
2.3.68.12 timelasthacked (FI-3356)
Type:long (Not Modifiable, Null OK)
Default Value:NULL
Remarks:The date and time of the last logon attempt with an invalid user credential.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.69 credentialhistory (TI-448)
Description:Stores past credentials for enforcement of password history restrictions (non-reuse)
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.69.1 changeid (FI-3371)
Type:long
Remarks:A historical index of credential changes. Allows the fetching of the last 'n' credentials, if desired.
2.3.69.2 credentials (FI-3375)
Type:string [288]
Remarks:The credential, e.g., PIN or password created by this change. Credentials can be an encoded PIN or password.
2.3.69.3 fkapplicationuser (FI-3373)
Type:guid (Cascade Delete, Null OK)
Remarks:The unique identifier of the ApplicationUser object for which this credential change occurred.
2.3.69.4 fkenduser (FI-3372)
Type:guid (Cascade Delete, Null OK)
Remarks:The unique identifier of the EndUser object for which this credential change occurred.
2.3.69.5 pkid (FI-3370)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.69.6 timechanged (FI-3376)
Type:long
Remarks:The date and time the credential was created or changed.
2.3.69.7 tkcredential (FI-3374)
Type:enum
Remarks:The type of credential such as a password or PIN.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.70 credentialpolicy (TI-447)
Description:Settings for enforcement of credential policy (password strength, expiration, etc.)
Fields:
2.3.70.1 displayname (FI-3361)
Type:string [255] (Unique)
Validation:^[^\x00-\x1F\x7F""""]{1,64}$
Remarks:The unique text name (e.g., "Administrator Password Policy") of the credential policy to be used when displaying entries in the administrative console, e.g. Cisco Unified CallManager Administration
2.3.70.2 expirywarningdays (FI-3423)
Type:long
Default Value:0
Check Constraint:(ExpiryWarningDays >=0) AND (ExpiryWarningDays <= 90)
Remarks:Number of days prior to Credential Expiring that warning message should be presented to the user. A value of 0 means no warning is given.
2.3.70.3 hackresettime (FI-3362)
Type:long
Default Value:30
Check Constraint:(HackResetTime >= 1) AND (HackResetTime <= 120)
Remarks:The length of time (in minutes) after which if no failed logon attempts occur, the count of failed logon attempts is cleared
2.3.70.4 isstandard (FI-3424)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:Indicates installed standard Credential Policy - cannot be modified or deleted
Rule (RI-396):
Type:Active (Update/Delete)
Rule Name:Cannot modify or delete Standard Credential Policy
Description:The installed standard Credential Policy cannot be modified or deleted (even using IMS). It is not necessary to use this policy if more secure policies exist, and the policy is maintained for backward compatibility only. The installed policy is the only policy where IsStandard is true.
Test Condition:ON UPDATE/DELETE IN CredentialPolicy: IF (old_IsStandard = 'T') THEN throw exception;
Error Message:Cannot modify or delete the installed standard Credential Policy.
Remedy:Create and assign more secure Credential Policies for passwords and PINs.
2.3.70.5 lockoutduration (FI-3363)
Type:long
Default Value:30
Check Constraint:(LockoutDuration >= 0) AND (LockoutDuration <= 1440)
Remarks:The length of time (in minutes) that a user who is locked out must wait until they can attempt to access the system again with this credential. A value of "0" means the user is locked out until the credential/account is unlocked by an administrator.
2.3.70.6 maxdays (FI-3364)
Type:long
Default Value:180
Check Constraint:(MaxDays >= 0) AND (MaxDays <= 365)
Remarks:The maximum number of days before the credential must be changed. A value of "0" means the credential will never expire.
2.3.70.7 maxhacks (FI-3365)
Type:long
Default Value:3
Check Constraint:(MaxHacks >= 0) AND (MaxHacks <= 100)
Remarks:The maximum number of failed logon attempts (hacks) before action is taken. A value of "0" means an unlimited number of logon attempts (i.e., no lockout) are allowed.
2.3.70.8 maxinactivedays (FI-3429)
Type:long
Default Value:0
Check Constraint:(MaxInactiveDays >= 0) AND (MaxInactiveDays <= 5000)
Remarks:The number of days after which a credential is disabled if not used. A value of 0 means the credential is never disabled because of inactivity
2.3.70.9 minduration (FI-3366)
Type:long
Default Value:0
Check Constraint:(MinDuration >= 0) AND (MinDuration <= 129600)
Remarks:The minimum number of minutes that must pass from the time of the last change before the credential can be changed. A value of "0" means that there are no restrictions on how often the user can change the credential.
2.3.70.10 minlength (FI-3367)
Type:long
Default Value:8
Check Constraint:(MinLength >= 1) AND (MinLength <= 64)
Remarks:The minimum number of characters or digits (PIN) required for the credential.
2.3.70.11 pkid (FI-3360)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.70.12 prevcredcount (FI-3368)
Type:long
Default Value:12
Check Constraint:(PrevCredCount >= 0) AND (PrevCredCount <= 25)
Remarks:The number of credentials to store. A value of "0" means that a new credential is not compared with previous credentials; thus a user can reuse a credential.
2.3.70.13 trivialcredchecking (FI-3369)
Type:bool
Default Value:TRUE
Remarks:A flag indicating whether to check against trivial credentials for extra security; True = check to make sure credentials are not trivial; False = do not check for trivial credentials (check length and valid characters only)
Uniqueness:No multicolumn uniqueness constraints
Constraints:
Rule (RFI-162):
Type:Inter-field Condition and Constraint
Constraint:( (MaxDays > 0) AND ( MaxDays*60*24 >= MinDuration) ) OR (MaxDays =0)
Remarks:Minimum Duration Between Credential Changes should be shorter that Credential Expires After days

 
2.3.71 credentialpolicydefault (TI-459)
Description:Specifies the default CredentialPolicy for each combination of user and credential type
Insert/Delete is not allowed.
Fields:
2.3.71.1 cantchange (FI-3472)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:A flag indicating whether the user can set this credential.
2.3.71.2 credentials (FI-3447)
Type:string [288] (Not Modifiable, Null OK)
Default Value:NULL
Remarks:The default PIN or password for new credentials. The credentials are stored in an encrypted format.
2.3.71.3 credmustchange (FI-3473)
Type:bool (Not Modifiable)
Default Value:TRUE
Remarks:A flag indicating whether the user must change their credentials (PIN or password) at the next login.
2.3.71.4 doesntexpire (FI-3474)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:A flag indicating whether this user credential will expire, and therefore the user must change the credential periodically. However, if the credential does not expire (value = "1"), the user still may change the credential (if allowed by CantChange).
2.3.71.5 fkcredentialpolicy (FI-3437)
Type:guid
Remarks:The default Credential Policy for new credentials of the specificed type (credential and user)
2.3.71.6 imsinfo (FI-3448)
Type:long (Not Modifiable)
Default Value:0
Remarks:Default Information used by IMS to encrypt data
2.3.71.7 pkid (FI-3436)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.71.8 tkcredential (FI-3438)
Type:enum (Not Modifiable)
Remarks:Used in combination with type of Credential User to establish a default
2.3.71.9 tkcredentialuser (FI-3439)
Type:enum (Not Modifiable)
Remarks:Used in combination with type of Credential to establish a default
Uniqueness:No multicolumn uniqueness constraints

 
2.3.72 crsapplication (TI-248)
Description:Application specific data for CRS
Fields:
2.3.72.1 aakeypadmapping (FI-1689)
Type:string [129]
Default Value:EMPTY
Remarks:The mapping of aapromptname to numbers only
Rule (RI-291):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Map name to keypad
Description:On I/U, take map alpha chars to keypad, abc=2, def=3, etc.
Test Condition:on insert/update of aapromptname
Error Message:Only keys mapping to 0 to 9 allowed
Rule (RI-291):
Type:Active (Insert/Update)
Rule Name:Map name to keypad
Description:On I/U, take map alpha chars to keypad, abc=2, def=3, etc.
Test Condition:on insert/update of aapromptname
Error Message:Only keys mapping to 0 to 9 allowed
2.3.72.2 aapromptname (FI-1690)
Type:string [129]
Default Value:EMPTY
Remarks:The letter representation of the search name using IVR
Rule (RI-291):
Type:Active (Insert/Update)
Rule Name:Map name to keypad
Description:On I/U, take map alpha chars to keypad, abc=2, def=3, etc.
Test Condition:on insert/update of aapromptname
Error Message:Only keys mapping to 0 to 9 allowed
2.3.72.3 fkenduser (FI-1688)
Type:guid (Cascade Delete)
2.3.72.4 fnamealtpronun (FI-2896)
Type:string [1024]
Default Value:EMPTY
Remarks:First Name Alternate Pronunciations delimited by a seperator
2.3.72.5 lnamealtpronun (FI-2897)
Type:string [1024]
Default Value:EMPTY
Remarks:Last Name Alternate Pronunciations delimited by a seperator
2.3.72.6 pkid (FI-1687)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.73 crsuserclusterspecific (TI-410)
Description:Stores user information for the CRS Application
Fields:
2.3.73.1 administratorlevel (FI-2898)
Type:long
Default Value:0
Remarks:Whether an Administrator
2.3.73.2 clustername (FI-3047)
Type:string [60]
2.3.73.3 fkenduser (FI-3046)
Type:guid (Cascade Delete)
2.3.73.4 issupervisor (FI-2899)
Type:bool
Default Value:FALSE
Remarks:Whether a Supervisor
2.3.73.5 pkid (FI-3045)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:fkenduser + clustername is unique. (MFI-94)

 
2.3.74 cubacountryregionalinfo (TI-1053)
Description:CUBA: Table to store Country Regional Packs on Cuba platform.
Is not replicated. Records may be modified only by installation and/or DB triggers.
Fields:
2.3.74.1 pkid (FI-9917)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique identifier for the record
2.3.74.2 tkcountry (FI-9918)
Type:enum (Unique, Indexed, Not Modifiable)
Remarks:Country id from typecountry table.
2.3.74.3 xml (FI-9919)
Type:string [32000] (Not Modifiable)
Remarks:Ring Tones and Other Region Specific Product configuration XML not used by CCM
Uniqueness:No multicolumn uniqueness constraints

 
2.3.75 cubaproductsupport (TI-597)
Description:CUBA:CubaProductSupport table to store the models that are supported in Pajaro system
Is not replicated. Records may be modified only by installation and/or DB triggers.
Fields:
2.3.75.1 displayname (FI-9923)
Type:string [100] (Not Modifiable, Null OK)
Default Value:NULL
2.3.75.2 enum (FI-6142)
Type:enum (Unique, Indexed, Not Modifiable)
Remarks:A number to identify the record
2.3.75.3 tkcubaproductdisplaygroup (FI-9924)
Type:enum (Not Modifiable)
Default Value:2
Remarks:A number to identify the record
2.3.75.4 tkdeviceprotocol (FI-6145)
Type:enum (Not Modifiable)
Default Value:99
Remarks:Enum of Device Protocol record
2.3.75.5 tkmodel (FI-6144)
Type:enum (Not Modifiable)
2.3.75.6 tkproduct (FI-6143)
Type:enum (Not Modifiable)
Uniqueness:No multicolumn uniqueness constraints

 
2.3.76 customannouncement (TI-617)
Description:subset of TypeAnnouncement with rows having AllowCustom = 1
Fields:
2.3.76.1 description (FI-6270)
Type:string [1024] (Null OK)
Validation:^[^""%&\\<>:]{0,255}$
Remarks:Description of the custom announcements
2.3.76.2 issystem (FI-6271)
Type:bool
Default Value:FALSE
Remarks:isSystem is an internal control for ipvms install to pre-configure some CustomAnnouncement entries with UI restriction (user cannot edit some fields). Records which have initial contents may be altered by the administrator, but may not be removed.
2.3.76.3 name (FI-5138)
Type:string [50] (Unique)
Validation:^[]a-zA-Z0-9 !#$&'()*+,./:;<=>?@[^_{|}~\\-]{0,50}$
2.3.76.4 pkid (FI-5137)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.76.5 tkannouncementfile (FI-5140)
Type:enum (Indexed, Null OK)
Default Value:NULL
Remarks:A number to identify the record
2.3.76.6 tkannouncements (FI-5139)
Type:enum (Unique, Indexed)
Remarks:A number to identify the record
Uniqueness:No multicolumn uniqueness constraints

 
2.3.77 customannouncementlocale (TI-618)
Description:null
Fields:
2.3.77.1 description (FI-5147)
Type:string [255]
Validation:^[]a-zA-Z0-9 !#$&'()*+,./:;<=>?@[^_{|}~\\-]{0,255}$
2.3.77.2 filename (FI-5142)
Type:string [128]
Validation:^[a-zA-Z 0-9._-]{1,128}$
2.3.77.3 fkcustomannouncement (FI-5143)
Type:guid
Migration Source:reference to CustomAnnouncement
2.3.77.4 highsourcefiledatetime (FI-5145)
Type:long
2.3.77.5 isenabled (FI-5148)
Type:bool
Default Value:TRUE
2.3.77.6 lowsourcefiledatetime (FI-5146)
Type:long
2.3.77.7 pkid (FI-5141)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.77.8 tkuserlocale (FI-5144)
Type:enum (Indexed)
Remarks:reference to TypeUserLocale
Uniqueness:fkcustomannouncement + tkuserlocale is unique. (MFI-126)

 
2.3.78 customuserattributedata (TI-545)
Description:Stores data to be syncronized to respective Custom Field Attribute. Each Record is associated to an End User and mapped to each supported TypeCustomUserAttributes
Fields:
2.3.78.1 fkenduser (FI-10012)
Type:guid (Indexed, Cascade Delete, Not Modifiable)
Remarks:Key Reference to the User to whom the data in the Value column applies.
2.3.78.2 pkid (FI-10010)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.78.3 tkcustomuserattribute (FI-10011)
Type:enum (Not Modifiable)
Remarks:This field is to map one of the 5 available custom field to the Data in CustomUserAttributeName table.
2.3.78.4 value (FI-10013)
Type:string [255] (Null OK)
Remarks:Data retrieved from LDAP for the specified Custom Attribute for the user associated with this record.
Uniqueness:tkcustomuserattribute + fkenduser is unique. (MFI-203)

 
2.3.79 customuserattributename (TI-544)
Description:Records in this table contain Configurable friendly names to all the Custom Field attributes defined in TypeCustomUserAttributes
Fields:
2.3.79.1 customfieldattributename (FI-10008)
Type:string [256] (Unique)
Validation:^[a-zA-Z 0-9]{1,64}$
Remarks:CustomFieldAttributeName field stores the name of the attribute during LDAP syncronization of EndUsers.
2.3.79.2 pkid (FI-10007)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.79.3 tkcustomuserattribute (FI-10009)
Type:enum (Unique, Not Modifiable)
Remarks:This field is to map one of the 5 available custom field to the Name in CustomUserAttributeName table.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.80 datetimesetting (TI-10)
Description:Common/shared date time zone and format settings
Fields:
2.3.80.1 datetemplate (FI-154)
Type:string [6]
Default Value:M-D-Y
Validation:^(M-D-Y|M/D/Y|M\.D\.Y|D-M-Y|D/M/Y|D\.M\.Y|Y-M-D|Y/M/D|Y\.M\.D)A?$
Migration Source:DateTimeGroup.DateTemplate
Remarks:Template to be used to display date on an IP Phone. If the last character is 'A' then it is 24 hour time. Otherwise, it is 12 hour time.
2.3.80.2 name (FI-153)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
Migration Source:DateTimeGroup.GroupName
Remarks:A descriptive name for the Date/Time group.
2.3.80.3 pkid (FI-152)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
2.3.80.4 resettoggle (FI-3135)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
2.3.80.5 tkreset (FI-3071)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
2.3.80.6 tktimezone (FI-155)
Type:enum
Default Value:21
Migration Source:DateTimeGroup.TimeZone
Remarks:Time zone for the CallManager group. The option "local time zone of CallManager" copies the time zone information from the operating system of the server where Cisco CallManager is installed.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.81 defaults (TI-11)
Description:CallManager specific default attributes for devices
Insert/Delete is not allowed.
Fields:
2.3.81.1 fkdevicepool (FI-240)
Type:guid (Null OK)
Default Value:NULL
Migration Source:convert from DevicePoolID
Remarks:Device pool that is associated with each type of device. The device pool defines common characteristics for all devices in the pool.
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
2.3.81.2 fkphonetemplate (FI-241)
Type:guid (Null OK)
Default Value:NULL
Migration Source:convert from PhoneTemplateID
Remarks:This is the phone template to assign to a device that auto-registers. It must be usable on the specified model.
Rule (RI-16):
Type:Validation (Insert/Update)
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-17):
Type:Validation (Insert/Update)
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
2.3.81.3 inactiveloadinformation (FI-242)
Type:string [50]
Default Value:EMPTY
Remarks:The filename of the inactive firmware load that is used with phone models that support dual-bank firmware (background download). The file is fed to the phones via TFTP but is not active. This can be overridden at the device level. If not overridden, then all devices of this model will download this firmware load file as the inactive load.
2.3.81.4 loadinformation (FI-239)
Type:string [50]
Default Value:EMPTY
Migration Source:Load_
Remarks:The filename of the firmware load that is used with a particular type of hardware device model. The file is fed to the phones via TFTP. This can be overridden at the device level. If not overridden, then all devices of this model will use this firmware load file.
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
2.3.81.5 pkid (FI-237)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
2.3.81.6 resettoggle (FI-3090)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
2.3.81.7 tkdeviceprotocol (FI-2359)
Type:enum
Default Value:99
Remarks:Default value for Device Protocol
Rule (RI-16):
Type:Validation (Insert/Update)
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-17):
Type:Validation (Insert/Update)
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
2.3.81.8 tkmodel (FI-238)
Type:enum (Not Modifiable)
Migration Source:convert from Type and HardwareType
Remarks:A defaults record must exist for every IP Phone.
Rule (RI-16):
Type:Validation (Insert/Update)
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-17):
Type:Validation (Insert/Update)
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
2.3.81.9 tkreset (FI-3091)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
2.3.81.10 versionstamp (FI-3115)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid plus seconds past midnight 1970 are concatenated
Rule (RI-283):
Type:Active (Update)
This field is modified by this rule.
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
Rule (RI-283):
Type:Active (Update)
Rule Name:defaults versionstamp
Description:on change to loadinfo in defaults table, update device versionstamp
Test Condition:update device
Uniqueness:tkmodel + tkdeviceprotocol is unique. (MFI-81)

 
2.3.82 defaultucuserprofile (TI-2611)
Description:Indicates which UCUserProfile record is the System Default if left unspecified where needed.
Insert/Delete is not allowed.
Fields:
2.3.82.1 fkucuserprofile (FI-25757)
Type:guid
Remarks:Defines which UCUserProfile should be used when one is required but left unspecified.
2.3.82.2 pkid (FI-25756)
Type:guid (Unique, Indexed, Not Modifiable)
Migration Source:Generated
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.83 destinationcodecontrol (TI-971)
Description:Allows configuration of outbound traffic throttling for a specific dialing plan destination, (Route Pattern), in accordance with DOD UCR 2008 specifications related to Destination Code Control, (DCC).
Fields:
2.3.83.1 blockedcallpercentage (FI-9834)
Type:long (Null OK)
Default Value:0
Check Constraint:(BlockedCallPercentage >= 0) AND (BlockedCallPercentage <= 100)
Remarks:This value specifies the percentage of lower precedence calls made to this destination that get blocked by the route pattern. This percentage limits the lower precedence calls only, the flash and higher precedence calls made to this destination are allowed at all times.
2.3.83.2 enabledccenforcement (FI-9832)
Type:bool
Default Value:FALSE
Remarks:Allows the application and enforcement of the restrictions specified in this DCC record to be enabled or disabled so that the specifications may be left intact without being active.
2.3.83.3 fknumplan (FI-9833)
Type:guid (Unique, Cascade Delete, Not Modifiable)
Remarks:Indicates the associated DN or Pattern, (RoutePattern), to which this record's DCC specifications apply
2.3.83.4 pkid (FI-9831)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.84 device (TI-1)
Description:Lists every device in system from the CallManager perspective
Fields:
2.3.84.1 allowcfbcontrolofcallsecurityicon (FI-25945)
Type:bool
Default Value:FALSE
Remarks:Allow Conference Bridge control of the call security icon
2.3.84.2 allowcticontrolflag (FI-2618)
Type:bool
Default Value:TRUE
Remarks:If true, this device allows CTI Control.
Rule (RFI-132):
Type:Inter-field Condition and Constraint
Test Condition:tkModel = 72 OR tkModel = 73
Constraint:AllowCTIControlFlag = 't'
Remarks:CTI Ports and CTI Route Points must always be CTI Controlled
2.3.84.3 allowhotelingflag (FI-831)
Type:bool
Default Value:FALSE
Remarks:If true, this device allows extension mobility.
Rule (RFI-193):
Type:Inter-field Condition and Constraint
Test Condition:IsProtected ='t'
Constraint:AllowHotelingFlag = 'f'
Remarks:Protected phone cannot have Extension Mobility enabled
Rule (RI-19):
Type:Validation (Insert/Update)
Rule Name:AllowHotelingFlag - EM feature support required
Description:Device.AllowHotelingFlag can only be true for devices that support Extension Mobility.
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Extension Mobility can only turned on for devices that support Extension Mobility feature.
Remedy:Check device type and Extension Mobility feature support before enabling Extension Mobility.
Rule (RI-19):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:AllowHotelingFlag - EM feature support required
Description:Device.AllowHotelingFlag can only be true for devices that support Extension Mobility.
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Extension Mobility can only turned on for devices that support Extension Mobility feature.
Remedy:Check device type and Extension Mobility feature support before enabling Extension Mobility.
Rule (RI-202):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate Default Device Profile for Model
Description:Create a Default Device Profile for a device type if one does not already exist, and extension mobility is enabled on a device of that type (e.g., create the Default Device Profile for a Cisco 7960 if it does not exist and EM is enabled on a 7960).
Test Condition:IF (NEW.AllowHotelingFlag is true) and ((select count(*) from device where tkmodel = NEW.tkmodel and tkdeviceprofile = 3) = 0)
Error Message:No default model profile, no mismatch login performed
Rule (RI-376):
Type:Active (Insert/Update)
Rule Name:Insert Dynamic Records for Extension Mobility
Description:When Extension Mobility (EM) is enabled on a phone, create the corresponding record in the ExtensionMobilityDynamic and EMCCDynamic and EMRemoteDynamic
Test Condition:ON INSERT/UPDATE INTO Device
2.3.84.4 authenticationstring (FI-1912)
Type:string [50]
Default Value:EMPTY
Validation:^[0-9]{4,10}$
2.3.84.5 calledinternationalprefix (FI-3868)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called International Prefix
2.3.84.6 calledinternationalstripdigits (FI-3879)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledInternationalStripDigits >= 0) AND (CalledInternationalStripDigits <= 24)
Remarks:Called International Strip Digits
2.3.84.7 callednationalprefix (FI-3867)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called National Prefix
2.3.84.8 callednationalstripdigits (FI-3878)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledNationalStripDigits >= 0) AND (CalledNationalStripDigits <= 24)
Remarks:CalledNational Strip Digits
2.3.84.9 calledsubscriberprefix (FI-3870)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called Subscriber Prefix
2.3.84.10 calledsubscriberstripdigits (FI-3881)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledSubscriberStripDigits >= 0) AND (CalledSubscriberStripDigits <= 24)
Remarks:Called Subscriber Strip Digits
2.3.84.11 calledunknownprefix (FI-3869)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called Unknown Prefix
2.3.84.12 calledunknownstripdigits (FI-3880)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledUnknownStripDigits >= 0) AND (CalledUnknownStripDigits <= 24)
Remarks:Called Unknown Strip Digits
2.3.84.13 calreference (FI-21054)
Type:long
Default Value:-1
Remarks:user can assign confidential access level value to the device
2.3.84.14 ctiid (FI-12)
Type:identity (Unique, Not Modifiable)
Migration Source:DeviceList.DeviceId
Remarks:Trigger set on insert. (one greater than highest). 32 bit value for Computer Telephony Interface
Rule (RI-2):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Generate CTI ID value
Description:On insert of a new record generate a unique 32-bit integer value and store the result in the CTI ID field
Test Condition:On Insert
2.3.84.15 datetimeinserted (FI-2667)
Type:string [30] (Null OK)
Remarks:Date and Time when Phone was inserted. Will be provided by an active B-Rule on device insert. Format is YYMMDD:HrMinSec
2.3.84.16 defaultdtmfcapability (FI-592)
Type:long
Default Value:0
Remarks:Is this a dead field?
2.3.84.17 description (FI-3)
Type:string [512]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%\\&<>]{0,128}$
Migration Source:DeviceList.Description
Rule (RI-964):
Type:Active (Insert/Update)
Rule Name:Copy truncated version of device Description to device nDescription
Description:Up to 254 characters of device Description is copied to nDescription on inserts and updates. nDescription can be used for collated ordering.
Test Condition:ON INSERT/UPDATE set nDescription = description
2.3.84.18 deviceleveltraceflag (FI-824)
Type:bool
Default Value:FALSE
2.3.84.19 dialplanwizardgenid (FI-677)
Type:long (Indexed, Null OK)
Default Value:NULL
Remarks:This record created by DialPlanWizard
2.3.84.20 dndtimeout (FI-3286)
Type:long
Default Value:0
Check Constraint:(DNDTimeout >= 0) AND (DNDTimeout <= 120)
Remarks:Period in minutes to remind the user that DND is active
2.3.84.21 earlyoffersupportforvoicecall (FI-10230)
Type:bool
Default Value:FALSE
Remarks:True-AS-SIP endpoints supports early offer for voice calls; False-AS-SIP endpoints supports delayed offer for voice calls. The default value is False.
2.3.84.22 ecpublickeycurve (FI-27034)
Type:string [50] (Null OK)
Default Value:NULL
Validation:^[a-zA-Z 0-9]{1,50}$
Remarks:EC key size(bits) for device table
2.3.84.23 enablebfcp (FI-9996)
Type:bool
Default Value:FALSE
Remarks:Boolean flag to control whether or not Binary Floor Control Protocol (BFCP) is enabled for this device.
2.3.84.24 enablecallroutingtordwhennoneisactive (FI-25715)
Type:bool
Default Value:FALSE
Remarks:This flag is used to determine if Call has to be forwarded to all Remote destinations or not.
Rule (RI-2129):
Type:Validation (Insert/Update)
Rule Name:Rule to validate INSERT/UPDATE on column EnableCallRoutingToRdWhenNoneIsActive
Description:INSERT/UPDATE operation to set value of new column to true should be rejected for all devices except CTI Remote Device
Error Message:Cannot perform insert/update operation as the current value is not applicable to the device type
2.3.84.25 enablegatewayrecordingqsig (FI-21027)
Type:bool
Default Value:f
Remarks:Allow sending recording control adpu on qsig link.
2.3.84.26 enableixchannel (FI-6278)
Type:bool
Default Value:FALSE
Remarks:Boolean flag to control whether or not iX Channel is enabled for this device.
2.3.84.27 fkaarneighborhood (FI-1120)
Type:guid (Null OK)
Default Value:NULL
Remarks:Used by both gateway and Phone
Rule (RI-22):
Type:Validation (Insert/Update)
Rule Name:AAR feature support required
Description:Device.fkAARNeighorhood and Device.fkCallingSearchSpace_AAR can only be specified for devices that support the AAR feature
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 21 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:AAR Group and Calling Search Space can only be used for devices that support the AAR feature.
Remedy:Check device type and AAR feature support before specifying an AAR Group or AAR Calling Search Space.
Rule (RI-22):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:AAR feature support required
Description:Device.fkAARNeighorhood and Device.fkCallingSearchSpace_AAR can only be specified for devices that support the AAR feature
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 21 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:AAR Group and Calling Search Space can only be used for devices that support the AAR feature.
Remedy:Check device type and AAR feature support before specifying an AAR Group or AAR Calling Search Space.
2.3.84.28 fkcallingsearchspace (FI-11)
Type:guid (Null OK)
Default Value:NULL
Migration Source:NULL
Rule (RI-27):
Type:Validation (Insert/Update)
Rule Name:Device CSS Restriction
Description:Calling Search Space is allowed for devices that originate or direct calls. This currently includes the following classes of device: Gateway, Phone, CTI Route Point, Trunk, Simulation. Not valid for other classes. (Note: change to lookup in ProductSupportsFeature)
Test Condition:Device.fkCallingSearchSpace IS NOT NULL AND Device.tkClass NOT IN (1, 2, 8, 10, 13, 18) THEN Throw Exception
Error Message:CallingSearchSpace is not valid for this type of device.
Remedy:Remove the Calling Search Space setting from the device and try again.
2.3.84.29 fkcallingsearchspace_aar (FI-1118)
Type:guid (Null OK)
Default Value:NULL
Migration Source:NULL
Rule (RI-22):
Type:Validation (Insert/Update)
Rule Name:AAR feature support required
Description:Device.fkAARNeighorhood and Device.fkCallingSearchSpace_AAR can only be specified for devices that support the AAR feature
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 21 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:AAR Group and Calling Search Space can only be used for devices that support the AAR feature.
Remedy:Check device type and AAR feature support before specifying an AAR Group or AAR Calling Search Space.
Rule (RI-22):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:AAR feature support required
Description:Device.fkAARNeighorhood and Device.fkCallingSearchSpace_AAR can only be specified for devices that support the AAR feature
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 21 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:AAR Group and Calling Search Space can only be used for devices that support the AAR feature.
Remedy:Check device type and AAR feature support before specifying an AAR Group or AAR Calling Search Space.
2.3.84.30 fkcallingsearchspace_calledintl (FI-3891)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party International Number
2.3.84.31 fkcallingsearchspace_callednational (FI-3890)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party National Number
2.3.84.32 fkcallingsearchspace_calledsubscriber (FI-3893)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party Subscriber Number
2.3.84.33 fkcallingsearchspace_calledunknown (FI-3892)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party Unknown Number
2.3.84.34 fkcallingsearchspace_cdpntransform (FI-3506)
Type:guid (Null OK)
Default Value:NULL
Remarks:If useDevicePoolCdpnTransformCSS is set to False this transformation will be applied on the called party
Rule (RI-447):
Type:Validation (Insert/Update)
Rule Name:Device.fkCallingSearchSpace_CdPNTransform is allowed for all gateways other than FXS ports
Description:Device.fkCallingSearchSpace_CdPNTransform is allowed for all gateways other than FXS ports
Test Condition:ON INSERT/UPDATE
Error Message:Device.fkCallingSearchSpace_CdPNTransform is allowed for all gateways other than FXS ports
2.3.84.35 fkcallingsearchspace_cgpningressdn (FI-10120)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling search space applied to calling party number on ingress from the calling device
2.3.84.36 fkcallingsearchspace_cgpnintl (FI-5124)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party International Number
2.3.84.37 fkcallingsearchspace_cgpnnational (FI-5123)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party National Number
2.3.84.38 fkcallingsearchspace_cgpnsubscriber (FI-5126)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party Subscriber Number
2.3.84.39 fkcallingsearchspace_cgpntransform (FI-3378)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Search Space for Calling Party Name Transformation Pattern
2.3.84.40 fkcallingsearchspace_cgpnunknown (FI-5125)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party Unknown Number
2.3.84.41 fkcallingsearchspace_rdntransform (FI-9926)
Type:guid (Null OK)
Default Value:NULL
Remarks:If useDevicePoolRdnTransformCSS is set to False this transformation will be applied on the Redirecting Number
Rule (RI-841):
Type:Validation (Insert/Update)
Rule Name:Device.fkCallingSearchSpace_RdNTransform is allowed for all gateways other than FXS ports
Description:Device.fkCallingSearchSpace_RdNTransform is allowed for all gateways other than FXS ports
Test Condition:ON INSERT/UPDATE
Error Message:Device.fkCallingSearchSpace_RdNTransform is allowed for all gateways other than FXS ports
2.3.84.42 fkcallingsearchspace_refer (FI-2397)
Type:guid (Null OK)
Default Value:NULL
Remarks:Pkid of CallingSearchSpace record for refer called Rerouting Calling Search Space in Admin
2.3.84.43 fkcallingsearchspace_reroute (FI-2396)
Type:guid (Null OK)
Default Value:NULL
Remarks:Pkid of CallingSearchSpace record for rerouting called Out-of-dialog Refer Calling Search Space in Admin
2.3.84.44 fkcallingsearchspace_restrict (FI-2714)
Type:guid (Null OK)
Default Value:NULL
Remarks:Pkid of CallingSearchSpace record for restriction
2.3.84.45 fkcallmanagergroup (FI-1301)
Type:guid (Null OK)
Default Value:NULL
Remarks:Used only by some Gateways.
Rule (RFI-6):
Type:Inter-field Condition and Constraint
Test Condition:tkClass = 7 OR tkModel = 133
Constraint:fkCallManagerGroup IS NOT NULL
Null Allowed:null
Remarks:CallManager required for Route list or WSM trunk.
Rule (RFI-7):
Type:Inter-field Condition and Constraint
Test Condition:tkClass != 7 AND tkModel != 133
Constraint:fkCallManagerGroup IS NULL
Null Allowed:null
Remarks:The Cisco Unified Communications Manager Group setting on a device (Device.fkCallManagerGroup) applies only to Route Lists. A group cannot be assigned to any other device types (Device.fkCallManagerGroup must be null).
2.3.84.46 fkcommondeviceconfig (FI-3164)
Type:guid (Null OK)
Default Value:NULL
2.3.84.47 fkcommonphoneconfig (FI-2945)
Type:guid
Default Value:ac243d17-98b4-4118-8feb-5ff2e1b781ac
2.3.84.48 fkdevicepool (FI-8)
Type:guid (Null OK)
Default Value:NULL
Migration Source:Convert from DeviceList.DevicePool
Rule (RI-29):
Type:Validation (Insert/Update)
Rule Name:Device Pool Required
Description:All devices that register with CallManager must be assigned to a specific Device Pool, except for Route Lists which use only a CallManager Group
Test Condition:IF (Device.fkDevicePool IS NULL AND Device.tkClass NOT IN (7, 15, 17, 254)) THEN Throw Exception
Error Message:A Device Pool is required for this device.
Remedy:Specify a Device Pool and try again.
Rule (RI-223):
Type:Active (Insert)
Rule Name:Add a VGC Gateway to MGCP on Device update
Description:On Insert only
Test Condition:?
Rule (RI-2155):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of Device, Set fkDevicePool=NULL for TelePresence Conference devices
Description:On Insert/Update of Device, make sure the fkDevicePool is NULL for TelePresence Conference devices
Test Condition:ON INSERT/UPDATE: IF fkDevicePool IS NOT NULL Set fkDevicePool to NULL
Rule (RI-2155):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:On Active Insert/Update of Device, Set fkDevicePool=NULL for TelePresence Conference devices
Description:On Insert/Update of Device, make sure the fkDevicePool is NULL for TelePresence Conference devices
Test Condition:ON INSERT/UPDATE: IF fkDevicePool IS NOT NULL Set fkDevicePool to NULL
2.3.84.49 fkdialrules (FI-2395)
Type:guid (Null OK)
Default Value:NULL
Remarks:Pkid of DialRules record
Rule (RI-320):
Type:Validation (Insert/Update)
Rule Name:Device Restriction for SIP Dial Rules
Description:SIP Dial Rules for 7905/7912 may only be associated with 7905 and 7912 model phones. All other phones must use 7940/7960/TMP dial rules.
Test Condition:ON INSERT/UPDATE IN Device IF (DialRules.tkDialPattern = 0 and Device.tkProduct IS NOT IN (7905, 7912) OR DialRules.tkDialPattern == 1 AND Device.tkProduct IS IN (7905, 7912)) THEN throw exception
Error Message:Cannot assign Dial Rules of this type to the specified device (model and rule types are mismatched).
Remedy:Check the dial rule and device type to make sure they are compatible (e.g., 7905 dial rule for a 7905 device).
Rule (RI-320):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Device Restriction for SIP Dial Rules
Description:SIP Dial Rules for 7905/7912 may only be associated with 7905 and 7912 model phones. All other phones must use 7940/7960/TMP dial rules.
Test Condition:ON INSERT/UPDATE IN Device IF (DialRules.tkDialPattern = 0 and Device.tkProduct IS NOT IN (7905, 7912) OR DialRules.tkDialPattern == 1 AND Device.tkProduct IS IN (7905, 7912)) THEN throw exception
Error Message:Cannot assign Dial Rules of this type to the specified device (model and rule types are mismatched).
Remedy:Check the dial rule and device type to make sure they are compatible (e.g., 7905 dial rule for a 7905 device).
2.3.84.50 fkelingroup (FI-26914)
Type:guid (Null OK)
Remarks:ELINGroup record used by this Device
2.3.84.51 fkenduser (FI-829)
Type:guid (Indexed, Null OK)
Default Value:NULL
Migration Source:User.pkid
Remarks:This is the id of currently logged on user if EM is being used, or the owner of the device if EM is not being used.
Rule (RFI-308):
Type:Inter-field Condition and Constraint
Test Condition:requireCERlocation = 't'
Constraint:fkEndUser IS NOT NULL
Null Allowed:null
Remarks:A device owner is required to allow off premise locations.
Rule (RI-163):
Type:Validation (Insert/Update)
Rule Name:Device Owner or Logged In User
Description:End Users can only own or log into phones and CTI Route Points.
Test Condition:IF (@Device.fkEndUser IS NOT NULL) AND (@Device.tkClass NOT IN (1, 10)) THEN throw exception
Error Message:End Users can only own or log into Phones and CTI Route Points.
Remedy:Remove the EndUser from the device and try again.
Rule (RI-844):
Type:Active (Insert/Update)
Rule Name:IMS-integrated Mobile Owner Syncs with Mobility User
Description:For IMS-integrated Mobile devices (as defined in ProductSupportsFeature), the owner (device.fkenduser) and mobility user (device.fkenduser_mobility) must be in sync. Sync owner to mobility user if it's not set.
Test Condition:ON INSERT/UPDATE in Device: IF (old_fkenduer_mobility <> new_fkenduser_mobility) THEN set fkenduser = new_fkenduser_mobility END IF;
Rule (RI-844):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:IMS-integrated Mobile Owner Syncs with Mobility User
Description:For IMS-integrated Mobile devices (as defined in ProductSupportsFeature), the owner (device.fkenduser) and mobility user (device.fkenduser_mobility) must be in sync. Sync owner to mobility user if it's not set.
Test Condition:ON INSERT/UPDATE in Device: IF (old_fkenduer_mobility <> new_fkenduser_mobility) THEN set fkenduser = new_fkenduser_mobility END IF;
Rule (RI-941):
Type:Validation (Insert/Update)
Rule Name:Token User can own only CDT device
Description:Token User can own only CDT device or be used for mobility only for CDT
Test Condition:On I/U of Device: FOR fkEndUser or fkEndUser_Mobility ,If tkUserProfile=3 AND (tkModel<>645 AND tkProduct<>530) THEN THROW EXCEPTION
Error Message:Token EndUser can be associated with CDT only or used for mobility
2.3.84.52 fkenduser_mobility (FI-3381)
Type:guid (Null OK)
Default Value:NULL
Remarks:End User that owns Dual-Mode, SNR Device, or deskphone with Mobility button (for Cell Pickup)
Rule (RFI-197):
Type:Inter-field Condition and Constraint
Test Condition:tkDeviceProtocol = 17
Constraint:(fkEndUser_Mobility IS NOT NULL)
Remarks:Mobility EndUser is required for Mobile Smart Client devices (Cisco Unified Mobile Communicator)
Rule (RI-411):
Type:Active (Update)
Rule Name:Device.fkEndUser_Mobility change removes RemoteDestinations
Description:When the EndUser associated with a Dual-mode or Remote Destination Profile device is changes, any Remote Destinations associated with that device are removed because the use data is no longer valid.
Test Condition:ON UPDATE IN Device: IF (NVL(old_fkenduser_mobility,'') <> NVL(new_fkenduser_mobility,'')) THEN DELETE FROM remotedestination WHERE (fkdevice_dualmode = old_pkid) OR (fkdevice_remotedestination = old_pkid) END IF;
Rule (RI-844):
Type:Active (Insert/Update)
Rule Name:IMS-integrated Mobile Owner Syncs with Mobility User
Description:For IMS-integrated Mobile devices (as defined in ProductSupportsFeature), the owner (device.fkenduser) and mobility user (device.fkenduser_mobility) must be in sync. Sync owner to mobility user if it's not set.
Test Condition:ON INSERT/UPDATE in Device: IF (old_fkenduer_mobility <> new_fkenduser_mobility) THEN set fkenduser = new_fkenduser_mobility END IF;
Rule (RI-874):
Type:Validation (Insert/Update)
Rule Name:Mobility Check on EndUser for CTI Remote Device
Description:EndUser associated with CTI Remote Device should be Mobility Enabled.
Test Condition:Check description for complete rule. ON INSERT INTO Device: SELECT fkenduser_mobility INTO theEndUser FROM device WHERE pkid = device.pkid; SELECT EnableMobility INTO mobility FROM enduser WHERE pkid = theEndUser; IF (mobility = 'F') THEN throw exception END IF;
Error Message:Cannot add the device for EndUser that does not have Mobility enabled.
Remedy:Enable Mobility on the EndUser associated with CTI Remote Device and try again.
Rule (RI-941):
Type:Validation (Insert/Update)
Rule Name:Token User can own only CDT device
Description:Token User can own only CDT device or be used for mobility only for CDT
Test Condition:On I/U of Device: FOR fkEndUser or fkEndUser_Mobility ,If tkUserProfile=3 AND (tkModel<>645 AND tkProduct<>530) THEN THROW EXCEPTION
Error Message:Token EndUser can be associated with CDT only or used for mobility
2.3.84.53 fkfeaturecontrolpolicy (FI-5715)
Type:guid (Null OK)
Default Value:NULL
Remarks:Feature Control Policy Record
Rule (RI-734):
Type:Validation (Insert/Update)
Rule Name:Device Table Feature Control Policy Restriction
Description:Only devices that support Feature Control Policy can specify fkFeatureControlPolicy
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 103 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Feature Control Policy can be set for devices that supports the Feature Control Policy
Remedy:Check Feature Control Policy feature support and device type before specifying a value for fkFeatureControlPolicy.
Rule (RI-734):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Device Table Feature Control Policy Restriction
Description:Only devices that support Feature Control Policy can specify fkFeatureControlPolicy
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 103 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Feature Control Policy can be set for devices that supports the Feature Control Policy
Remedy:Check Feature Control Policy feature support and device type before specifying a value for fkFeatureControlPolicy.
2.3.84.54 fkgeolocation (FI-5001)
Type:guid (Null OK)
Default Value:NULL
2.3.84.55 fkgeolocationfilter_lp (FI-5002)
Type:guid (Null OK)
Default Value:NULL
2.3.84.56 fklocation (FI-599)
Type:guid
Default Value:29c5c1c4-8871-4d1e-8394-0b9181e8c54d
Rule (RI-30):
Type:Validation (Insert/Update)
Rule Name:Device Location Restriction
Description:Location is not used for MTP, Route List, Gatekeeper, Device Profile
Test Condition:IF (Device.fkLocation IS NOT NULL) AND (Device.tkClass IN (5, 7, 15, 17, 254)) THEN Throw Exception
Error Message:Location is not valid for this type of device.
Remedy:Remove the Location setting from the device and try again.
Rule (RI-30):
Type:Validation (Insert/Update)
Rule Name:Device Location Restriction
Description:Location is not used for MTP, Route List, Gatekeeper, Device Profile
Test Condition:IF (Device.fkLocation IS NOT NULL) AND (Device.tkClass IN (5, 7, 15, 17, 254)) THEN Throw Exception
Error Message:Location is not valid for this type of device.
Remedy:Remove the Location setting from the device and try again.
2.3.84.57 fkmatrix_presence (FI-2752)
Type:guid
Default Value:ad243d17-98b4-4118-8feb-5ff2e1b781ac
Remarks:delete likely, use securityprofile
2.3.84.58 fkmediaresourcelist (FI-837)
Type:guid (Null OK)
Default Value:NULL
Rule (RI-31):
Type:Validation (Insert/Update)
Rule Name:Media Resource List Restriction
Description:Media Resource List is used only for Phones, Gateways, CTI Route Points, Trunks and Simulations. Media Resource List is not valid on other types of devices
Test Condition:IF (Device.fkMediaResourceList IS NOT NULL) AND (Device.tkClass IS NOT IN (1, 2, 10, 13, 18)) THEN Throw Exception
Error Message:Media Resource List is not valid for this type of device.
Remedy:Remove the Media Resource List setting from the device and try again.
Rule (RI-31):
Type:Validation (Insert/Update)
Rule Name:Media Resource List Restriction
Description:Media Resource List is used only for Phones, Gateways, CTI Route Points, Trunks and Simulations. Media Resource List is not valid on other types of devices
Test Condition:IF (Device.fkMediaResourceList IS NOT NULL) AND (Device.tkClass IS NOT IN (1, 2, 10, 13, 18)) THEN Throw Exception
Error Message:Media Resource List is not valid for this type of device.
Remedy:Remove the Media Resource List setting from the device and try again.
Rule (RI-405):
Type:Active (Update)
Rule Name:Setting MTPRequired='F' or fkMRL=NULL sets H323Device.EnableOutboundFaststart='F'
Description:When EnableOutboundFastStart is true for a H.323 device, the MTPRequired field must also be true, and a Media Resource Group List must be selected. If the MTPRequired is subsequently changed to False, or the Media Resource Group List is removed from the device, the EnableOutboundFaststart setting is automatically turned off.
Test Condition:ON UPDATE in Device: If (new_tkDeviceProtocol = 2) AND ( (new_MTPRequired = 'F' AND old_MTPRequired = 'T') OR (old_fkMediaResourceList IS NOT NULL AND new_fkMediaResourceList IS NULL) ) THEN UPDATE H323Device SET EnableOutboundFaststart = 'F' WHERE fkDevice = new_pkid AND EnableOutboundFaststart = 'T'; END IF;
2.3.84.59 fkmlppdomain (FI-1954)
Type:guid (Null OK)
Default Value:NULL
Migration Source:mlppdomainid
Remarks:null means uses device pool value
Rule (RI-56):
Type:Validation (Insert/Update)
Rule Name:MLPP Domain ID Restriction
Description:MLPP Domain ID is allowed for devices that originate or direct calls. This currently includes the following classes of device: Gateway, Phone, CTI Route Point, Trunk, Simulation and Device Profile. Not valid for other classes. (Note: change to lookup in ProductSupportsFeature)
Test Condition:Device.fkMlppDomainID IS NOT NULL AND Device.tkClass IN (1, 2, 8, 10, 13, 18) THEN Throw Exception
Error Message:MLPP Domain ID is not valid for this type of device.
Remedy:Remove the MLPP Domain ID setting from the device and try again.
Rule (RI-56):
Type:Validation (Insert/Update)
Rule Name:MLPP Domain ID Restriction
Description:MLPP Domain ID is allowed for devices that originate or direct calls. This currently includes the following classes of device: Gateway, Phone, CTI Route Point, Trunk, Simulation and Device Profile. Not valid for other classes. (Note: change to lookup in ProductSupportsFeature)
Test Condition:Device.fkMlppDomainID IS NOT NULL AND Device.tkClass IN (1, 2, 8, 10, 13, 18) THEN Throw Exception
Error Message:MLPP Domain ID is not valid for this type of device.
Remedy:Remove the MLPP Domain ID setting from the device and try again.
2.3.84.60 fkmobilesmartclientprofile (FI-3697)
Type:guid (Null OK)
Default Value:NULL
Remarks:Type of Smart Client for smart client devices and dual-mode phones
Rule (RI-484):
Type:Active (Update)
Rule Name:Clear RemoteDestination if Smart Client disabled
Description:If a Dual-mode device is configured with Mobile Smart Client enabled and a Remote Destination exists that is using the smart client, the RemoteDestination.fkDevice_MobileSmartClient field must be set to NULL if the Dual Mode is updated to disable the Mobile Smart Client (device.fkMobileSmartClientProfile is set to NULL).
Test Condition:ON UPDATE IN Device: IF (new_IsDualMode = 't') AND (new_fkMobileSmartClientProfile IS NULL) AND (old_fkMobileSmartClientProfile IS NOT NULL) THEN UPDATE RemoteDestination SET fkDevice_MobileSmartClient = NULL WHERE fkDevice_MobileSmartClient = new_pkid END IF;
Rule (RI-946):
Type:Active (Insert/Update)
Rule Name:Auto-fix for Dual Mode and Mobile Smart Client device settings
Description:IF autofix is enabled AND IsDualMode='t' THEN SET tkRingSeting_DND = 1 i.e. disabled AND OR IF tkDevicePotocol=17 (MobileSmartClient) THEN SET tkRingSeting_DND = 1 i.e. disabled AND SET fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Test Condition:IF g_enable_auto_fix = 't' AND IsDualMode='t' THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=NULL OR IF tkDevicePotocol=17 THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Rule (RI-946):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Auto-fix for Dual Mode and Mobile Smart Client device settings
Description:IF autofix is enabled AND IsDualMode='t' THEN SET tkRingSeting_DND = 1 i.e. disabled AND OR IF tkDevicePotocol=17 (MobileSmartClient) THEN SET tkRingSeting_DND = 1 i.e. disabled AND SET fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Test Condition:IF g_enable_auto_fix = 't' AND IsDualMode='t' THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=NULL OR IF tkDevicePotocol=17 THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
2.3.84.61 fkphonetemplate (FI-9)
Type:guid (Null OK)
Default Value:NULL
Migration Source:Get indirectly from PhoneDeviceToTemplate
Remarks:If tModel.tClass is not phone, then this is NULL
Rule (RI-16):
Type:Validation (Insert/Update)
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-16):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-17):
Type:Validation (Insert/Update)
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-17):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-423):
Type:Active (Delete)
Rule Name:Remove Individual phone templates
Description:When a phone with individual Phone Templates is deleted, the individual Phone Templates must be deleted.
Test Condition:ON DELETE in Device: if phonetemplate.name like '%Individual Template' DELETE FROM phonetemplate WHERE PhoneTemplate.pkid = device.fkphoneTemplate
2.3.84.62 fkprocessnode (FI-424)
Type:guid (Cascade Delete, Not Modifiable, Null OK)
Default Value:NULL
Migration Source:See word doc, each install must add node information
Remarks:This is the node this device is running on if the device is a process.
Rule (RI-32):
Type:Validation (Insert/Update)
Rule Name:Process Node Required
Description:Software based devices that rely on the IP Media Streaming service must be associated with a server (Process Node).
Test Condition:IF (Device.fkProcessNode IS NULL) AND (Device.tkModel IN (50, 70, 110, 126)) THEN Throw Exception
Error Message:A Server (Process Node) is required for this device.
Remedy:Specify a Server (Process Node) and try again.
Rule (RI-33):
Type:Validation (Insert/Update)
Rule Name:Process Node Restriction
Description:Devices other than software media streaming applications cannot be assigned to a server (Process Node)
Test Condition:IF (Device.fkProcessNode IS NOT NULL) AND (Device.tkModel NOT IN (50, 70, 110, 126)) THEN Throw Exception
Error Message:This device cannot be assigned to a Server (ProcessNode).
Remedy:Remove the Server (Process Node) setting from the device and try again.
Rule (RI-34):
Type:Validation (Insert/Update)
Rule Name:Enterprise Node Restriction
Description:Devices cannot be assigned to the reserved Enterprise Node (system Process Node)
Test Condition:IF (Device.fkProcessNode = '00000000-111-0000-0000-000000000000') THEN Throw Exception
Error Message:Devices cannot be assigned to the reserved Enterprise Node (system Process Node).
Remedy:Associate the device with another Server (Process Node).
Rule (RI-35):
Type:Validation (Insert/Update)
Rule Name:One software device type per Server
Description:Only one software based IP Media Streaming device of each type (CFB, MOH, MTP, ANN) can be assigned to a Server (Process Node)
Test Condition:IF (SELECT COUNT(*) FROM Device WHERE fkProcessNode = @Device.fkProcessNode AND tkModel = @Device.tkModel) > 1 THEN Throw Exception
Error Message:Only one software based IP Media Streaming device of each type (CFB, MOH, MTP, ANN) can be assigned to a Server (Process Node).
Remedy:Associate the device with another Server (Process Node).
Rule (RI-380):
Type:Validation (Insert/Update/Delete)
Rule Name:One server should have exactly one software device (CFB, MTP, MOH, ANN, IVR) each type
Description:One IP Media Streaming software device each type is install by default on all servers cannot be deleted
Test Condition:ON DELETE or Insert Device: IF (old_tkProduct IN (28, 30, 51, 89, 36672)) THEN throw exception;
Error Message:Cannot insert or delete the IP Media Streaming software devices installed on a server by default.
Remedy:Disable the service or remove the device from Media Resource Groups where it appears.
2.3.84.63 fksecurityprofile (FI-2349)
Type:guid (Null OK)
Default Value:NULL
Remarks:Foreign Key to Security Profile
Rule (RI-316):
Type:Active (Insert/Update)
Rule Name:Prevent applying secure profile where not supported.
Description:on I/U of Device
Test Condition:Only endpoints on gateways with secure mode support may be set to use Security Profiles marked for secure mode. Further, all endpoints on analog gateways must remain consistent in either all operating in secure mode or all in non-secure mode
Rule (RI-340):
Type:Validation (Insert/Update)
Rule Name:Correct security profile for device
Description:on I/U of device
Test Condition:prevent bad value combinations
Rule (RI-402):
Type:Active (Insert/Update)
Rule Name:Security Profile required if Standard Security Profile exists for device type, models will be automatically set to NULL
Description:If a Standard Security Profile exist for a given device type or class, then devices of that type or class must use a Security Profile.
Test Condition:ON INSERT/UPDATE INTO Device: IF (new_fkSecurityProfile IS NULL) THEN SELECT COUNT(*) INTO nRows FROM SecurityProfile where IsStandard = 't' AND tkModel = new_tkModel and tkDeviceProtocol = new_tkDeviceProtocol); IF nRows > 0 THEN throw exception;
Error Message:A security profile is required for this model and protocol.
Remedy:Specify a Security Profile that matches the device type.
Rule (RI-402):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Security Profile required if Standard Security Profile exists for device type, models will be automatically set to NULL
Description:If a Standard Security Profile exist for a given device type or class, then devices of that type or class must use a Security Profile.
Test Condition:ON INSERT/UPDATE INTO Device: IF (new_fkSecurityProfile IS NULL) THEN SELECT COUNT(*) INTO nRows FROM SecurityProfile where IsStandard = 't' AND tkModel = new_tkModel and tkDeviceProtocol = new_tkDeviceProtocol); IF nRows > 0 THEN throw exception;
Error Message:A security profile is required for this model and protocol.
Remedy:Specify a Security Profile that matches the device type.
Rule (RI-459):
Type:Validation (Insert/Update)
Rule Name:Device.fkSecurityProfile restriction for CUMA
Description:Security Profile used by a device cannot be a CUMA security policy
Test Condition:Security Profile used by a device cannot be a CUMA security policy
Rule (RI-472):
Type:Validation (Insert/Update)
Rule Name:Security Profile must be secure for Protected device (secure tone)
Description:Security Profile used with Protected device must be secure (encrypted)
Test Condition:ON INSERT/UPDATE IN Device, SecurityProfile:
Error Message:Security Profiles used with Protected phones (Device.IsProtected = True) must use encryption
Remedy:Make sure the Security Profile uses Encryption, or disable Secure Tone on the phone
Rule (RI-604):
Type:Validation (Update)
Rule Name:SAF Enabled trunk only supports non secure profile
Description:SAF Enabled trunk only supports non secure profile
Test Condition:SAF Enabled trunk only supports non secure profile
Error Message:SAF Enabled trunk only supports non secure profile
Rule (RI-940):
Type:Validation (Insert/Update)
Rule Name:Model Independent Security Profile
Description:Check if the device supports Model independent security profile , if yes then check whether this device support features like Encryption,Authentication and File Encryption and if it doesn't supports any of these three features then set its security profile as the Standard Non-Secure security profile intended for that particular model.
Test Condition:ON INSERT/UPDATE INTO Device: SELECT tkSecurityPolicy INTO m_tkSecurityPolicy FROM SecurityProfile WHERE pkid = new_fkSecurityProfile; IF device supports Model Independent Security Profile (m_tkSecurityProfile =99) THEN IF there exists a record in PSF table for each supporting feature: Encryption, Authentication, File Encryption with tkDeviceProtocol in (new_tkDeviceProtocol,99) and tkModel = new_tkModel THEN RETURN new_fkSecurityProfile; ELSE SELECT pkid INTO m_fkSecurityProfile FROM SecurityProfile WHERE tkmodel = new_tkModel AND tkDeviceProtocol = new_tkDeviceProtocol AND isStandard = 't';RETURN m_fkSecurityProfile;
Remedy:1
Rule (RI-940):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Model Independent Security Profile
Description:Check if the device supports Model independent security profile , if yes then check whether this device support features like Encryption,Authentication and File Encryption and if it doesn't supports any of these three features then set its security profile as the Standard Non-Secure security profile intended for that particular model.
Test Condition:ON INSERT/UPDATE INTO Device: SELECT tkSecurityPolicy INTO m_tkSecurityPolicy FROM SecurityProfile WHERE pkid = new_fkSecurityProfile; IF device supports Model Independent Security Profile (m_tkSecurityProfile =99) THEN IF there exists a record in PSF table for each supporting feature: Encryption, Authentication, File Encryption with tkDeviceProtocol in (new_tkDeviceProtocol,99) and tkModel = new_tkModel THEN RETURN new_fkSecurityProfile; ELSE SELECT pkid INTO m_fkSecurityProfile FROM SecurityProfile WHERE tkmodel = new_tkModel AND tkDeviceProtocol = new_tkDeviceProtocol AND isStandard = 't';RETURN m_fkSecurityProfile;
Remedy:1
2.3.84.64 fksipprofile (FI-2489)
Type:guid (Null OK)
Default Value:NULL
Rule (RI-936):
Type:Active (Insert/Update)
Rule Name:On Insert/Update of Device set SIPProfile to NULL for non SIP device
Description:On Insert/Update of Device, SET SIPProfile to NULL for non SIP device.
Test Condition:For INSERT/UPDATE of Device, IF tkdeviceprotocol <> 11,UPDATE Device SET fkSIPProfile = NULL
Rule (RI-936):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:On Insert/Update of Device set SIPProfile to NULL for non SIP device
Description:On Insert/Update of Device, SET SIPProfile to NULL for non SIP device.
Test Condition:For INSERT/UPDATE of Device, IF tkdeviceprotocol <> 11,UPDATE Device SET fkSIPProfile = NULL
2.3.84.65 fksoftkeytemplate (FI-1129)
Type:guid (Null OK)
Default Value:NULL
Remarks:association between device and softkey template
Rule (RI-37):
Type:Validation (Insert/Update)
Rule Name:SoftkeyTemplate Restriction
Description:Softkey Templates can be assigned only to devices that support Softkeys
Test Condition:IF (@Device.fkSoftkeyTemplate IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 18 AND tkProduct = @Device.tkProduct AND tkDeviceprotocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Softkey Template is not valid for this type of device.
Remedy:Remove the Softkey Template setting and try again.
Rule (RI-37):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:SoftkeyTemplate Restriction
Description:Softkey Templates can be assigned only to devices that support Softkeys
Test Condition:IF (@Device.fkSoftkeyTemplate IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 18 AND tkProduct = @Device.tkProduct AND tkDeviceprotocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Softkey Template is not valid for this type of device.
Remedy:Remove the Softkey Template setting and try again.
2.3.84.66 fkvipre164transformation (FI-5272)
Type:guid (Null OK)
Default Value:NULL
Migration Source:NULL
2.3.84.67 fkwifihotspotprofile (FI-25811)
Type:guid (Null OK)
Remarks:Reference to WiFi HotspotProfile.
2.3.84.68 fkwirelesslanprofilegroup (FI-25713)
Type:guid (Null OK)
Remarks:Reference to Wireless LAN Profile Group.
2.3.84.69 hotlinedevice (FI-3940)
Type:bool
Default Value:FALSE
Remarks:TRUE if this is a Hotline device
Rule (RI-631):
Type:Validation (Insert/Update)
Rule Name:Hotline support required for Hotline Device
Description:Hotline Device setting can only be true for devices supporting Hotline feature (tkSupportsFeature = 93)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support Hotline (hotlinedevice setting)
Remedy:Set hotlinedevice to false and try again
Rule (RI-631):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Hotline support required for Hotline Device
Description:Hotline Device setting can only be true for devices supporting Hotline feature (tkSupportsFeature = 93)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support Hotline (hotlinedevice setting)
Remedy:Set hotlinedevice to false and try again
2.3.84.70 huntlistforvm (FI-3167)
Type:bool
Default Value:FALSE
2.3.84.71 ignorepi (FI-2162)
Type:bool
Default Value:FALSE
2.3.84.72 ikdevice_defaultprofile (FI-833)
Type:guid (Null OK)
Default Value:NULL
Remarks:Points to the profile to log in when "logout" is called. If an insert or update is performed, and this field is NULL, then generate an auto-generated profile based on this device's current settings. If this value was pointing to a AGP, then delete the old AGP. If the AllowHotellingFlag is true.
Rule (RI-310):
Type:Active (Update)
Rule Name:(obsolete) Insert DeviceEMSyn record if auto sync of auto generated profile is needed
Description:When EM is on (Device.AllowHotelingFlag = true), if the default Device Profile is the auto generated Device Profile for the current device, and the value of service parameter (enableAutoDeviceProfileSynChronize) is true, then insert a record into DeviceEMSyn table with the pkid of auto-generated profile and the pkid of the current device. Later DbMon will process the change notification of DeviceEMSyn to re-generate the auto-generated profile of the current device.
Test Condition:Device.AllowHotelingFlag = true
Rule (RI-343):
Type:Validation (Insert/Update)
Rule Name:EM Logout Profile Model and Protocol Restriction
Description:The model and protocol of a phone and a User Device Profile selected as the logout profile must both match
Test Condition:ON INSERT/UPDATE IN Device IF (Device.tkModel <> Profile.tkModel) OR (Device.tkDeviceProtocol <> Profile.tkDeviceProtocol) THEN throw exception
Error Message:Logout Profile is not the same model and protocol as the device
Remedy:Select a logout profile that is the same model and protocol as the phone and try again
Rule (RI-376):
Type:Active (Insert/Update)
Rule Name:Insert Dynamic Records for Extension Mobility
Description:When Extension Mobility (EM) is enabled on a phone, create the corresponding record in the ExtensionMobilityDynamic and EMCCDynamic and EMRemoteDynamic
Test Condition:ON INSERT/UPDATE INTO Device
2.3.84.73 ikdevice_primaryphone (FI-3524)
Type:guid (Null OK)
Default Value:NULL
Remarks:Primary Phone associated with this device
2.3.84.74 internationalprefix (FI-3513)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:International Prefix
Rule (RFI-184):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77)
Constraint:(InternationalPrefix = '') OR (InternationalPrefix = 'Default') OR (InternationalPrefix = 'default')
Null Allowed:null
Remarks:International Prefix should be empty for devices other than H323 gateways and trunks and MGCP T1/E1 PRI and BRI gateways
Rule (RFI-256):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77)
Constraint:(InternationalStripDigits = '') OR (InternationalStripDigits IS NULL)
Null Allowed:null
Remarks:International Strip Digits should be empty for devices other than H323 gateways and trunks and MGCP T1/E1 PRI and BRI gateways
2.3.84.75 internationalstripdigits (FI-5112)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(InternationalStripDigits >= 0) AND (InternationalStripDigits <= 24)
Remarks:International Strip Digits
Rule (RFI-228):
Type:Inter-field Condition and Constraint
Test Condition:(InternationalPrefix = 'Default') OR (InternationalPrefix = 'default')
Constraint:InternationalStripDigits IS NULL
Remarks:Cannot use InternationalStripDigits when the Default prefix is used.
2.3.84.76 isactive (FI-3592)
Type:bool
Default Value:TRUE
Remarks:Determines whether a phone consumes licenses and can register with CUCM. Intended to allow BAT dummy phones to be provisioned for use with TAPS without consuming additional licenses.
2.3.84.77 isdualmode (FI-3377)
Type:bool (Indexed, Not Modifiable)
Default Value:FALSE
Remarks:Indicates a remote destination is a dual-mode phone; set based on device type
Rule (RI-379):
Type:Validation (Insert/Update)
Rule Name:Device DND Option feature restriction
Description:DND Option can only be set to non-Zero on devices that support the DND feature (in ProductSupportsFeature table). For those devices that support the feature, only the Ringer Off (0) is valid, unless a parameter is present in the PSF record. If a parameter value of 1 exists in PSF table, only Call Reject is valid. If the param value is (2), all options including Use Common Profile (2) are valid. Dual mode and remote destination profile only support the Call Reject option.
Test Condition:ON INSERT INTO Device: IF((tkproduct=112 or isdualmode = 't') and (tkDNDOption <>1)) throw exception; ELSE IF (new_tkDNDOption <> 0) THEN SELECT parameter INTO restriction FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_DND) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99); IF (rows returned = 0) THEN throw exception ELSE IF (NVL(restriction, '') <> '') THEN IF (new_tkDNDOption <> restriction) THEN throw exception END IF; END IF; END IF; END IF
Error Message:This device does not support the selected DND Option
Remedy:Do not set a DND Option, or check for restrictions on which options are valid for this device.
Rule (RI-381):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:DualMode device type (in PSF) is marked isDualMode = True
Description:If a device type is marked as Dual Mode in the ProductSupportsFeature table, then the Device and RemoteDestination records for the device are automatically updated to set IsDualMode field to true.
Test Condition:ON INSERT INTO Device
Rule (RI-381):
Type:Active (Insert)
Rule Name:DualMode device type (in PSF) is marked isDualMode = True
Description:If a device type is marked as Dual Mode in the ProductSupportsFeature table, then the Device and RemoteDestination records for the device are automatically updated to set IsDualMode field to true.
Test Condition:ON INSERT INTO Device
Rule (RI-484):
Type:Active (Update)
Rule Name:Clear RemoteDestination if Smart Client disabled
Description:If a Dual-mode device is configured with Mobile Smart Client enabled and a Remote Destination exists that is using the smart client, the RemoteDestination.fkDevice_MobileSmartClient field must be set to NULL if the Dual Mode is updated to disable the Mobile Smart Client (device.fkMobileSmartClientProfile is set to NULL).
Test Condition:ON UPDATE IN Device: IF (new_IsDualMode = 't') AND (new_fkMobileSmartClientProfile IS NULL) AND (old_fkMobileSmartClientProfile IS NOT NULL) THEN UPDATE RemoteDestination SET fkDevice_MobileSmartClient = NULL WHERE fkDevice_MobileSmartClient = new_pkid END IF;
Rule (RI-946):
Type:Active (Insert/Update)
Rule Name:Auto-fix for Dual Mode and Mobile Smart Client device settings
Description:IF autofix is enabled AND IsDualMode='t' THEN SET tkRingSeting_DND = 1 i.e. disabled AND OR IF tkDevicePotocol=17 (MobileSmartClient) THEN SET tkRingSeting_DND = 1 i.e. disabled AND SET fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Test Condition:IF g_enable_auto_fix = 't' AND IsDualMode='t' THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=NULL OR IF tkDevicePotocol=17 THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
2.3.84.78 ispaienabled (FI-3484)
Type:bool
Default Value:TRUE
2.3.84.79 isprotected (FI-3685)
Type:bool (Indexed)
Default Value:FALSE
Remarks:Device is used for secure calls with supplementary services disabled
Rule (RI-471):
Type:Validation (Insert/Update)
Rule Name:Secure Tone support required for Protected device
Description:IsProtected setting can only be true for devices supporting secure tone feature (tkSupportsFeature = 81)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support secure tone (isprotected setting)
Remedy:Set IsProtected to false and try again
Rule (RI-471):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Secure Tone support required for Protected device
Description:IsProtected setting can only be true for devices supporting secure tone feature (tkSupportsFeature = 81)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support secure tone (isprotected setting)
Remedy:Set IsProtected to false and try again
Rule (RI-472):
Type:Validation (Insert/Update)
Rule Name:Security Profile must be secure for Protected device (secure tone)
Description:Security Profile used with Protected device must be secure (encrypted)
Test Condition:ON INSERT/UPDATE IN Device, SecurityProfile:
Error Message:Security Profiles used with Protected phones (Device.IsProtected = True) must use encryption
Remedy:Make sure the Security Profile uses Encryption, or disable Secure Tone on the phone
Rule (RI-473):
Type:Validation (Insert/Update)
Rule Name:DN restrictions for Protected device (secure tone)
Description:Do not allow a "protected" phone to have a shared line
Test Condition:ON INSERT/UPDATE IN Device, DeviceNumplanMap:
Error Message:Protected device can not support shared line.
Remedy:Protected device does not support shared line.
2.3.84.80 isrpidenabled (FI-3485)
Type:bool
Default Value:TRUE
Rule (RI-440):
Type:Active (Update)
Rule Name:Setting isRpidEnabled='F' sets sipdevice.tkpresentationbit_connectedline=DEFAULT
Description:When IsRpidEnabled is set to FALSE in the Device Table the tkPresentationBit_ConnectedLine will be set to DEFAULT (0x00) in sipdevice table
Test Condition:ON UPDATE in Device: IF IsRpidEnabled='F' THEN UPDATE SIPDEVICE SET tkPresentationBit_ConnectedLine = DEFAULT; END IF;
Error Message:Value of tkpresentationbit_connectedline is not Compatible
Rule (RI-441):
Type:Active (Update)
Rule Name:Setting IsRpidEnabled='F' sets SIPDevice.tkPresentationBit_ConnectedName=DEFAULT
Description:When IsRpidEnabled is set to FALSE in the Device Table the tkPresentationBit_ConnectedName will be set to DEFAULT (0x00) in SIPDevice table
Test Condition:ON UPDATE in Device: IF IsRPIDEnabled='F' THEN UPDATE SIPDevice SET tkPresentationBit_ConnectedName = DEFAULT; END IF;
Error Message:Value of tkpresentationbit_connectedname is not Compatible
2.3.84.81 isstandard (FI-3036)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:if set to true, then this device cannot be inserted or deleted, except by another business rule or the install
2.3.84.82 istrustedrelaypoint (FI-3479)
Type:bool
Default Value:FALSE
Remarks:Applies to MTP or transcoder that acts as Trusted Relay Point for virtual networks
Rule (RFI-163):
Type:Inter-field Condition and Constraint
Test Condition:tkClass != 5
Constraint:IsTrustedRelayPoint='f'
Remarks:IsTrustedRelayPoint can only be true for MTP or Transcoder device
2.3.84.83 md5hash (FI-3030)
Type:string [64] (Null OK)
Default Value:EMPTY
2.3.84.84 msisdn (FI-21325)
Type:string [31] (Indexed, Null OK)
Validation:^[]a-zA-Z0-9!#$%&()*+,.:;<=>?@[^_{|}~-]{0,30}$
Remarks:Mobile Device MSISDN.
2.3.84.85 mtprequired (FI-1320)
Type:bool
Default Value:FALSE
Rule (RI-405):
Type:Active (Update)
Rule Name:Setting MTPRequired='F' or fkMRL=NULL sets H323Device.EnableOutboundFaststart='F'
Description:When EnableOutboundFastStart is true for a H.323 device, the MTPRequired field must also be true, and a Media Resource Group List must be selected. If the MTPRequired is subsequently changed to False, or the Media Resource Group List is removed from the device, the EnableOutboundFaststart setting is automatically turned off.
Test Condition:ON UPDATE in Device: If (new_tkDeviceProtocol = 2) AND ( (new_MTPRequired = 'F' AND old_MTPRequired = 'T') OR (old_fkMediaResourceList IS NOT NULL AND new_fkMediaResourceList IS NULL) ) THEN UPDATE H323Device SET EnableOutboundFaststart = 'F' WHERE fkDevice = new_pkid AND EnableOutboundFaststart = 'T'; END IF;
Rule (RI-613):
Type:Validation (Insert/Update)
Rule Name:EMCC SIP Trunk validation
Description:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Test Condition:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Error Message:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
2.3.84.86 name (FI-2)
Type:string [129] (Unique, Indexed)
Migration Source:DeviceList.DeviceName
Remarks:URL friendly characters; 15 char for non MGCP devices else XXX@MGCPDomainName
Rule (RI-17):
Type:Validation (Insert/Update)
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-26):
Type:Validation (Insert/Update)
Rule Name:Device Name Validation
Description:For products that are configured as devices, name validation is based on the content of devicenameformat in specified for the product (TypeProduct). The exceptions are gateways for which the names are generated based on unit/subunit/slot position, and virtual devices used for extension mobility and configuration only (User Device Profiles, Autogenerated Profiles, Templates). Virtual devices allow ASCII names up to 50 characters including most punctuation.
Test Condition:ON INSERT/UPDATE IN Device
Error Message:The device name format is not valid or contains invalid characters.
Remedy:Check the name to make sure it is valid for specified product and try again.
Rule (RI-223):
Type:Active (Insert)
Rule Name:Add a VGC Gateway to MGCP on Device update
Description:On Insert only
Test Condition:?
Rule (RI-250):
Type:Active (Update)
Rule Name:Trim VG200 gateway name
Description:See CSCeg63298:VG200 gateway does not register with CCM. Need to trim leading and trailing spaces from devicename
Test Condition:?
Rule (RI-250):
Type:Active (Update)
This field is modified by this rule.
Rule Name:Trim VG200 gateway name
Description:See CSCeg63298:VG200 gateway does not register with CCM. Need to trim leading and trailing spaces from devicename
Test Condition:?
2.3.84.87 nationalprefix (FI-3512)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:National Prefix
Rule (RFI-183):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77)
Constraint:(NationalPrefix = '') OR (NationalPrefix = 'Default') OR (NationalPrefix = 'default')
Null Allowed:null
Remarks:National Prefix should be empty for devices other than H323 gateways and trunks and MGCP T1/E1 PRI and BRI gateways
Rule (RFI-255):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77)
Constraint:(NationalStripDigits = '') OR (NationalStripDigits IS NULL)
Null Allowed:null
Remarks:National Strip Digits should be empty for devices other than H323 gateways and trunks and MGCP T1/E1 PRI and BRI gateways
2.3.84.88 nationalstripdigits (FI-5111)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(NationalStripDigits >= 0) AND (NationalStripDigits <= 24)
Remarks:National Strip Digits
Rule (RFI-227):
Type:Inter-field Condition and Constraint
Test Condition:(NationalPrefix = 'Default') OR (NationalPrefix = 'default')
Constraint:NationalStripDigits IS NULL
Remarks:Cannot use StripDigits when the Default prefix is used.
2.3.84.89 ndescription (FI-21293)
Type:nstring (Indexed, Not Modifiable)
Default Value:EMPTY
Remarks:Copy of Description used for collating
Rule (RI-964):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Copy truncated version of device Description to device nDescription
Description:Up to 254 characters of device Description is copied to nDescription on inserts and updates. nDescription can be used for collated ordering.
Test Condition:ON INSERT/UPDATE set nDescription = description
2.3.84.90 networkholdmohaudiosourceid (FI-839)
Type:long (Null OK)
Default Value:NULL
Rule (RI-60):
Type:Validation (Insert/Update)
Rule Name:Network Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the Network Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Network Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a Network Hold Audio Source.
Rule (RI-60):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Network Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the Network Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Network Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a Network Hold Audio Source.
2.3.84.91 packetcaptureduration (FI-1911)
Type:long (Null OK)
Default Value:0
Check Constraint:(PacketCaptureDuration >= 0) AND (PacketCaptureDuration <= 300)
Remarks:Duration in minutes
2.3.84.92 pkid (FI-1)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-16):
Type:Validation (Insert/Update)
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-26):
Type:Validation (Insert/Update)
Rule Name:Device Name Validation
Description:For products that are configured as devices, name validation is based on the content of devicenameformat in specified for the product (TypeProduct). The exceptions are gateways for which the names are generated based on unit/subunit/slot position, and virtual devices used for extension mobility and configuration only (User Device Profiles, Autogenerated Profiles, Templates). Virtual devices allow ASCII names up to 50 characters including most punctuation.
Test Condition:ON INSERT/UPDATE IN Device
Error Message:The device name format is not valid or contains invalid characters.
Remedy:Check the name to make sure it is valid for specified product and try again.
Rule (RI-184):
Type:Validation (Insert/Update)
Rule Name:Insert/Update of Device for an MGCP Endpoint
Description:When a new MGCP endpoint device is created/ updated, the devicename should follow the name pattern for that device. This pattern is in Gateway layout table for that MGCP Product, slot position, MGCPSlotModule and MGCpVic.
Test Condition:On Insert or Update of MGCP Gateway endpoint.
Error Message:Device name format is not correct.
Rule (RI-199):
Type:Validation (Insert/Update)
Rule Name:Device Security Feature validation
Description:Valid Device Security Modes for each device type are determined by the ProductSupportsFeature records for the security features. Devices that do not support any security feature must be set to non-secure mode. Devices that support other security modes can be set to Default, Not-Secure, or one of the supported security modes (Authentication or Encryption as determined in ProductSupportsFeature).
Test Condition:On Insert/Update of tksecuritymode on Device table.
Error Message:The security feature is not supported for this device
Remedy:Either unselect the desired feature or choose another device.
Rule (RI-202):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate Default Device Profile for Model
Description:Create a Default Device Profile for a device type if one does not already exist, and extension mobility is enabled on a device of that type (e.g., create the Default Device Profile for a Cisco 7960 if it does not exist and EM is enabled on a 7960).
Test Condition:IF (NEW.AllowHotelingFlag is true) and ((select count(*) from device where tkmodel = NEW.tkmodel and tkdeviceprofile = 3) = 0)
Error Message:No default model profile, no mismatch login performed
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
Rule (RI-223):
Type:Active (Insert)
Rule Name:Add a VGC Gateway to MGCP on Device update
Description:On Insert only
Test Condition:?
Rule (RI-263):
Type:Active (Insert)
Rule Name:Set QSIG on Device
Description:When a device is inserted, the QSIG setting for the device is determined automatically as follows: For trunks other than Inter-cluster trunk, the device is treated as H.323; inter-cluster trunk is treated as Mixed-Non-QSIG. Digital Access PRI gateways using QSIG protocol are considered QSIG, H.323 Gateways are considered H.323, and all other gateways (including Digital Access PRI with a non-QSIG protocol) are Mixed-Non-QSIG. All other devices except Route Lists are considered Mixed-Non-QSIG. For Route Lists, see rule "Set QSIG on Route List"
Test Condition:On Insert into Device
Rule (RI-297):
Type:Validation (Insert/Update)
Rule Name:SRTP and Outbound Faststart Conflict
Description:The SRTPAllowed and EnableOutboundFastStart settings (for H.323 devices) are mutually exclusive - only one may be true at any given time.
Test Condition:IF (Device.SRTPAllowed = 't') AND (H323Device.EnableOutboundFastStart = 't') THEN throw exception
Error Message:SRTP and Outbound FastStart cannot be enabled at the same time.
Remedy:Disable either SRTP or Outbound FastStart and try again.
Rule (RI-305):
Type:Active (Insert)
Rule Name:device insert versionstamp
Description:on insert of a device, generate a deviceversionstamp record
Test Condition:insert device
Rule (RI-310):
Type:Active (Update)
Rule Name:(obsolete) Insert DeviceEMSyn record if auto sync of auto generated profile is needed
Description:When EM is on (Device.AllowHotelingFlag = true), if the default Device Profile is the auto generated Device Profile for the current device, and the value of service parameter (enableAutoDeviceProfileSynChronize) is true, then insert a record into DeviceEMSyn table with the pkid of auto-generated profile and the pkid of the current device. Later DbMon will process the change notification of DeviceEMSyn to re-generate the auto-generated profile of the current device.
Test Condition:Device.AllowHotelingFlag = true
Rule (RI-316):
Type:Active (Insert/Update)
Rule Name:Prevent applying secure profile where not supported.
Description:on I/U of Device
Test Condition:Only endpoints on gateways with secure mode support may be set to use Security Profiles marked for secure mode. Further, all endpoints on analog gateways must remain consistent in either all operating in secure mode or all in non-secure mode
Rule (RI-320):
Type:Validation (Insert/Update)
Rule Name:Device Restriction for SIP Dial Rules
Description:SIP Dial Rules for 7905/7912 may only be associated with 7905 and 7912 model phones. All other phones must use 7940/7960/TMP dial rules.
Test Condition:ON INSERT/UPDATE IN Device IF (DialRules.tkDialPattern = 0 and Device.tkProduct IS NOT IN (7905, 7912) OR DialRules.tkDialPattern == 1 AND Device.tkProduct IS IN (7905, 7912)) THEN throw exception
Error Message:Cannot assign Dial Rules of this type to the specified device (model and rule types are mismatched).
Remedy:Check the dial rule and device type to make sure they are compatible (e.g., 7905 dial rule for a 7905 device).
Rule (RI-336):
Type:Validation (Delete)
Rule Name:Deletion of In use Device Profile is not allowed
Description:on D of Device Profile
Test Condition:prevent deletion of device profile
Rule (RI-338):
Type:Validation (Insert)
Rule Name:One default profile per model
Description:Only one EM device default profile allowed per model
Test Condition:SELECT COUNT(*) FROM Device where tkdeviceprofile = 3 AND tkmodel = @tkmodel
Error Message:Only one device default profile is allowed per model
Rule (RI-339):
Type:Validation (Delete)
Rule Name:Device default profile cannot be deleted
Description:The device default profile cannot be deleted when there is still extension mobility enabled device for that model
Test Condition:IF EXISTS (SELECT name FROM Device where allowhotelingflag = 't' and tkmodel = @tkmodel)
Error Message:There is still some devices have extension mobility enabled for this model, device default profile cannot be deleted
Rule (RI-343):
Type:Validation (Insert/Update)
Rule Name:EM Logout Profile Model and Protocol Restriction
Description:The model and protocol of a phone and a User Device Profile selected as the logout profile must both match
Test Condition:ON INSERT/UPDATE IN Device IF (Device.tkModel <> Profile.tkModel) OR (Device.tkDeviceProtocol <> Profile.tkDeviceProtocol) THEN throw exception
Error Message:Logout Profile is not the same model and protocol as the device
Remedy:Select a logout profile that is the same model and protocol as the phone and try again
Rule (RI-359):
Type:Active (Delete)
Rule Name:Remove MGCP Member from MGCP when Device is Deleted
Description:When the endpoint device in an MGCP gateway is deleted, cascade the delete to the MGCPDeviceMember table if that record has not already been removed. MGCPDeviceMember and Device records should always be deleted together.
Test Condition:ON DELETE in Device: DELETE FROM MGCPDeviceMember WHERE fkDevice = @pkid
Rule (RI-372):
Type:Active (Insert)
Rule Name:Insert Dynamic Records for Device Table
Description:When a device record for a phone is inserted, insert records for DND, Privacy, Mobility and Hunt Group Log (Hlog) as needed based on product feature support.
Test Condition:ON INSERT INTO Device
Rule (RI-376):
Type:Active (Insert/Update)
Rule Name:Insert Dynamic Records for Extension Mobility
Description:When Extension Mobility (EM) is enabled on a phone, create the corresponding record in the ExtensionMobilityDynamic and EMCCDynamic and EMRemoteDynamic
Test Condition:ON INSERT/UPDATE INTO Device
Rule (RI-405):
Type:Active (Update)
Rule Name:Setting MTPRequired='F' or fkMRL=NULL sets H323Device.EnableOutboundFaststart='F'
Description:When EnableOutboundFastStart is true for a H.323 device, the MTPRequired field must also be true, and a Media Resource Group List must be selected. If the MTPRequired is subsequently changed to False, or the Media Resource Group List is removed from the device, the EnableOutboundFaststart setting is automatically turned off.
Test Condition:ON UPDATE in Device: If (new_tkDeviceProtocol = 2) AND ( (new_MTPRequired = 'F' AND old_MTPRequired = 'T') OR (old_fkMediaResourceList IS NOT NULL AND new_fkMediaResourceList IS NULL) ) THEN UPDATE H323Device SET EnableOutboundFaststart = 'F' WHERE fkDevice = new_pkid AND EnableOutboundFaststart = 'T'; END IF;
Rule (RI-411):
Type:Active (Update)
Rule Name:Device.fkEndUser_Mobility change removes RemoteDestinations
Description:When the EndUser associated with a Dual-mode or Remote Destination Profile device is changes, any Remote Destinations associated with that device are removed because the use data is no longer valid.
Test Condition:ON UPDATE IN Device: IF (NVL(old_fkenduser_mobility,'') <> NVL(new_fkenduser_mobility,'')) THEN DELETE FROM remotedestination WHERE (fkdevice_dualmode = old_pkid) OR (fkdevice_remotedestination = old_pkid) END IF;
Rule (RI-418):
Type:Active (Insert)
Rule Name:DeviceTFTPDynamic rebuildToggle
Description:update entry in DeviceTFTPDynamic
Test Condition:insert into DeviceTFTPDynamic
Rule (RI-423):
Type:Active (Delete)
Rule Name:Remove Individual phone templates
Description:When a phone with individual Phone Templates is deleted, the individual Phone Templates must be deleted.
Test Condition:ON DELETE in Device: if phonetemplate.name like '%Individual Template' DELETE FROM phonetemplate WHERE PhoneTemplate.pkid = device.fkphoneTemplate
Rule (RI-440):
Type:Active (Update)
Rule Name:Setting isRpidEnabled='F' sets sipdevice.tkpresentationbit_connectedline=DEFAULT
Description:When IsRpidEnabled is set to FALSE in the Device Table the tkPresentationBit_ConnectedLine will be set to DEFAULT (0x00) in sipdevice table
Test Condition:ON UPDATE in Device: IF IsRpidEnabled='F' THEN UPDATE SIPDEVICE SET tkPresentationBit_ConnectedLine = DEFAULT; END IF;
Error Message:Value of tkpresentationbit_connectedline is not Compatible
Rule (RI-441):
Type:Active (Update)
Rule Name:Setting IsRpidEnabled='F' sets SIPDevice.tkPresentationBit_ConnectedName=DEFAULT
Description:When IsRpidEnabled is set to FALSE in the Device Table the tkPresentationBit_ConnectedName will be set to DEFAULT (0x00) in SIPDevice table
Test Condition:ON UPDATE in Device: IF IsRPIDEnabled='F' THEN UPDATE SIPDevice SET tkPresentationBit_ConnectedName = DEFAULT; END IF;
Error Message:Value of tkpresentationbit_connectedname is not Compatible
Rule (RI-468):
Type:Active (Delete)
Rule Name:Remove default intercom device from Numplan when Device is Deleted
Description:When a device is deleted, update all Numplan records where this device is used as fkDevice_IntercomDefault
Test Condition:ON DELETE in Device: UPDATE Numplan set fkDevice_IntercomDefault = NULL WHERE fkDevice_IntercomDefault = @pkid
Rule (RI-473):
Type:Validation (Insert/Update)
Rule Name:DN restrictions for Protected device (secure tone)
Description:Do not allow a "protected" phone to have a shared line
Test Condition:ON INSERT/UPDATE IN Device, DeviceNumplanMap:
Error Message:Protected device can not support shared line.
Remedy:Protected device does not support shared line.
Rule (RI-484):
Type:Active (Update)
Rule Name:Clear RemoteDestination if Smart Client disabled
Description:If a Dual-mode device is configured with Mobile Smart Client enabled and a Remote Destination exists that is using the smart client, the RemoteDestination.fkDevice_MobileSmartClient field must be set to NULL if the Dual Mode is updated to disable the Mobile Smart Client (device.fkMobileSmartClientProfile is set to NULL).
Test Condition:ON UPDATE IN Device: IF (new_IsDualMode = 't') AND (new_fkMobileSmartClientProfile IS NULL) AND (old_fkMobileSmartClientProfile IS NOT NULL) THEN UPDATE RemoteDestination SET fkDevice_MobileSmartClient = NULL WHERE fkDevice_MobileSmartClient = new_pkid END IF;
Rule (RI-604):
Type:Validation (Update)
Rule Name:SAF Enabled trunk only supports non secure profile
Description:SAF Enabled trunk only supports non secure profile
Test Condition:SAF Enabled trunk only supports non secure profile
Error Message:SAF Enabled trunk only supports non secure profile
Rule (RI-613):
Type:Validation (Insert/Update)
Rule Name:EMCC SIP Trunk validation
Description:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Test Condition:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Error Message:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Rule (RI-711):
Type:Active (Update)
Rule Name:Configuration of E1 links that are PRI EURO protocol type for MLPP is allowed.
Description:If device is E1 and MLPP Indication <> 0 Or MLPP Preemption <> 0 Then if PriProtocol <> PRI_EURO then throw exception
Test Condition:On update of Device Table
Rule (RI-780):
Type:Active (Insert)
Rule Name:Devicerelatedversionstamp Update
Description:When a new Device is added, insert corresponding record in Devicerelatedversionstamp table with generated versionstamp.
Test Condition:ON INSERT IN Device : versionstamp = versionStampGenerator()
Rule (RI-785):
Type:Active (Insert)
Rule Name:Insert RemoteDestination Records for Device Table
Description:When a device record for a phone is inserted, insert records for RemoteDestination as needed based on product feature support(SUPPORTS_FEATURE_MOBILITY_SIPLINE).
Test Condition: SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 109 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Rule (RI-821):
Type:Active (Update)
Rule Name:when device.tkStatus_DeviceMobilityMode is set to 0 - off, then set the DeviceMobilityDynamic.fkDevicePool_DeviceMobility
Description:Need to add a rule that sets (UPDATE) the fkDevicePool_DeviceMobility to NULL when we disable the devicemobility of the device
Test Condition:ON UPDATE, IF(device.tkStatus_DeviceMobilityMode=0) Then DeviceMobilityDynamic.fkDevicePool_DeviceMobility= NULL;
Rule (RI-866):
Type:Active (Insert/Update)
Rule Name:Insert/Delete entry into DeviceCERDynamic
Description:When Device.RequireCERLocation is enabled,insert a record into DeviceCERDyanmic
Test Condition:ON UPDATE TO DEVICE.REQUIRECERLOCATION INSERT/DELETE INTO DEVICECERDYNAMIC
Rule (RI-874):
Type:Validation (Insert/Update)
Rule Name:Mobility Check on EndUser for CTI Remote Device
Description:EndUser associated with CTI Remote Device should be Mobility Enabled.
Test Condition:Check description for complete rule. ON INSERT INTO Device: SELECT fkenduser_mobility INTO theEndUser FROM device WHERE pkid = device.pkid; SELECT EnableMobility INTO mobility FROM enduser WHERE pkid = theEndUser; IF (mobility = 'F') THEN throw exception END IF;
Error Message:Cannot add the device for EndUser that does not have Mobility enabled.
Remedy:Enable Mobility on the EndUser associated with CTI Remote Device and try again.
Rule (RI-888):
Type:Active (Insert)
Rule Name:Insert Dynamic Records for Registration of Phones
Description:When a device record gets inserted where tkclass=1 (phone), create the corresponding record in the RegistrationDynamic table.
Test Condition:ON INSERT INTO Device: IF (tkClass = 1) THEN INSERT INTO RegistrationDynamic (pkid, fkDevice) values (newid(), new_pkid)
Rule (RI-936):
Type:Active (Insert/Update)
Rule Name:On Insert/Update of Device set SIPProfile to NULL for non SIP device
Description:On Insert/Update of Device, SET SIPProfile to NULL for non SIP device.
Test Condition:For INSERT/UPDATE of Device, IF tkdeviceprotocol <> 11,UPDATE Device SET fkSIPProfile = NULL
Rule (RI-941):
Type:Validation (Insert/Update)
Rule Name:Token User can own only CDT device
Description:Token User can own only CDT device or be used for mobility only for CDT
Test Condition:On I/U of Device: FOR fkEndUser or fkEndUser_Mobility ,If tkUserProfile=3 AND (tkModel<>645 AND tkProduct<>530) THEN THROW EXCEPTION
Error Message:Token EndUser can be associated with CDT only or used for mobility
Rule (RI-2137):
Type:Validation (Delete)
Rule Name:Self-Provisioing CTI RP deletion not allowed
Description:CTI RP selected in the self provisioning configuration cannot be deleted
Test Condition:On Delete (select count(*) from globalsetting where tkglobalsetting=TypeGlobalSetting.GLOBAL_SETTING_SELF_PROVISIONING_IVR_CTIROUTEPOINT and settingvalue=device.pkid) < 1
Error Message:This CTI Route Point is being used in the Self Provisioing Configuration hence cannot be deleted.
2.3.84.93 pstnaccess (FI-5271)
Type:bool
Default Value:FALSE
2.3.84.94 publickey (FI-2464)
Type:string [2048] (Null OK)
Default Value:NULL
2.3.84.95 remotedevice (FI-3168)
Type:bool
Default Value:FALSE
2.3.84.96 requirecerlocation (FI-10043)
Type:bool
Default Value:FALSE
Remarks:Enables CER tracking of the device
Rule (RI-866):
Type:Active (Insert/Update)
Rule Name:Insert/Delete entry into DeviceCERDynamic
Description:When Device.RequireCERLocation is enabled,insert a record into DeviceCERDyanmic
Test Condition:ON UPDATE TO DEVICE.REQUIRECERLOCATION INSERT/DELETE INTO DEVICECERDYNAMIC
Rule (RI-866):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Insert/Delete entry into DeviceCERDynamic
Description:When Device.RequireCERLocation is enabled,insert a record into DeviceCERDyanmic
Test Condition:ON UPDATE TO DEVICE.REQUIRECERLOCATION INSERT/DELETE INTO DEVICECERDYNAMIC
2.3.84.97 requiredtmfreception (FI-2462)
Type:bool
Default Value:FALSE
2.3.84.98 resettoggle (FI-3110)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
Rule (RI-305):
Type:Active (Insert)
Rule Name:device insert versionstamp
Description:on insert of a device, generate a deviceversionstamp record
Test Condition:insert device
2.3.84.99 retryvideocallasaudio (FI-1230)
Type:bool
Default Value:TRUE
2.3.84.100 rfc2833disabled (FI-2490)
Type:bool
Default Value:FALSE
2.3.84.101 routelistenabled (FI-1300)
Type:bool
Default Value:FALSE
Rule (RI-64):
Type:Validation (Insert/Update)
Rule Name:Route List Enabled Restriction
Description:Only Route List device may set the RouteListEnabled setting to true.
Test Condition:IF (@Device.RouteListEnabled = TRUE) AND (@Device.tkModel != 90) THEN throw exception
Error Message:Route List Enabled can be true only for Route List devices.
Remedy:Check device type and try again.
2.3.84.102 runonallnodes (FI-5853)
Type:bool
Default Value:FALSE
Remarks:The Run On All Nodes flag allows logical device definitions, (such as a SIP Trunk Handler Process), to be defined once and then marked to execute on each node. This reduces admin effort and inter-node handoff processing
Rule (RFI-284):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (37,77,95)
Constraint:RunOnAllNodes = 'f'
Remarks:Run On All Nodes can be enabled only for RouteList, Non-Gatekeeper Controlled Intercluster Trunk and SIP Trunk.
2.3.84.103 sendgeolocation (FI-5003)
Type:bool
Default Value:FALSE
Remarks:If true the GeoLocation is sent for the device else not
Rule (RI-613):
Type:Validation (Insert/Update)
Rule Name:EMCC SIP Trunk validation
Description:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Test Condition:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Error Message:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
2.3.84.104 specialloadinformation (FI-7)
Type:string [32] (Null OK)
Default Value:NULL
Migration Source:Set to NULL
Remarks:Used only by devices with firmware loads
Rule (RI-65):
Type:Validation (Insert/Update)
Rule Name:Special Load Information Restriction
Description:Special Load Information can only specified on a device that has a Firmware Load.
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 12 AND tkModel = @Device.tkModel
Error Message:Special Load Information can only specified on a device that has a Firmware Load.
Remedy:Check device type or remove Special Firmware Load information and try again.
2.3.84.105 srtpallowed (FI-3033)
Type:bool (Indexed)
Default Value:FALSE
Rule (RI-297):
Type:Validation (Insert/Update)
Rule Name:SRTP and Outbound Faststart Conflict
Description:The SRTPAllowed and EnableOutboundFastStart settings (for H.323 devices) are mutually exclusive - only one may be true at any given time.
Test Condition:IF (Device.SRTPAllowed = 't') AND (H323Device.EnableOutboundFastStart = 't') THEN throw exception
Error Message:SRTP and Outbound FastStart cannot be enabled at the same time.
Remedy:Disable either SRTP or Outbound FastStart and try again.
Rule (RI-297):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:SRTP and Outbound Faststart Conflict
Description:The SRTPAllowed and EnableOutboundFastStart settings (for H.323 devices) are mutually exclusive - only one may be true at any given time.
Test Condition:IF (Device.SRTPAllowed = 't') AND (H323Device.EnableOutboundFastStart = 't') THEN throw exception
Error Message:SRTP and Outbound FastStart cannot be enabled at the same time.
Remedy:Disable either SRTP or Outbound FastStart and try again.
2.3.84.106 srtpfallbackallowed (FI-3481)
Type:bool
Default Value:FALSE
Remarks:Allow fallback to Local SRTP
2.3.84.107 sshpassword (FI-2711)
Type:string [200]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{0,200}$
Remarks:SSH password for phone
2.3.84.108 sshuserid (FI-2712)
Type:string [50]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{0,50}$
Remarks:SSH userid for phone
2.3.84.109 subscriberprefix (FI-3515)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Subscriber Prefix
Rule (RFI-185):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77)
Constraint:(SubscriberPrefix = '') OR (SubscriberPrefix = 'Default') OR (SubscriberPrefix = 'default')
Null Allowed:null
Remarks:Subscriber Prefix should be empty for devices other than H323 gateways and trunks and MGCP T1/E1 PRI and BRI gateways
Rule (RFI-257):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77)
Constraint:(SubscriberStripDigits = '') OR (SubscriberStripDigits IS NULL)
Null Allowed:null
Remarks:Subscriber Strip Digits should be empty for devices other than H323 gateways and trunks and MGCP T1/E1 PRI and BRI gateways
2.3.84.110 subscriberstripdigits (FI-5114)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(SubscriberStripDigits >= 0) AND (SubscriberStripDigits <= 24)
Remarks:Subscriber Strip Digits
Rule (RFI-230):
Type:Inter-field Condition and Constraint
Test Condition:(SubscriberPrefix= 'Default') OR (SubscriberPrefix= 'default')
Constraint:SubscriberStripDigits IS NULL
Remarks:Cannot use SubscriberStripDigits when the Default prefix is used.
2.3.84.111 subunit (FI-926)
Type:long (Not Modifiable)
Default Value:0
2.3.84.112 tkbarge (FI-3466)
Type:enum
Default Value:3
Rule (RI-416):
Type:Validation (Insert/Update)
Rule Name:Single Button Barge Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkBarge
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Single Button Barge can only be set for devices that have the Single Button Barge Feature
Remedy:Check the Single Button Barge feature support and device type before specifying a Single Button Barge value.
Rule (RI-416):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Single Button Barge Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkBarge
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Single Button Barge can only be set for devices that have the Single Button Barge Feature
Remedy:Check the Single Button Barge feature support and device type before specifying a Single Button Barge value.
2.3.84.113 tkcalmode (FI-21055)
Type:enum (Null OK)
Remarks:user can assign confidential access level mode to the device
2.3.84.114 tkcertificateoperation (FI-2347)
Type:enum
Default Value:1
Remarks:Certificate Operation
2.3.84.115 tkcertificatestatus (FI-1914)
Type:enum
Default Value:1
2.3.84.116 tkclass (FI-146)
Type:enum
Migration Source:DeviceList.Type
Remarks:Redundant. Use tkModel to look up Class in TypeModel table.
Rule (RFI-14):
Type:Inter-field Condition and Constraint
Test Condition:RouteListEnabled = 't'
Constraint:tkClass = 7
Remarks:Make sure RouteListEnabled is enabled for RouteLists only
Rule (RFI-686):
Type:Inter-field Condition and Constraint
Test Condition:fkELINGroup is NOT NULL
Constraint:tkClass IN (1,10,253) OR tkmodel = 120
Remarks:fkELINGroup can only be set/updated to a non-NULL value for a Phone, CTI Route Point or FXS port on a Gateway
Rule (RI-25):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Set Device Profile and Class
Description:When a device is inserted as a Device Profile, the class of the device is changed to CLASS_DEVICE_PROFILE indicate it is a profile rather than a real device.
Test Condition:If (Device.tkDeviceProfile != 0) Then Set Device.tkClass = 254
Rule (RI-25):
Type:Active (Insert/Update)
Rule Name:Set Device Profile and Class
Description:When a device is inserted as a Device Profile, the class of the device is changed to CLASS_DEVICE_PROFILE indicate it is a profile rather than a real device.
Test Condition:If (Device.tkDeviceProfile != 0) Then Set Device.tkClass = 254
Rule (RI-66):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Set tkClass on Insert
Description:The class of a device is determined by the settings in the TypeModel table in the database. A device's class is set at insert and cannot be modified. Class is determined by Model, and Model is determined by Product.
Test Condition:SET Device.tkClass = (SELECT tkClass FROM TypeModel WHERE Enum = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct))
Rule (RI-66):
Type:Active (Insert)
Rule Name:Set tkClass on Insert
Description:The class of a device is determined by the settings in the TypeModel table in the database. A device's class is set at insert and cannot be modified. Class is determined by Model, and Model is determined by Product.
Test Condition:SET Device.tkClass = (SELECT tkClass FROM TypeModel WHERE Enum = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct))
Rule (RI-223):
Type:Active (Insert)
Rule Name:Add a VGC Gateway to MGCP on Device update
Description:On Insert only
Test Condition:?
Rule (RI-263):
Type:Active (Insert)
Rule Name:Set QSIG on Device
Description:When a device is inserted, the QSIG setting for the device is determined automatically as follows: For trunks other than Inter-cluster trunk, the device is treated as H.323; inter-cluster trunk is treated as Mixed-Non-QSIG. Digital Access PRI gateways using QSIG protocol are considered QSIG, H.323 Gateways are considered H.323, and all other gateways (including Digital Access PRI with a non-QSIG protocol) are Mixed-Non-QSIG. All other devices except Route Lists are considered Mixed-Non-QSIG. For Route Lists, see rule "Set QSIG on Route List"
Test Condition:On Insert into Device
Rule (RI-316):
Type:Active (Insert/Update)
Rule Name:Prevent applying secure profile where not supported.
Description:on I/U of Device
Test Condition:Only endpoints on gateways with secure mode support may be set to use Security Profiles marked for secure mode. Further, all endpoints on analog gateways must remain consistent in either all operating in secure mode or all in non-secure mode
Rule (RI-343):
Type:Validation (Insert/Update)
Rule Name:EM Logout Profile Model and Protocol Restriction
Description:The model and protocol of a phone and a User Device Profile selected as the logout profile must both match
Test Condition:ON INSERT/UPDATE IN Device IF (Device.tkModel <> Profile.tkModel) OR (Device.tkDeviceProtocol <> Profile.tkDeviceProtocol) THEN throw exception
Error Message:Logout Profile is not the same model and protocol as the device
Remedy:Select a logout profile that is the same model and protocol as the phone and try again
Rule (RI-372):
Type:Active (Insert)
Rule Name:Insert Dynamic Records for Device Table
Description:When a device record for a phone is inserted, insert records for DND, Privacy, Mobility and Hunt Group Log (Hlog) as needed based on product feature support.
Test Condition:ON INSERT INTO Device
Rule (RI-376):
Type:Active (Insert/Update)
Rule Name:Insert Dynamic Records for Extension Mobility
Description:When Extension Mobility (EM) is enabled on a phone, create the corresponding record in the ExtensionMobilityDynamic and EMCCDynamic and EMRemoteDynamic
Test Condition:ON INSERT/UPDATE INTO Device
Rule (RI-378):
Type:Validation (Insert)
Rule Name:Prevent too many phones in database.
Description:The number of allowed phones in the cluster has been exceeded. Total number of allowed phones = phones + 2 * EMCC phones and should be less than or equal to 700 phones for Cisco Unified Communications Manager Business Edition and 60000 phones for Cisco Unified Communications Manager.
Test Condition:ON INSERT INTO Device: Phones + (2 * EMCC phones) <= Max_Phones
Error Message:Total number of allowed phones should be less than or equal to 700 phones for Cisco Unified Communications Manager Business Edition and 60000 phones for Cisco Unified Communications Manager.
Remedy:Please reduce the number of phones or EMCC phones and try again.
Rule (RI-402):
Type:Active (Insert/Update)
Rule Name:Security Profile required if Standard Security Profile exists for device type, models will be automatically set to NULL
Description:If a Standard Security Profile exist for a given device type or class, then devices of that type or class must use a Security Profile.
Test Condition:ON INSERT/UPDATE INTO Device: IF (new_fkSecurityProfile IS NULL) THEN SELECT COUNT(*) INTO nRows FROM SecurityProfile where IsStandard = 't' AND tkModel = new_tkModel and tkDeviceProtocol = new_tkDeviceProtocol); IF nRows > 0 THEN throw exception;
Error Message:A security profile is required for this model and protocol.
Remedy:Specify a Security Profile that matches the device type.
Rule (RI-418):
Type:Active (Insert)
Rule Name:DeviceTFTPDynamic rebuildToggle
Description:update entry in DeviceTFTPDynamic
Test Condition:insert into DeviceTFTPDynamic
Rule (RI-423):
Type:Active (Delete)
Rule Name:Remove Individual phone templates
Description:When a phone with individual Phone Templates is deleted, the individual Phone Templates must be deleted.
Test Condition:ON DELETE in Device: if phonetemplate.name like '%Individual Template' DELETE FROM phonetemplate WHERE PhoneTemplate.pkid = device.fkphoneTemplate
Rule (RI-888):
Type:Active (Insert)
Rule Name:Insert Dynamic Records for Registration of Phones
Description:When a device record gets inserted where tkclass=1 (phone), create the corresponding record in the RegistrationDynamic table.
Test Condition:ON INSERT INTO Device: IF (tkClass = 1) THEN INSERT INTO RegistrationDynamic (pkid, fkDevice) values (newid(), new_pkid)
2.3.84.117 tkcountry (FI-996)
Type:enum (Null OK)
Default Value:NULL
Rule (RI-68):
Type:Validation (Insert/Update)
Rule Name:Device Country (Network Locale) Setting
Description:The valid Country (also called Network Locale) settings for a device are determined by the content of the ProductCapabilities table for that device type and feature. A locale must be installed or internally supported by the device to be valid. The ProductCapabilities table lists valid Countries for each device type.
Test Condition:@Device.tkCountry IN (SELECT EnumValue FROM ProductCapabilities WHERE (tkProductConfig = 32) AND (tkProduct = @Device.tkProduct))
Error Message:The specified Network Locale is not valid for this device.
Remedy:Check the locale support and device type and try again. It may be necessary to install the specified locale for this device.
2.3.84.118 tkdeviceprofile (FI-832)
Type:enum
Default Value:0
Remarks:Is this record a profile or real device
Rule (RI-24):
Type:Validation (Insert/Update)
Rule Name:Invalid Device Profile setting
Description:Only a phone that supports extension mobility can be configured as a device profile
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99) AND tkDeviceProfile != 0
Error Message:Device Profile can only be created for devices that support Extension Mobility feature.
Remedy:Check the device type and feature support and try again.
Rule (RI-25):
Type:Active (Insert/Update)
Rule Name:Set Device Profile and Class
Description:When a device is inserted as a Device Profile, the class of the device is changed to CLASS_DEVICE_PROFILE indicate it is a profile rather than a real device.
Test Condition:If (Device.tkDeviceProfile != 0) Then Set Device.tkClass = 254
Rule (RI-26):
Type:Validation (Insert/Update)
Rule Name:Device Name Validation
Description:For products that are configured as devices, name validation is based on the content of devicenameformat in specified for the product (TypeProduct). The exceptions are gateways for which the names are generated based on unit/subunit/slot position, and virtual devices used for extension mobility and configuration only (User Device Profiles, Autogenerated Profiles, Templates). Virtual devices allow ASCII names up to 50 characters including most punctuation.
Test Condition:ON INSERT/UPDATE IN Device
Error Message:The device name format is not valid or contains invalid characters.
Remedy:Check the name to make sure it is valid for specified product and try again.
Rule (RI-66):
Type:Active (Insert)
Rule Name:Set tkClass on Insert
Description:The class of a device is determined by the settings in the TypeModel table in the database. A device's class is set at insert and cannot be modified. Class is determined by Model, and Model is determined by Product.
Test Condition:SET Device.tkClass = (SELECT tkClass FROM TypeModel WHERE Enum = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct))
Rule (RI-336):
Type:Validation (Delete)
Rule Name:Deletion of In use Device Profile is not allowed
Description:on D of Device Profile
Test Condition:prevent deletion of device profile
Rule (RI-338):
Type:Validation (Insert)
Rule Name:One default profile per model
Description:Only one EM device default profile allowed per model
Test Condition:SELECT COUNT(*) FROM Device where tkdeviceprofile = 3 AND tkmodel = @tkmodel
Error Message:Only one device default profile is allowed per model
Rule (RI-339):
Type:Validation (Delete)
Rule Name:Device default profile cannot be deleted
Description:The device default profile cannot be deleted when there is still extension mobility enabled device for that model
Test Condition:IF EXISTS (SELECT name FROM Device where allowhotelingflag = 't' and tkmodel = @tkmodel)
Error Message:There is still some devices have extension mobility enabled for this model, device default profile cannot be deleted
Rule (RI-376):
Type:Active (Insert/Update)
Rule Name:Insert Dynamic Records for Extension Mobility
Description:When Extension Mobility (EM) is enabled on a phone, create the corresponding record in the ExtensionMobilityDynamic and EMCCDynamic and EMRemoteDynamic
Test Condition:ON INSERT/UPDATE INTO Device
Rule (RI-418):
Type:Active (Insert)
Rule Name:DeviceTFTPDynamic rebuildToggle
Description:update entry in DeviceTFTPDynamic
Test Condition:insert into DeviceTFTPDynamic
2.3.84.119 tkdeviceprotocol (FI-5)
Type:enum
Migration Source:DeviceList.Protocol
Rule (RI-16):
Type:Validation (Insert/Update)
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-17):
Type:Validation (Insert/Update)
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-19):
Type:Validation (Insert/Update)
Rule Name:AllowHotelingFlag - EM feature support required
Description:Device.AllowHotelingFlag can only be true for devices that support Extension Mobility.
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Extension Mobility can only turned on for devices that support Extension Mobility feature.
Remedy:Check device type and Extension Mobility feature support before enabling Extension Mobility.
Rule (RI-22):
Type:Validation (Insert/Update)
Rule Name:AAR feature support required
Description:Device.fkAARNeighorhood and Device.fkCallingSearchSpace_AAR can only be specified for devices that support the AAR feature
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 21 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:AAR Group and Calling Search Space can only be used for devices that support the AAR feature.
Remedy:Check device type and AAR feature support before specifying an AAR Group or AAR Calling Search Space.
Rule (RI-24):
Type:Validation (Insert/Update)
Rule Name:Invalid Device Profile setting
Description:Only a phone that supports extension mobility can be configured as a device profile
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99) AND tkDeviceProfile != 0
Error Message:Device Profile can only be created for devices that support Extension Mobility feature.
Remedy:Check the device type and feature support and try again.
Rule (RI-37):
Type:Validation (Insert/Update)
Rule Name:SoftkeyTemplate Restriction
Description:Softkey Templates can be assigned only to devices that support Softkeys
Test Condition:IF (@Device.fkSoftkeyTemplate IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 18 AND tkProduct = @Device.tkProduct AND tkDeviceprotocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Softkey Template is not valid for this type of device.
Remedy:Remove the Softkey Template setting and try again.
Rule (RI-41):
Type:Validation (Insert/Update)
Rule Name:(obsolete) Device Login Duration Restriction
Description:Login Duration is only valid on devices supporting Extension Mobility
Test Condition:IF (@Device.LoginDuration IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Login Duration is valid only for devices that support Extension Mobility feature.
Remedy:Remove the Login Duration setting from the device and try again.
Rule (RI-42):
Type:Validation (Insert/Update)
Rule Name:(obsolete) Device Login Time Restriction
Description:Login Time is only valid on devices supporting Extension Mobility
Test Condition:IF (@Device.LoginTime IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Login Time is valid only for devices that support Extension Mobility feature.
Remedy:Remove the Login Time setting from the device and try again.
Rule (RI-60):
Type:Validation (Insert/Update)
Rule Name:Network Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the Network Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Network Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a Network Hold Audio Source.
Rule (RI-61):
Type:Validation (Insert/Update)
Rule Name:User Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the User Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a User Hold Audio Source.
Rule (RI-69):
Type:Validation (Insert/Update)
Rule Name:Device Protocol Setting
Description:The valid Device Protocol settings for a device are determined by the content of the ProductCapabilities table for that device type and feature.
Test Condition:@Device.tkDeviceProtocol IN (SELECT EnumValue FROM ProductCapabilities WHERE (tkProductConfig = 7) AND (tkProduct = @Device.tkProduct))
Error Message:The specified Device Protocol is not valid for this device.
Remedy:Check the Device Protocol support and device type and try again..
Rule (RI-71):
Type:Active (Insert)
Rule Name:MLPP Preemption Default Setting
Description:If a product supports MLPP Preemption (SUPPORTS_FEATURE_PREEMPTION), then the Default value is PREEMPTION_DEFAULT; otherwise the default value is PREEMPTION_DISABLED
Test Condition:IF (SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0 THEN SET Device.tkPreemption = 0 ELSE SET Device.tkPreemption = 2
Rule (RI-72):
Type:Validation (Insert/Update)
Rule Name:MLPP Preemption Restriction
Description:Only devices that support MLPP Preemption feature may set the Preemption setting to a value other than DISABLED (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkPreemption != 0) THEN throw exception
Error Message:MLPP Preemption must be disabled on devices that do not support the MLPP Preemption feature.
Remedy:Check the MLPP Preemption feature support and device type and try again.
Rule (RI-74):
Type:Validation (Insert/Update)
Rule Name:MLPP Indication Restriction
Description:Only devices that support MLPP Indication feature may set the Indication setting to a value other than OFF (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 34 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkStatus_MLPPIndicationStatus != 0) THEN throw exception
Error Message:MLPP Indication must be off on devices that do not support the MLPP Indication feature.
Remedy:Check the MLPP Indication feature support and device type and try again.
Rule (RI-75):
Type:Validation (Insert/Update)
Rule Name:User Locale Restriction
Description:Only devices that support Localization feature use the User Locale setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 17 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Locale can only be set for devices that support the Localization feature.
Remedy:Check the Localization feature support and device type before specifying a User Locale.
Rule (RI-106):
Type:Documentation (Developer notes only)
Rule Name:DigitalAccessBri record required
Description:Devices with the Digital Access BRI Device Protocol should always have a corresponding record in the DigitalAccessBri table.
Test Condition:Device.tkDeviceProtocol = 10
Rule (RI-107):
Type:Documentation (Developer notes only)
Rule Name:DigitalAccessPri record required
Description:Devices with the Digital Access PRI Device Protocol should always have a corresponding record in the DigitalAccessPri table.
Test Condition:Device.tkDeviceProtocol = 1
Rule (RI-110):
Type:Documentation (Developer notes only)
Rule Name:DigitalAccessT1 record required
Description:Devices with the Digital Access T1 Device Protocol should always have a corresponding record in the DigitalAccessT1 table, and port information in the DigitalAccessT1Port table.
Test Condition:Device.tkDeviceProtocol = 4
Rule (RI-263):
Type:Active (Insert)
Rule Name:Set QSIG on Device
Description:When a device is inserted, the QSIG setting for the device is determined automatically as follows: For trunks other than Inter-cluster trunk, the device is treated as H.323; inter-cluster trunk is treated as Mixed-Non-QSIG. Digital Access PRI gateways using QSIG protocol are considered QSIG, H.323 Gateways are considered H.323, and all other gateways (including Digital Access PRI with a non-QSIG protocol) are Mixed-Non-QSIG. All other devices except Route Lists are considered Mixed-Non-QSIG. For Route Lists, see rule "Set QSIG on Route List"
Test Condition:On Insert into Device
Rule (RI-297):
Type:Validation (Insert/Update)
Rule Name:SRTP and Outbound Faststart Conflict
Description:The SRTPAllowed and EnableOutboundFastStart settings (for H.323 devices) are mutually exclusive - only one may be true at any given time.
Test Condition:IF (Device.SRTPAllowed = 't') AND (H323Device.EnableOutboundFastStart = 't') THEN throw exception
Error Message:SRTP and Outbound FastStart cannot be enabled at the same time.
Remedy:Disable either SRTP or Outbound FastStart and try again.
Rule (RI-316):
Type:Active (Insert/Update)
Rule Name:Prevent applying secure profile where not supported.
Description:on I/U of Device
Test Condition:Only endpoints on gateways with secure mode support may be set to use Security Profiles marked for secure mode. Further, all endpoints on analog gateways must remain consistent in either all operating in secure mode or all in non-secure mode
Rule (RI-320):
Type:Validation (Insert/Update)
Rule Name:Device Restriction for SIP Dial Rules
Description:SIP Dial Rules for 7905/7912 may only be associated with 7905 and 7912 model phones. All other phones must use 7940/7960/TMP dial rules.
Test Condition:ON INSERT/UPDATE IN Device IF (DialRules.tkDialPattern = 0 and Device.tkProduct IS NOT IN (7905, 7912) OR DialRules.tkDialPattern == 1 AND Device.tkProduct IS IN (7905, 7912)) THEN throw exception
Error Message:Cannot assign Dial Rules of this type to the specified device (model and rule types are mismatched).
Remedy:Check the dial rule and device type to make sure they are compatible (e.g., 7905 dial rule for a 7905 device).
Rule (RI-338):
Type:Validation (Insert)
Rule Name:One default profile per model
Description:Only one EM device default profile allowed per model
Test Condition:SELECT COUNT(*) FROM Device where tkdeviceprofile = 3 AND tkmodel = @tkmodel
Error Message:Only one device default profile is allowed per model
Rule (RI-339):
Type:Validation (Delete)
Rule Name:Device default profile cannot be deleted
Description:The device default profile cannot be deleted when there is still extension mobility enabled device for that model
Test Condition:IF EXISTS (SELECT name FROM Device where allowhotelingflag = 't' and tkmodel = @tkmodel)
Error Message:There is still some devices have extension mobility enabled for this model, device default profile cannot be deleted
Rule (RI-340):
Type:Validation (Insert/Update)
Rule Name:Correct security profile for device
Description:on I/U of device
Test Condition:prevent bad value combinations
Rule (RI-343):
Type:Validation (Insert/Update)
Rule Name:EM Logout Profile Model and Protocol Restriction
Description:The model and protocol of a phone and a User Device Profile selected as the logout profile must both match
Test Condition:ON INSERT/UPDATE IN Device IF (Device.tkModel <> Profile.tkModel) OR (Device.tkDeviceProtocol <> Profile.tkDeviceProtocol) THEN throw exception
Error Message:Logout Profile is not the same model and protocol as the device
Remedy:Select a logout profile that is the same model and protocol as the phone and try again
Rule (RI-379):
Type:Validation (Insert/Update)
Rule Name:Device DND Option feature restriction
Description:DND Option can only be set to non-Zero on devices that support the DND feature (in ProductSupportsFeature table). For those devices that support the feature, only the Ringer Off (0) is valid, unless a parameter is present in the PSF record. If a parameter value of 1 exists in PSF table, only Call Reject is valid. If the param value is (2), all options including Use Common Profile (2) are valid. Dual mode and remote destination profile only support the Call Reject option.
Test Condition:ON INSERT INTO Device: IF((tkproduct=112 or isdualmode = 't') and (tkDNDOption <>1)) throw exception; ELSE IF (new_tkDNDOption <> 0) THEN SELECT parameter INTO restriction FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_DND) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99); IF (rows returned = 0) THEN throw exception ELSE IF (NVL(restriction, '') <> '') THEN IF (new_tkDNDOption <> restriction) THEN throw exception END IF; END IF; END IF; END IF
Error Message:This device does not support the selected DND Option
Remedy:Do not set a DND Option, or check for restrictions on which options are valid for this device.
Rule (RI-381):
Type:Active (Insert)
Rule Name:DualMode device type (in PSF) is marked isDualMode = True
Description:If a device type is marked as Dual Mode in the ProductSupportsFeature table, then the Device and RemoteDestination records for the device are automatically updated to set IsDualMode field to true.
Test Condition:ON INSERT INTO Device
Rule (RI-395):
Type:Validation (Insert/Update)
Rule Name:Device Outbound Call Rollover Feature Restriction
Description:The Device.tkOutboundCallRollover setting can only be non-default (other than None) for devices that support the Automatic Outbound Call Rollover feature.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkOutboundCallRollover <> 0) THEN IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_AUTOMATIC_OUTBOUND_CALL_ROLLOVER) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99) = 0 THEN throw exception; END IF; END IF;
Error Message:This device does not supports Automatic Outbound Call Rollover.
Remedy:Set the OutboundCallRollover option to No Rollover for this device.
Rule (RI-402):
Type:Active (Insert/Update)
Rule Name:Security Profile required if Standard Security Profile exists for device type, models will be automatically set to NULL
Description:If a Standard Security Profile exist for a given device type or class, then devices of that type or class must use a Security Profile.
Test Condition:ON INSERT/UPDATE INTO Device: IF (new_fkSecurityProfile IS NULL) THEN SELECT COUNT(*) INTO nRows FROM SecurityProfile where IsStandard = 't' AND tkModel = new_tkModel and tkDeviceProtocol = new_tkDeviceProtocol); IF nRows > 0 THEN throw exception;
Error Message:A security profile is required for this model and protocol.
Remedy:Specify a Security Profile that matches the device type.
Rule (RI-405):
Type:Active (Update)
Rule Name:Setting MTPRequired='F' or fkMRL=NULL sets H323Device.EnableOutboundFaststart='F'
Description:When EnableOutboundFastStart is true for a H.323 device, the MTPRequired field must also be true, and a Media Resource Group List must be selected. If the MTPRequired is subsequently changed to False, or the Media Resource Group List is removed from the device, the EnableOutboundFaststart setting is automatically turned off.
Test Condition:ON UPDATE in Device: If (new_tkDeviceProtocol = 2) AND ( (new_MTPRequired = 'F' AND old_MTPRequired = 'T') OR (old_fkMediaResourceList IS NOT NULL AND new_fkMediaResourceList IS NULL) ) THEN UPDATE H323Device SET EnableOutboundFaststart = 'F' WHERE fkDevice = new_pkid AND EnableOutboundFaststart = 'T'; END IF;
Rule (RI-415):
Type:Validation (Insert/Update)
Rule Name:Join Across Lines Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkStatus_joinacrosslines
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Join Across Lines can only be set for devices that have the Join Across Lines Feature
Remedy:Check the Join Across Lines feature support and device type before specifying a Join Across Lines value.
Rule (RI-416):
Type:Validation (Insert/Update)
Rule Name:Single Button Barge Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkBarge
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Single Button Barge can only be set for devices that have the Single Button Barge Feature
Remedy:Check the Single Button Barge feature support and device type before specifying a Single Button Barge value.
Rule (RI-431):
Type:Validation (Insert/Update)
Rule Name:Phone Personalization Feature Support restriction
Description:Only devices that support the Phone Personalization can have a non-default value for Device.tkPhonePersonalization.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkPhonePersonalization <> 3) AND (SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 80 AND tkProduct = new_tkProduct AND tkDeviceProtocol IN (99, new_tkDeviceProtocol) = 0 THEN throw exception; END IF
Error Message:Phone Personalization feature is not supported on the specified device type.
Remedy:Do not change the setting (tkPhonePersonalization) from Default (value = 3)
Rule (RI-471):
Type:Validation (Insert/Update)
Rule Name:Secure Tone support required for Protected device
Description:IsProtected setting can only be true for devices supporting secure tone feature (tkSupportsFeature = 81)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support secure tone (isprotected setting)
Remedy:Set IsProtected to false and try again
Rule (RI-631):
Type:Validation (Insert/Update)
Rule Name:Hotline support required for Hotline Device
Description:Hotline Device setting can only be true for devices supporting Hotline feature (tkSupportsFeature = 93)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support Hotline (hotlinedevice setting)
Remedy:Set hotlinedevice to false and try again
Rule (RI-734):
Type:Validation (Insert/Update)
Rule Name:Device Table Feature Control Policy Restriction
Description:Only devices that support Feature Control Policy can specify fkFeatureControlPolicy
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 103 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Feature Control Policy can be set for devices that supports the Feature Control Policy
Remedy:Check Feature Control Policy feature support and device type before specifying a value for fkFeatureControlPolicy.
Rule (RI-785):
Type:Active (Insert)
Rule Name:Insert RemoteDestination Records for Device Table
Description:When a device record for a phone is inserted, insert records for RemoteDestination as needed based on product feature support(SUPPORTS_FEATURE_MOBILITY_SIPLINE).
Test Condition: SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 109 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Rule (RI-844):
Type:Active (Insert/Update)
Rule Name:IMS-integrated Mobile Owner Syncs with Mobility User
Description:For IMS-integrated Mobile devices (as defined in ProductSupportsFeature), the owner (device.fkenduser) and mobility user (device.fkenduser_mobility) must be in sync. Sync owner to mobility user if it's not set.
Test Condition:ON INSERT/UPDATE in Device: IF (old_fkenduer_mobility <> new_fkenduser_mobility) THEN set fkenduser = new_fkenduser_mobility END IF;
Rule (RI-866):
Type:Active (Insert/Update)
Rule Name:Insert/Delete entry into DeviceCERDynamic
Description:When Device.RequireCERLocation is enabled,insert a record into DeviceCERDyanmic
Test Condition:ON UPDATE TO DEVICE.REQUIRECERLOCATION INSERT/DELETE INTO DEVICECERDYNAMIC
Rule (RI-936):
Type:Active (Insert/Update)
Rule Name:On Insert/Update of Device set SIPProfile to NULL for non SIP device
Description:On Insert/Update of Device, SET SIPProfile to NULL for non SIP device.
Test Condition:For INSERT/UPDATE of Device, IF tkdeviceprotocol <> 11,UPDATE Device SET fkSIPProfile = NULL
Rule (RI-940):
Type:Validation (Insert/Update)
Rule Name:Model Independent Security Profile
Description:Check if the device supports Model independent security profile , if yes then check whether this device support features like Encryption,Authentication and File Encryption and if it doesn't supports any of these three features then set its security profile as the Standard Non-Secure security profile intended for that particular model.
Test Condition:ON INSERT/UPDATE INTO Device: SELECT tkSecurityPolicy INTO m_tkSecurityPolicy FROM SecurityProfile WHERE pkid = new_fkSecurityProfile; IF device supports Model Independent Security Profile (m_tkSecurityProfile =99) THEN IF there exists a record in PSF table for each supporting feature: Encryption, Authentication, File Encryption with tkDeviceProtocol in (new_tkDeviceProtocol,99) and tkModel = new_tkModel THEN RETURN new_fkSecurityProfile; ELSE SELECT pkid INTO m_fkSecurityProfile FROM SecurityProfile WHERE tkmodel = new_tkModel AND tkDeviceProtocol = new_tkDeviceProtocol AND isStandard = 't';RETURN m_fkSecurityProfile;
Remedy:1
Rule (RI-946):
Type:Active (Insert/Update)
Rule Name:Auto-fix for Dual Mode and Mobile Smart Client device settings
Description:IF autofix is enabled AND IsDualMode='t' THEN SET tkRingSeting_DND = 1 i.e. disabled AND OR IF tkDevicePotocol=17 (MobileSmartClient) THEN SET tkRingSeting_DND = 1 i.e. disabled AND SET fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Test Condition:IF g_enable_auto_fix = 't' AND IsDualMode='t' THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=NULL OR IF tkDevicePotocol=17 THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
2.3.84.120 tkdevicetrustmode (FI-9824)
Type:enum
Default Value:0
Remarks:Allows for administrative control of the display of secure icon for specified device types. Options are Trusted and Not Trusted.
2.3.84.121 tkdndoption (FI-3287)
Type:enum
Default Value:0
Remarks:Type of call handling while DND is enabled (0=Ringer Off, 1=Call Reject); depends on product support; overrides CommonPhoneConfig setting
Rule (RI-379):
Type:Validation (Insert/Update)
Rule Name:Device DND Option feature restriction
Description:DND Option can only be set to non-Zero on devices that support the DND feature (in ProductSupportsFeature table). For those devices that support the feature, only the Ringer Off (0) is valid, unless a parameter is present in the PSF record. If a parameter value of 1 exists in PSF table, only Call Reject is valid. If the param value is (2), all options including Use Common Profile (2) are valid. Dual mode and remote destination profile only support the Call Reject option.
Test Condition:ON INSERT INTO Device: IF((tkproduct=112 or isdualmode = 't') and (tkDNDOption <>1)) throw exception; ELSE IF (new_tkDNDOption <> 0) THEN SELECT parameter INTO restriction FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_DND) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99); IF (rows returned = 0) THEN throw exception ELSE IF (NVL(restriction, '') <> '') THEN IF (new_tkDNDOption <> restriction) THEN throw exception END IF; END IF; END IF; END IF
Error Message:This device does not support the selected DND Option
Remedy:Do not set a DND Option, or check for restrictions on which options are valid for this device.
Rule (RI-379):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Device DND Option feature restriction
Description:DND Option can only be set to non-Zero on devices that support the DND feature (in ProductSupportsFeature table). For those devices that support the feature, only the Ringer Off (0) is valid, unless a parameter is present in the PSF record. If a parameter value of 1 exists in PSF table, only Call Reject is valid. If the param value is (2), all options including Use Common Profile (2) are valid. Dual mode and remote destination profile only support the Call Reject option.
Test Condition:ON INSERT INTO Device: IF((tkproduct=112 or isdualmode = 't') and (tkDNDOption <>1)) throw exception; ELSE IF (new_tkDNDOption <> 0) THEN SELECT parameter INTO restriction FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_DND) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99); IF (rows returned = 0) THEN throw exception ELSE IF (NVL(restriction, '') <> '') THEN IF (new_tkDNDOption <> restriction) THEN throw exception END IF; END IF; END IF; END IF
Error Message:This device does not support the selected DND Option
Remedy:Do not set a DND Option, or check for restrictions on which options are valid for this device.
2.3.84.122 tkdtmfsignaling (FI-2399)
Type:enum
Default Value:1
Rule (RI-331):
Type:Validation (Insert/Update)
Rule Name:device.tkdtmfsignaling validation
Description:on insert or change to DTMF setting for SIP trunk make sure that out-of-band is not set since it is invalid value
Test Condition:update device
2.3.84.123 tkkeyauthority (FI-3013)
Type:enum
Default Value:0
Remarks:TypeKeyAuthority
2.3.84.124 tkmodel (FI-4)
Type:enum (Not Modifiable)
Migration Source:DeviceList.Type
Remarks:Redundant. Use tkProduct to look up tkModel in TypeProduct table.
Rule (RI-16):
Type:Validation (Insert/Update)
Rule Name:Phone Template required
Description:Devices that use a phone button template must have a template specified
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 13 AND tkModel = @Defaults.tkModel AND tkDeviceProtocol IN (@Defaults.tkDeviceProtocol,99)
Error Message:A device that uses Phone Templates have a specific Phone Template assigned.
Remedy:Specify a Phone Template.
Rule (RI-17):
Type:Validation (Insert/Update)
Rule Name:Phone Template Model
Description:The model must match for a device default and the specified phone template for that device type.
Test Condition:@Defaults.tkModel = (SELECT PhoneTemplate.tkModel FROM PhoneTemplate WHERE PhoneTemplate.pkid = @Defaults.tkPhoneTemplate)
Error Message:The Phone Template model does not match the device model.
Remedy:Specifiy a Phone Template for the correct model.
Rule (RI-26):
Type:Validation (Insert/Update)
Rule Name:Device Name Validation
Description:For products that are configured as devices, name validation is based on the content of devicenameformat in specified for the product (TypeProduct). The exceptions are gateways for which the names are generated based on unit/subunit/slot position, and virtual devices used for extension mobility and configuration only (User Device Profiles, Autogenerated Profiles, Templates). Virtual devices allow ASCII names up to 50 characters including most punctuation.
Test Condition:ON INSERT/UPDATE IN Device
Error Message:The device name format is not valid or contains invalid characters.
Remedy:Check the name to make sure it is valid for specified product and try again.
Rule (RI-64):
Type:Validation (Insert/Update)
Rule Name:Route List Enabled Restriction
Description:Only Route List device may set the RouteListEnabled setting to true.
Test Condition:IF (@Device.RouteListEnabled = TRUE) AND (@Device.tkModel != 90) THEN throw exception
Error Message:Route List Enabled can be true only for Route List devices.
Remedy:Check device type and try again.
Rule (RI-67):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Set tkModel on Insert
Description:The model of a device is determined by the settings in the TypeProduct table in the database. A device's model is set at insert and cannot be modified.
Test Condition:SET Device.tkModel = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct)
Rule (RI-67):
Type:Active (Insert)
Rule Name:Set tkModel on Insert
Description:The model of a device is determined by the settings in the TypeProduct table in the database. A device's model is set at insert and cannot be modified.
Test Condition:SET Device.tkModel = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct)
Rule (RI-202):
Type:Active (Insert/Update/Delete records)
Rule Name:Generate Default Device Profile for Model
Description:Create a Default Device Profile for a device type if one does not already exist, and extension mobility is enabled on a device of that type (e.g., create the Default Device Profile for a Cisco 7960 if it does not exist and EM is enabled on a 7960).
Test Condition:IF (NEW.AllowHotelingFlag is true) and ((select count(*) from device where tkmodel = NEW.tkmodel and tkdeviceprofile = 3) = 0)
Error Message:No default model profile, no mismatch login performed
Rule (RI-223):
Type:Active (Insert)
Rule Name:Add a VGC Gateway to MGCP on Device update
Description:On Insert only
Test Condition:?
Rule (RI-263):
Type:Active (Insert)
Rule Name:Set QSIG on Device
Description:When a device is inserted, the QSIG setting for the device is determined automatically as follows: For trunks other than Inter-cluster trunk, the device is treated as H.323; inter-cluster trunk is treated as Mixed-Non-QSIG. Digital Access PRI gateways using QSIG protocol are considered QSIG, H.323 Gateways are considered H.323, and all other gateways (including Digital Access PRI with a non-QSIG protocol) are Mixed-Non-QSIG. All other devices except Route Lists are considered Mixed-Non-QSIG. For Route Lists, see rule "Set QSIG on Route List"
Test Condition:On Insert into Device
Rule (RI-316):
Type:Active (Insert/Update)
Rule Name:Prevent applying secure profile where not supported.
Description:on I/U of Device
Test Condition:Only endpoints on gateways with secure mode support may be set to use Security Profiles marked for secure mode. Further, all endpoints on analog gateways must remain consistent in either all operating in secure mode or all in non-secure mode
Rule (RI-320):
Type:Validation (Insert/Update)
Rule Name:Device Restriction for SIP Dial Rules
Description:SIP Dial Rules for 7905/7912 may only be associated with 7905 and 7912 model phones. All other phones must use 7940/7960/TMP dial rules.
Test Condition:ON INSERT/UPDATE IN Device IF (DialRules.tkDialPattern = 0 and Device.tkProduct IS NOT IN (7905, 7912) OR DialRules.tkDialPattern == 1 AND Device.tkProduct IS IN (7905, 7912)) THEN throw exception
Error Message:Cannot assign Dial Rules of this type to the specified device (model and rule types are mismatched).
Remedy:Check the dial rule and device type to make sure they are compatible (e.g., 7905 dial rule for a 7905 device).
Rule (RI-338):
Type:Validation (Insert)
Rule Name:One default profile per model
Description:Only one EM device default profile allowed per model
Test Condition:SELECT COUNT(*) FROM Device where tkdeviceprofile = 3 AND tkmodel = @tkmodel
Error Message:Only one device default profile is allowed per model
Rule (RI-339):
Type:Validation (Delete)
Rule Name:Device default profile cannot be deleted
Description:The device default profile cannot be deleted when there is still extension mobility enabled device for that model
Test Condition:IF EXISTS (SELECT name FROM Device where allowhotelingflag = 't' and tkmodel = @tkmodel)
Error Message:There is still some devices have extension mobility enabled for this model, device default profile cannot be deleted
Rule (RI-340):
Type:Validation (Insert/Update)
Rule Name:Correct security profile for device
Description:on I/U of device
Test Condition:prevent bad value combinations
Rule (RI-343):
Type:Validation (Insert/Update)
Rule Name:EM Logout Profile Model and Protocol Restriction
Description:The model and protocol of a phone and a User Device Profile selected as the logout profile must both match
Test Condition:ON INSERT/UPDATE IN Device IF (Device.tkModel <> Profile.tkModel) OR (Device.tkDeviceProtocol <> Profile.tkDeviceProtocol) THEN throw exception
Error Message:Logout Profile is not the same model and protocol as the device
Remedy:Select a logout profile that is the same model and protocol as the phone and try again
Rule (RI-402):
Type:Active (Insert/Update)
Rule Name:Security Profile required if Standard Security Profile exists for device type, models will be automatically set to NULL
Description:If a Standard Security Profile exist for a given device type or class, then devices of that type or class must use a Security Profile.
Test Condition:ON INSERT/UPDATE INTO Device: IF (new_fkSecurityProfile IS NULL) THEN SELECT COUNT(*) INTO nRows FROM SecurityProfile where IsStandard = 't' AND tkModel = new_tkModel and tkDeviceProtocol = new_tkDeviceProtocol); IF nRows > 0 THEN throw exception;
Error Message:A security profile is required for this model and protocol.
Remedy:Specify a Security Profile that matches the device type.
Rule (RI-940):
Type:Validation (Insert/Update)
Rule Name:Model Independent Security Profile
Description:Check if the device supports Model independent security profile , if yes then check whether this device support features like Encryption,Authentication and File Encryption and if it doesn't supports any of these three features then set its security profile as the Standard Non-Secure security profile intended for that particular model.
Test Condition:ON INSERT/UPDATE INTO Device: SELECT tkSecurityPolicy INTO m_tkSecurityPolicy FROM SecurityProfile WHERE pkid = new_fkSecurityProfile; IF device supports Model Independent Security Profile (m_tkSecurityProfile =99) THEN IF there exists a record in PSF table for each supporting feature: Encryption, Authentication, File Encryption with tkDeviceProtocol in (new_tkDeviceProtocol,99) and tkModel = new_tkModel THEN RETURN new_fkSecurityProfile; ELSE SELECT pkid INTO m_fkSecurityProfile FROM SecurityProfile WHERE tkmodel = new_tkModel AND tkDeviceProtocol = new_tkDeviceProtocol AND isStandard = 't';RETURN m_fkSecurityProfile;
Remedy:1
Rule (RI-2129):
Type:Validation (Insert/Update)
Rule Name:Rule to validate INSERT/UPDATE on column EnableCallRoutingToRdWhenNoneIsActive
Description:INSERT/UPDATE operation to set value of new column to true should be rejected for all devices except CTI Remote Device
Error Message:Cannot perform insert/update operation as the current value is not applicable to the device type
Rule (RI-2155):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of Device, Set fkDevicePool=NULL for TelePresence Conference devices
Description:On Insert/Update of Device, make sure the fkDevicePool is NULL for TelePresence Conference devices
Test Condition:ON INSERT/UPDATE: IF fkDevicePool IS NOT NULL Set fkDevicePool to NULL
2.3.84.125 tknetworklocation (FI-2164)
Type:enum
Default Value:2
Remarks:Stores OffNet/OnNet info
2.3.84.126 tkoutboundcallrollover (FI-3422)
Type:enum
Default Value:0
Remarks:Determines rollover behavior of phones when MaxNumCalls is exceeded on a line and a new call is started
Rule (RI-395):
Type:Validation (Insert/Update)
Rule Name:Device Outbound Call Rollover Feature Restriction
Description:The Device.tkOutboundCallRollover setting can only be non-default (other than None) for devices that support the Automatic Outbound Call Rollover feature.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkOutboundCallRollover <> 0) THEN IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_AUTOMATIC_OUTBOUND_CALL_ROLLOVER) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99) = 0 THEN throw exception; END IF; END IF;
Error Message:This device does not supports Automatic Outbound Call Rollover.
Remedy:Set the OutboundCallRollover option to No Rollover for this device.
Rule (RI-395):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Device Outbound Call Rollover Feature Restriction
Description:The Device.tkOutboundCallRollover setting can only be non-default (other than None) for devices that support the Automatic Outbound Call Rollover feature.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkOutboundCallRollover <> 0) THEN IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_AUTOMATIC_OUTBOUND_CALL_ROLLOVER) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99) = 0 THEN throw exception; END IF; END IF;
Error Message:This device does not supports Automatic Outbound Call Rollover.
Remedy:Set the OutboundCallRollover option to No Rollover for this device.
2.3.84.127 tkpacketcapturemode (FI-1910)
Type:enum
Default Value:0
2.3.84.128 tkphonepersonalization (FI-3456)
Type:enum
Default Value:3
Rule (RI-431):
Type:Validation (Insert/Update)
Rule Name:Phone Personalization Feature Support restriction
Description:Only devices that support the Phone Personalization can have a non-default value for Device.tkPhonePersonalization.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkPhonePersonalization <> 3) AND (SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 80 AND tkProduct = new_tkProduct AND tkDeviceProtocol IN (99, new_tkDeviceProtocol) = 0 THEN throw exception; END IF
Error Message:Phone Personalization feature is not supported on the specified device type.
Remedy:Do not change the setting (tkPhonePersonalization) from Default (value = 3)
Rule (RI-431):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Phone Personalization Feature Support restriction
Description:Only devices that support the Phone Personalization can have a non-default value for Device.tkPhonePersonalization.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkPhonePersonalization <> 3) AND (SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 80 AND tkProduct = new_tkProduct AND tkDeviceProtocol IN (99, new_tkDeviceProtocol) = 0 THEN throw exception; END IF
Error Message:Phone Personalization feature is not supported on the specified device type.
Remedy:Do not change the setting (tkPhonePersonalization) from Default (value = 3)
2.3.84.129 tkphoneservicedisplay (FI-3626)
Type:enum
Default Value:3
Remarks:Identifies which services are displayed for a button (services, directories, messages): Internal, External, Both, or Default (use CommonPhoneConfig value)
2.3.84.130 tkpreemption (FI-1303)
Type:enum
Default Value:2
Rule (RI-71):
Type:Active (Insert)
Rule Name:MLPP Preemption Default Setting
Description:If a product supports MLPP Preemption (SUPPORTS_FEATURE_PREEMPTION), then the Default value is PREEMPTION_DEFAULT; otherwise the default value is PREEMPTION_DISABLED
Test Condition:IF (SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0 THEN SET Device.tkPreemption = 0 ELSE SET Device.tkPreemption = 2
Rule (RI-71):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:MLPP Preemption Default Setting
Description:If a product supports MLPP Preemption (SUPPORTS_FEATURE_PREEMPTION), then the Default value is PREEMPTION_DEFAULT; otherwise the default value is PREEMPTION_DISABLED
Test Condition:IF (SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0 THEN SET Device.tkPreemption = 0 ELSE SET Device.tkPreemption = 2
Rule (RI-72):
Type:Validation (Insert/Update)
Rule Name:MLPP Preemption Restriction
Description:Only devices that support MLPP Preemption feature may set the Preemption setting to a value other than DISABLED (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkPreemption != 0) THEN throw exception
Error Message:MLPP Preemption must be disabled on devices that do not support the MLPP Preemption feature.
Remedy:Check the MLPP Preemption feature support and device type and try again.
Rule (RI-72):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:MLPP Preemption Restriction
Description:Only devices that support MLPP Preemption feature may set the Preemption setting to a value other than DISABLED (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkPreemption != 0) THEN throw exception
Error Message:MLPP Preemption must be disabled on devices that do not support the MLPP Preemption feature.
Remedy:Check the MLPP Preemption feature support and device type and try again.
Rule (RI-711):
Type:Active (Update)
Rule Name:Configuration of E1 links that are PRI EURO protocol type for MLPP is allowed.
Description:If device is E1 and MLPP Indication <> 0 Or MLPP Preemption <> 0 Then if PriProtocol <> PRI_EURO then throw exception
Test Condition:On update of Device Table
2.3.84.131 tkproduct (FI-662)
Type:enum
Rule (RFI-675):
Type:Inter-field Condition and Constraint
Test Condition:AllowCFBControlOfCallSecurityIcon = 't'
Default:FALSE
Constraint:EXISTS (SELECT 1 FROM productsupportsfeature psf WHERE psf.tkProduct = tkProduct AND psf.tkDeviceProtocol in (tkDeviceProtocol, 99) AND psf.tksupportsfeature = (SELECT enum from typesupportsfeature where moniker = 'SUPPORTS_FEATURE_CALL_SECURITY_ICON_AGGREGATION'))
Remarks:Product type does not support Control of Call Security Icon Aggregation
Rule (RI-19):
Type:Validation (Insert/Update)
Rule Name:AllowHotelingFlag - EM feature support required
Description:Device.AllowHotelingFlag can only be true for devices that support Extension Mobility.
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Extension Mobility can only turned on for devices that support Extension Mobility feature.
Remedy:Check device type and Extension Mobility feature support before enabling Extension Mobility.
Rule (RI-22):
Type:Validation (Insert/Update)
Rule Name:AAR feature support required
Description:Device.fkAARNeighorhood and Device.fkCallingSearchSpace_AAR can only be specified for devices that support the AAR feature
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 21 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:AAR Group and Calling Search Space can only be used for devices that support the AAR feature.
Remedy:Check device type and AAR feature support before specifying an AAR Group or AAR Calling Search Space.
Rule (RI-24):
Type:Validation (Insert/Update)
Rule Name:Invalid Device Profile setting
Description:Only a phone that supports extension mobility can be configured as a device profile
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99) AND tkDeviceProfile != 0
Error Message:Device Profile can only be created for devices that support Extension Mobility feature.
Remedy:Check the device type and feature support and try again.
Rule (RI-26):
Type:Validation (Insert/Update)
Rule Name:Device Name Validation
Description:For products that are configured as devices, name validation is based on the content of devicenameformat in specified for the product (TypeProduct). The exceptions are gateways for which the names are generated based on unit/subunit/slot position, and virtual devices used for extension mobility and configuration only (User Device Profiles, Autogenerated Profiles, Templates). Virtual devices allow ASCII names up to 50 characters including most punctuation.
Test Condition:ON INSERT/UPDATE IN Device
Error Message:The device name format is not valid or contains invalid characters.
Remedy:Check the name to make sure it is valid for specified product and try again.
Rule (RI-37):
Type:Validation (Insert/Update)
Rule Name:SoftkeyTemplate Restriction
Description:Softkey Templates can be assigned only to devices that support Softkeys
Test Condition:IF (@Device.fkSoftkeyTemplate IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 18 AND tkProduct = @Device.tkProduct AND tkDeviceprotocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Softkey Template is not valid for this type of device.
Remedy:Remove the Softkey Template setting and try again.
Rule (RI-41):
Type:Validation (Insert/Update)
Rule Name:(obsolete) Device Login Duration Restriction
Description:Login Duration is only valid on devices supporting Extension Mobility
Test Condition:IF (@Device.LoginDuration IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Login Duration is valid only for devices that support Extension Mobility feature.
Remedy:Remove the Login Duration setting from the device and try again.
Rule (RI-42):
Type:Validation (Insert/Update)
Rule Name:(obsolete) Device Login Time Restriction
Description:Login Time is only valid on devices supporting Extension Mobility
Test Condition:IF (@Device.LoginTime IS NOT NULL) AND ((SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 9 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) THEN Throw Exception
Error Message:Login Time is valid only for devices that support Extension Mobility feature.
Remedy:Remove the Login Time setting from the device and try again.
Rule (RI-60):
Type:Validation (Insert/Update)
Rule Name:Network Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the Network Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Network Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a Network Hold Audio Source.
Rule (RI-61):
Type:Validation (Insert/Update)
Rule Name:User Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the User Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a User Hold Audio Source.
Rule (RI-66):
Type:Active (Insert)
Rule Name:Set tkClass on Insert
Description:The class of a device is determined by the settings in the TypeModel table in the database. A device's class is set at insert and cannot be modified. Class is determined by Model, and Model is determined by Product.
Test Condition:SET Device.tkClass = (SELECT tkClass FROM TypeModel WHERE Enum = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct))
Rule (RI-67):
Type:Active (Insert)
Rule Name:Set tkModel on Insert
Description:The model of a device is determined by the settings in the TypeProduct table in the database. A device's model is set at insert and cannot be modified.
Test Condition:SET Device.tkModel = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct)
Rule (RI-69):
Type:Validation (Insert/Update)
Rule Name:Device Protocol Setting
Description:The valid Device Protocol settings for a device are determined by the content of the ProductCapabilities table for that device type and feature.
Test Condition:@Device.tkDeviceProtocol IN (SELECT EnumValue FROM ProductCapabilities WHERE (tkProductConfig = 7) AND (tkProduct = @Device.tkProduct))
Error Message:The specified Device Protocol is not valid for this device.
Remedy:Check the Device Protocol support and device type and try again..
Rule (RI-70):
Type:Validation (Insert/Update)
Rule Name:Protocol Side Setting
Description:The valid Protocol Side settings for a device are determined by the content of the ProductCapabilities table for that device type and feature. Most devices are only User side. Only gateways and trunks are configured as Network Side when necessary.
Test Condition:@Device.tkProtocolSide IN (SELECT EnumValue FROM ProductCapabilities WHERE (tkProductConfig = 18) AND (tkProduct = @Device.tkProduct))
Error Message:The specified Protcol Side is not valid for this device.
Remedy:Check the Protocol Side support and device type and try again.
Rule (RI-71):
Type:Active (Insert)
Rule Name:MLPP Preemption Default Setting
Description:If a product supports MLPP Preemption (SUPPORTS_FEATURE_PREEMPTION), then the Default value is PREEMPTION_DEFAULT; otherwise the default value is PREEMPTION_DISABLED
Test Condition:IF (SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0 THEN SET Device.tkPreemption = 0 ELSE SET Device.tkPreemption = 2
Rule (RI-72):
Type:Validation (Insert/Update)
Rule Name:MLPP Preemption Restriction
Description:Only devices that support MLPP Preemption feature may set the Preemption setting to a value other than DISABLED (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 35 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkPreemption != 0) THEN throw exception
Error Message:MLPP Preemption must be disabled on devices that do not support the MLPP Preemption feature.
Remedy:Check the MLPP Preemption feature support and device type and try again.
Rule (RI-74):
Type:Validation (Insert/Update)
Rule Name:MLPP Indication Restriction
Description:Only devices that support MLPP Indication feature may set the Indication setting to a value other than OFF (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 34 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkStatus_MLPPIndicationStatus != 0) THEN throw exception
Error Message:MLPP Indication must be off on devices that do not support the MLPP Indication feature.
Remedy:Check the MLPP Indication feature support and device type and try again.
Rule (RI-75):
Type:Validation (Insert/Update)
Rule Name:User Locale Restriction
Description:Only devices that support Localization feature use the User Locale setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 17 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Locale can only be set for devices that support the Localization feature.
Remedy:Check the Localization feature support and device type before specifying a User Locale.
Rule (RI-199):
Type:Validation (Insert/Update)
Rule Name:Device Security Feature validation
Description:Valid Device Security Modes for each device type are determined by the ProductSupportsFeature records for the security features. Devices that do not support any security feature must be set to non-secure mode. Devices that support other security modes can be set to Default, Not-Secure, or one of the supported security modes (Authentication or Encryption as determined in ProductSupportsFeature).
Test Condition:On Insert/Update of tksecuritymode on Device table.
Error Message:The security feature is not supported for this device
Remedy:Either unselect the desired feature or choose another device.
Rule (RI-263):
Type:Active (Insert)
Rule Name:Set QSIG on Device
Description:When a device is inserted, the QSIG setting for the device is determined automatically as follows: For trunks other than Inter-cluster trunk, the device is treated as H.323; inter-cluster trunk is treated as Mixed-Non-QSIG. Digital Access PRI gateways using QSIG protocol are considered QSIG, H.323 Gateways are considered H.323, and all other gateways (including Digital Access PRI with a non-QSIG protocol) are Mixed-Non-QSIG. All other devices except Route Lists are considered Mixed-Non-QSIG. For Route Lists, see rule "Set QSIG on Route List"
Test Condition:On Insert into Device
Rule (RI-379):
Type:Validation (Insert/Update)
Rule Name:Device DND Option feature restriction
Description:DND Option can only be set to non-Zero on devices that support the DND feature (in ProductSupportsFeature table). For those devices that support the feature, only the Ringer Off (0) is valid, unless a parameter is present in the PSF record. If a parameter value of 1 exists in PSF table, only Call Reject is valid. If the param value is (2), all options including Use Common Profile (2) are valid. Dual mode and remote destination profile only support the Call Reject option.
Test Condition:ON INSERT INTO Device: IF((tkproduct=112 or isdualmode = 't') and (tkDNDOption <>1)) throw exception; ELSE IF (new_tkDNDOption <> 0) THEN SELECT parameter INTO restriction FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_DND) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99); IF (rows returned = 0) THEN throw exception ELSE IF (NVL(restriction, '') <> '') THEN IF (new_tkDNDOption <> restriction) THEN throw exception END IF; END IF; END IF; END IF
Error Message:This device does not support the selected DND Option
Remedy:Do not set a DND Option, or check for restrictions on which options are valid for this device.
Rule (RI-380):
Type:Validation (Insert/Update/Delete)
Rule Name:One server should have exactly one software device (CFB, MTP, MOH, ANN, IVR) each type
Description:One IP Media Streaming software device each type is install by default on all servers cannot be deleted
Test Condition:ON DELETE or Insert Device: IF (old_tkProduct IN (28, 30, 51, 89, 36672)) THEN throw exception;
Error Message:Cannot insert or delete the IP Media Streaming software devices installed on a server by default.
Remedy:Disable the service or remove the device from Media Resource Groups where it appears.
Rule (RI-381):
Type:Active (Insert)
Rule Name:DualMode device type (in PSF) is marked isDualMode = True
Description:If a device type is marked as Dual Mode in the ProductSupportsFeature table, then the Device and RemoteDestination records for the device are automatically updated to set IsDualMode field to true.
Test Condition:ON INSERT INTO Device
Rule (RI-395):
Type:Validation (Insert/Update)
Rule Name:Device Outbound Call Rollover Feature Restriction
Description:The Device.tkOutboundCallRollover setting can only be non-default (other than None) for devices that support the Automatic Outbound Call Rollover feature.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkOutboundCallRollover <> 0) THEN IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = SUPPORTS_FEATURE_AUTOMATIC_OUTBOUND_CALL_ROLLOVER) AND (tkProduct = new_tkProduct) AND (tkDeviceProtocol IN (new_tkDeviceProtocol,99) = 0 THEN throw exception; END IF; END IF;
Error Message:This device does not supports Automatic Outbound Call Rollover.
Remedy:Set the OutboundCallRollover option to No Rollover for this device.
Rule (RI-415):
Type:Validation (Insert/Update)
Rule Name:Join Across Lines Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkStatus_joinacrosslines
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Join Across Lines can only be set for devices that have the Join Across Lines Feature
Remedy:Check the Join Across Lines feature support and device type before specifying a Join Across Lines value.
Rule (RI-416):
Type:Validation (Insert/Update)
Rule Name:Single Button Barge Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkBarge
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Single Button Barge can only be set for devices that have the Single Button Barge Feature
Remedy:Check the Single Button Barge feature support and device type before specifying a Single Button Barge value.
Rule (RI-431):
Type:Validation (Insert/Update)
Rule Name:Phone Personalization Feature Support restriction
Description:Only devices that support the Phone Personalization can have a non-default value for Device.tkPhonePersonalization.
Test Condition:ON INSERT/UPDATE IN Device: IF (new_tkPhonePersonalization <> 3) AND (SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 80 AND tkProduct = new_tkProduct AND tkDeviceProtocol IN (99, new_tkDeviceProtocol) = 0 THEN throw exception; END IF
Error Message:Phone Personalization feature is not supported on the specified device type.
Remedy:Do not change the setting (tkPhonePersonalization) from Default (value = 3)
Rule (RI-447):
Type:Validation (Insert/Update)
Rule Name:Device.fkCallingSearchSpace_CdPNTransform is allowed for all gateways other than FXS ports
Description:Device.fkCallingSearchSpace_CdPNTransform is allowed for all gateways other than FXS ports
Test Condition:ON INSERT/UPDATE
Error Message:Device.fkCallingSearchSpace_CdPNTransform is allowed for all gateways other than FXS ports
Rule (RI-471):
Type:Validation (Insert/Update)
Rule Name:Secure Tone support required for Protected device
Description:IsProtected setting can only be true for devices supporting secure tone feature (tkSupportsFeature = 81)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support secure tone (isprotected setting)
Remedy:Set IsProtected to false and try again
Rule (RI-604):
Type:Validation (Update)
Rule Name:SAF Enabled trunk only supports non secure profile
Description:SAF Enabled trunk only supports non secure profile
Test Condition:SAF Enabled trunk only supports non secure profile
Error Message:SAF Enabled trunk only supports non secure profile
Rule (RI-613):
Type:Validation (Insert/Update)
Rule Name:EMCC SIP Trunk validation
Description:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Test Condition:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Error Message:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Rule (RI-631):
Type:Validation (Insert/Update)
Rule Name:Hotline support required for Hotline Device
Description:Hotline Device setting can only be true for devices supporting Hotline feature (tkSupportsFeature = 93)
Test Condition:ON INSERT/UPDATE IN Device:
Error Message:This Device Model does not support Hotline (hotlinedevice setting)
Remedy:Set hotlinedevice to false and try again
Rule (RI-711):
Type:Active (Update)
Rule Name:Configuration of E1 links that are PRI EURO protocol type for MLPP is allowed.
Description:If device is E1 and MLPP Indication <> 0 Or MLPP Preemption <> 0 Then if PriProtocol <> PRI_EURO then throw exception
Test Condition:On update of Device Table
Rule (RI-734):
Type:Validation (Insert/Update)
Rule Name:Device Table Feature Control Policy Restriction
Description:Only devices that support Feature Control Policy can specify fkFeatureControlPolicy
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 103 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Feature Control Policy can be set for devices that supports the Feature Control Policy
Remedy:Check Feature Control Policy feature support and device type before specifying a value for fkFeatureControlPolicy.
Rule (RI-785):
Type:Active (Insert)
Rule Name:Insert RemoteDestination Records for Device Table
Description:When a device record for a phone is inserted, insert records for RemoteDestination as needed based on product feature support(SUPPORTS_FEATURE_MOBILITY_SIPLINE).
Test Condition: SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 109 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Rule (RI-841):
Type:Validation (Insert/Update)
Rule Name:Device.fkCallingSearchSpace_RdNTransform is allowed for all gateways other than FXS ports
Description:Device.fkCallingSearchSpace_RdNTransform is allowed for all gateways other than FXS ports
Test Condition:ON INSERT/UPDATE
Error Message:Device.fkCallingSearchSpace_RdNTransform is allowed for all gateways other than FXS ports
Rule (RI-844):
Type:Active (Insert/Update)
Rule Name:IMS-integrated Mobile Owner Syncs with Mobility User
Description:For IMS-integrated Mobile devices (as defined in ProductSupportsFeature), the owner (device.fkenduser) and mobility user (device.fkenduser_mobility) must be in sync. Sync owner to mobility user if it's not set.
Test Condition:ON INSERT/UPDATE in Device: IF (old_fkenduer_mobility <> new_fkenduser_mobility) THEN set fkenduser = new_fkenduser_mobility END IF;
Rule (RI-866):
Type:Active (Insert/Update)
Rule Name:Insert/Delete entry into DeviceCERDynamic
Description:When Device.RequireCERLocation is enabled,insert a record into DeviceCERDyanmic
Test Condition:ON UPDATE TO DEVICE.REQUIRECERLOCATION INSERT/DELETE INTO DEVICECERDYNAMIC
Rule (RI-874):
Type:Validation (Insert/Update)
Rule Name:Mobility Check on EndUser for CTI Remote Device
Description:EndUser associated with CTI Remote Device should be Mobility Enabled.
Test Condition:Check description for complete rule. ON INSERT INTO Device: SELECT fkenduser_mobility INTO theEndUser FROM device WHERE pkid = device.pkid; SELECT EnableMobility INTO mobility FROM enduser WHERE pkid = theEndUser; IF (mobility = 'F') THEN throw exception END IF;
Error Message:Cannot add the device for EndUser that does not have Mobility enabled.
Remedy:Enable Mobility on the EndUser associated with CTI Remote Device and try again.
Rule (RI-941):
Type:Validation (Insert/Update)
Rule Name:Token User can own only CDT device
Description:Token User can own only CDT device or be used for mobility only for CDT
Test Condition:On I/U of Device: FOR fkEndUser or fkEndUser_Mobility ,If tkUserProfile=3 AND (tkModel<>645 AND tkProduct<>530) THEN THROW EXCEPTION
Error Message:Token EndUser can be associated with CDT only or used for mobility
2.3.84.132 tkproduct_base (FI-1050)
Type:enum (Null OK)
Default Value:NULL
Remarks:Is this a dead field? Used by GW?
Rule (RI-223):
Type:Active (Insert)
Rule Name:Add a VGC Gateway to MGCP on Device update
Description:On Insert only
Test Condition:?
Rule (RI-223):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Add a VGC Gateway to MGCP on Device update
Description:On Insert only
Test Condition:?
Rule (RI-316):
Type:Active (Insert/Update)
Rule Name:Prevent applying secure profile where not supported.
Description:on I/U of Device
Test Condition:Only endpoints on gateways with secure mode support may be set to use Security Profiles marked for secure mode. Further, all endpoints on analog gateways must remain consistent in either all operating in secure mode or all in non-secure mode
2.3.84.133 tkprotocolside (FI-6)
Type:enum
Default Value:1
Migration Source:DeviceList.Side
Remarks:Network side or User Side
Rule (RFI-128):
Type:Inter-field Condition and Constraint
Test Condition:tkDeviceProtocol = 4
Constraint:tkProtocolSide <> 1
Remarks:User side does not support Digital Access T1 protocol
Rule (RI-70):
Type:Validation (Insert/Update)
Rule Name:Protocol Side Setting
Description:The valid Protocol Side settings for a device are determined by the content of the ProductCapabilities table for that device type and feature. Most devices are only User side. Only gateways and trunks are configured as Network Side when necessary.
Test Condition:@Device.tkProtocolSide IN (SELECT EnumValue FROM ProductCapabilities WHERE (tkProductConfig = 18) AND (tkProduct = @Device.tkProduct))
Error Message:The specified Protcol Side is not valid for this device.
Remedy:Check the Protocol Side support and device type and try again.
Rule (RI-70):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Protocol Side Setting
Description:The valid Protocol Side settings for a device are determined by the content of the ProductCapabilities table for that device type and feature. Most devices are only User side. Only gateways and trunks are configured as Network Side when necessary.
Test Condition:@Device.tkProtocolSide IN (SELECT EnumValue FROM ProductCapabilities WHERE (tkProductConfig = 18) AND (tkProduct = @Device.tkProduct))
Error Message:The specified Protcol Side is not valid for this device.
Remedy:Check the Protocol Side support and device type and try again.
2.3.84.134 tkqsig (FI-1410)
Type:enum (Not Modifiable)
Default Value:4
Rule (RI-263):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Set QSIG on Device
Description:When a device is inserted, the QSIG setting for the device is determined automatically as follows: For trunks other than Inter-cluster trunk, the device is treated as H.323; inter-cluster trunk is treated as Mixed-Non-QSIG. Digital Access PRI gateways using QSIG protocol are considered QSIG, H.323 Gateways are considered H.323, and all other gateways (including Digital Access PRI with a non-QSIG protocol) are Mixed-Non-QSIG. All other devices except Route Lists are considered Mixed-Non-QSIG. For Route Lists, see rule "Set QSIG on Route List"
Test Condition:On Insert into Device
Rule (RI-263):
Type:Active (Insert)
Rule Name:Set QSIG on Device
Description:When a device is inserted, the QSIG setting for the device is determined automatically as follows: For trunks other than Inter-cluster trunk, the device is treated as H.323; inter-cluster trunk is treated as Mixed-Non-QSIG. Digital Access PRI gateways using QSIG protocol are considered QSIG, H.323 Gateways are considered H.323, and all other gateways (including Digital Access PRI with a non-QSIG protocol) are Mixed-Non-QSIG. All other devices except Route Lists are considered Mixed-Non-QSIG. For Route Lists, see rule "Set QSIG on Route List"
Test Condition:On Insert into Device
2.3.84.135 tkreset (FI-3111)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
2.3.84.136 tkringsetting_dnd (FI-3288)
Type:enum (Null OK)
Default Value:NULL
Check Constraint:((tkRingSetting_DND = 1) OR (tkRingSetting_DND = 2) OR (tkRingSetting_DND = 5))
Rule (RI-946):
Type:Active (Insert/Update)
Rule Name:Auto-fix for Dual Mode and Mobile Smart Client device settings
Description:IF autofix is enabled AND IsDualMode='t' THEN SET tkRingSeting_DND = 1 i.e. disabled AND OR IF tkDevicePotocol=17 (MobileSmartClient) THEN SET tkRingSeting_DND = 1 i.e. disabled AND SET fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Test Condition:IF g_enable_auto_fix = 't' AND IsDualMode='t' THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=NULL OR IF tkDevicePotocol=17 THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Rule (RI-946):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Auto-fix for Dual Mode and Mobile Smart Client device settings
Description:IF autofix is enabled AND IsDualMode='t' THEN SET tkRingSeting_DND = 1 i.e. disabled AND OR IF tkDevicePotocol=17 (MobileSmartClient) THEN SET tkRingSeting_DND = 1 i.e. disabled AND SET fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
Test Condition:IF g_enable_auto_fix = 't' AND IsDualMode='t' THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=NULL OR IF tkDevicePotocol=17 THEN RETURN tkRingSetting_DND =1,fkMobileSmartClientProfile=(SELECT pkid FROM MobileSmartClientProfile WHERE IsStandard='t')
2.3.84.137 tksipassertedtype (FI-3493)
Type:enum
Default Value:0
Rule (RFI-165):
Type:Inter-field Condition and Constraint
Test Condition:tkModel != 131
Default:0
Constraint:tkSipAssertedType=0
Remarks:SIP Asserted Type only applies to SIP Trunk. Other Device should set to default (0)
Rule (RFI-169):
Type:Inter-field Condition and Constraint
Test Condition:IsPAIEnabled='f'
Constraint:tkSIPAssertedType NOT IN (1,2)
Remarks:When PAI feature is disabled, the SIP Asserted Type should be set to DEFAULT
2.3.84.138 tksipcodec_mtppreferredorigcodec (FI-3015)
Type:enum
Default Value:1
Remarks:Preferred Originating Codec (G711u, G711a, G729a, G729ab, G729b)
2.3.84.139 tksipprivacy (FI-3489)
Type:enum
Default Value:0
Rule (RFI-164):
Type:Inter-field Condition and Constraint
Test Condition:tkModel != 131
Default:0
Constraint:tkSipPrivacy=0
Remarks:SIP Privacy only applies to SIP Trunk. Other Device should set to default (0)
Rule (RFI-168):
Type:Inter-field Condition and Constraint
Test Condition:IsPAIEnabled='f'
Constraint:tkSIPPrivacy NOT IN (1,2,6)
Remarks:When PAI feature is disabled, the SIP Privacy Type should be set to DEFAULT
2.3.84.140 tkstatus_alwaysuseprimeline (FI-3704)
Type:enum
Default Value:2
Remarks:Determines off-hook behavior of phones with active calls present
2.3.84.141 tkstatus_alwaysuseprimelineforvm (FI-3705)
Type:enum
Default Value:2
Remarks:Determines Voice Message retreival behavior of phones
2.3.84.142 tkstatus_audiblealertingbusy (FI-3531)
Type:enum
Default Value:2
Remarks:Indicates whether Audible Alert tone is played when phone is busy (call active); Default means use the Service Parameter setting
2.3.84.143 tkstatus_audiblealertingidle (FI-3530)
Type:enum
Default Value:2
Remarks:Indicates whether Audible Alert tone is played when phone is idle (no call active); Default means use the Service Parameter setting
2.3.84.144 tkstatus_builtinbridge (FI-1306)
Type:enum
Default Value:2
2.3.84.145 tkstatus_devicemobilitymode (FI-3169)
Type:enum
Default Value:2
Rule (RI-821):
Type:Active (Update)
Rule Name:when device.tkStatus_DeviceMobilityMode is set to 0 - off, then set the DeviceMobilityDynamic.fkDevicePool_DeviceMobility
Description:Need to add a rule that sets (UPDATE) the fkDevicePool_DeviceMobility to NULL when we disable the devicemobility of the device
Test Condition:ON UPDATE, IF(device.tkStatus_DeviceMobilityMode=0) Then DeviceMobilityDynamic.fkDevicePool_DeviceMobility= NULL;
2.3.84.146 tkstatus_joinacrosslines (FI-3465)
Type:enum
Default Value:2
Rule (RFI-194):
Type:Inter-field Condition and Constraint
Test Condition:IsProtected ='t'
Constraint:tkStatus_joinacrosslines=0
Remarks:Protected phone cannot have Join Across Line Features active
Rule (RI-415):
Type:Validation (Insert/Update)
Rule Name:Join Across Lines Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkStatus_joinacrosslines
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Join Across Lines can only be set for devices that have the Join Across Lines Feature
Remedy:Check the Join Across Lines feature support and device type before specifying a Join Across Lines value.
Rule (RI-415):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Join Across Lines Restriction
Description:Only devices that support Join Across lines can have a value other than zero for tkStatus_joinacrosslines
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 78 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:Join Across Lines can only be set for devices that have the Join Across Lines Feature
Remedy:Check the Join Across Lines feature support and device type before specifying a Join Across Lines value.
2.3.84.147 tkstatus_mlppindicationstatus (FI-1302)
Type:enum
Default Value:0
Rule (RI-73):
Type:Default (Defines a default value)
Rule Name:MLPP Indication Default Setting
Description:If a product supports MLPP Indication (SUPPORTS_FEATURE_MLPP), then the Default value is STATUS_DEFAULT; otherwise the default value is STATUS_OFF
Test Condition:IF (SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 34 AND tkProduct = @Device.tkProduct) = 0 THEN SET Device.tkStatus_MLPPIndicationStatus = 0 ELSE SET Device.tkStatus_MLPPIndicationStatus = 2
Rule (RI-74):
Type:Validation (Insert/Update)
Rule Name:MLPP Indication Restriction
Description:Only devices that support MLPP Indication feature may set the Indication setting to a value other than OFF (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 34 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkStatus_MLPPIndicationStatus != 0) THEN throw exception
Error Message:MLPP Indication must be off on devices that do not support the MLPP Indication feature.
Remedy:Check the MLPP Indication feature support and device type and try again.
Rule (RI-74):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:MLPP Indication Restriction
Description:Only devices that support MLPP Indication feature may set the Indication setting to a value other than OFF (0).
Test Condition:IF ((SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 34 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)) = 0) AND (Device.tkStatus_MLPPIndicationStatus != 0) THEN throw exception
Error Message:MLPP Indication must be off on devices that do not support the MLPP Indication feature.
Remedy:Check the MLPP Indication feature support and device type and try again.
Rule (RI-711):
Type:Active (Update)
Rule Name:Configuration of E1 links that are PRI EURO protocol type for MLPP is allowed.
Description:If device is E1 and MLPP Indication <> 0 Or MLPP Preemption <> 0 Then if PriProtocol <> PRI_EURO then throw exception
Test Condition:On update of Device Table
2.3.84.148 tkstatus_usetrustedrelaypoint (FI-3478)
Type:enum (Indexed)
Default Value:2
Remarks:Indicates whether Trusted Relay Point should be used if available
2.3.84.149 tkuserlocale (FI-1035)
Type:enum (Null OK)
Default Value:NULL
Remarks:User local of device, see device pool if null
Rule (RI-75):
Type:Validation (Insert/Update)
Rule Name:User Locale Restriction
Description:Only devices that support Localization feature use the User Locale setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 17 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Locale can only be set for devices that support the Localization feature.
Remedy:Check the Localization feature support and device type before specifying a User Locale.
Rule (RI-75):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:User Locale Restriction
Description:Only devices that support Localization feature use the User Locale setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 17 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Locale can only be set for devices that support the Localization feature.
Remedy:Check the Localization feature support and device type before specifying a User Locale.
2.3.84.150 transmitutf8 (FI-2094)
Type:bool
Default Value:FALSE
Remarks:If true, transmit utf8 calling party id
2.3.84.151 unattended_port (FI-2398)
Type:bool
Default Value:FALSE
Rule (RI-613):
Type:Validation (Insert/Update)
Rule Name:EMCC SIP Trunk validation
Description:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Test Condition:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
Error Message:EMCC Trunk has to have SendGeolocation as true, MTPRequired as false, UnattendedPort as false
2.3.84.152 unit (FI-925)
Type:long
Default Value:0
Rule (RI-119):
Type:Active (Insert/Update/Delete records)
This field is modified by this rule.
Rule Name:MGCP Slot copy to Device Unit
Description:MGCPDeviceMember table's Slot field value is copied to Device table's Unit field.
Test Condition:UPDATE Device SET Unit = MGCPDeviceMember.Slot WHERE Device.pkid = MGCP.fkDevice
2.3.84.153 unknownprefix (FI-3514)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Unknown Prefix
Rule (RFI-186):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77,95,18)
Constraint:(UnknownPrefix = '') OR (UnknownPrefix = 'Default') OR (UnknownPrefix = 'default')
Null Allowed:null
Remarks:Unknown Prefix should be empty for devices other than H323 gateways and trunks, MGCP T1/E1 PRI and BRI gateways, MGCP FXO Ports, and SIP trunks
Rule (RFI-258):
Type:Inter-field Condition and Constraint
Test Condition:tkProduct NOT IN (2,1,90,55,52,10001,17,75,76,77,95,18)
Constraint:(UnknownStripDigits = '') OR (UnknownStripDigits IS NULL)
Null Allowed:null
Remarks:Unknown Strip Digits should be empty for devices other than H323 gateways and trunks, MGCP T1/E1 PRI and BRI gateways, MGCP FXO Ports, and SIP trunks
2.3.84.154 unknownstripdigits (FI-5113)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(UnknownStripDigits >= 0) AND (UnknownStripDigits <= 24)
Remarks:Unknown Strip Digits
Rule (RFI-229):
Type:Inter-field Condition and Constraint
Test Condition:(UnknownPrefix = 'Default') OR (UnknownPrefix = 'default')
Constraint:UnknownStripDigits IS NULL
Remarks:Cannot use UnknownStripDigits when the Default prefix is used.
2.3.84.155 upgradefinishtime (FI-1917)
Type:string [50]
Default Value:EMPTY
2.3.84.156 usedevicepoolcalledcssintl (FI-5198)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CalledIntl setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.157 usedevicepoolcalledcssnatl (FI-5197)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CalledNational setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.158 usedevicepoolcalledcsssubs (FI-5200)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CalledSubscriber setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.159 usedevicepoolcalledcssunkn (FI-5199)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CalledUnknown setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.160 usedevicepoolcdpntransformcss (FI-3509)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CdPNTransform setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.161 usedevicepoolcgpningressdn (FI-10058)
Type:bool
Default Value:TRUE
Remarks:Indicates whether to use fkCallingSearchSpace_CgpnIngressDN on this Device (this table) or from the Device Pool.
2.3.84.162 usedevicepoolcgpntransformcss (FI-3521)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CgPNTransform setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.163 usedevicepoolcgpntransformcssintl (FI-5412)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CgpnTransform setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.164 usedevicepoolcgpntransformcssnatl (FI-5411)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CgpnTransform setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.165 usedevicepoolcgpntransformcsssubs (FI-5414)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CgpnTransform setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.166 usedevicepoolcgpntransformcssunkn (FI-5413)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CgpnTransform setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.167 usedevicepoolrdntransformcss (FI-9925)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_RdNTransform setting from Device Pool will be used and if false use setting on Device including NULL to mean no Calling Search Space
2.3.84.168 userholdmohaudiosourceid (FI-838)
Type:long (Null OK)
Default Value:NULL
Rule (RI-61):
Type:Validation (Insert/Update)
Rule Name:User Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the User Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a User Hold Audio Source.
Rule (RI-61):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:User Hold Audio Source Restriction
Description:Only devices that support Music On Hold feature use the User Hold Audio Source setting
Test Condition:SELECT COUNT (*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 4 AND tkProduct = @Device.tkProduct AND tkDeviceProtocol IN (@Device.tkDeviceProtocol,99)
Error Message:User Hold Audio Source can only be used for devices that support the Music On Hold feature.
Remedy:Check device type and Music On Hold feature support before specifying a User Hold Audio Source.
2.3.84.169 v150modemrelaycapable (FI-2165)
Type:bool
Default Value:FALSE
2.3.84.170 versionstamp (FI-3128)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid plus seconds past midnight 1970 are concatenated
Rule (RI-216):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
Rule (RI-305):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:device insert versionstamp
Description:on insert of a device, generate a deviceversionstamp record
Test Condition:insert device
Rule (RI-305):
Type:Active (Insert)
Rule Name:device insert versionstamp
Description:on insert of a device, generate a deviceversionstamp record
Test Condition:insert device
Uniqueness:No multicolumn uniqueness constraints
Constraints:
Rule (RFI-110):
Type:Inter-field Condition and Constraint
Constraint:( fkCallingSearchSpace IS NULL ) OR ( tkClass IN (1, 2, 8, 10, 13, 18, 20, 250, 251, 252, 253, 254) )
Remarks:CallingSearchSpace is not valid for this type of device
Rule (RFI-111):
Type:Inter-field Condition and Constraint
Constraint:( fkDevicePool IS NOT NULL ) OR ( tkClass IN (7, 15, 17, 250, 252, 253, 254)) OR (tkModel = 133) OR (EXISTS (SELECT 1 FROM TypeModel TM WHERE tkModel = TM.enum AND TM.tksubclass = (SELECT enum FROM TypeSubClass WHERE moniker = 'SUB_CLASS_CISCO_TELEPRESENCE_MCU')))
Remarks:A Device Pool is required for this device.
Rule (RFI-113):
Type:Inter-field Condition and Constraint
Constraint:( fkMediaResourceList IS NULL) OR ( tkClass IN (1, 2, 10, 13, 18, 20, 250, 251, 252, 253))
Remarks:Media Resource List is not valid for this type of device.
Rule (RFI-114):
Type:Inter-field Condition and Constraint
Constraint:( ( fkProcessNode IS not NULL) OR ( tkModel not IN (50, 70, 110, 126, 36219))) AND ( (fkProcessNode IS NULL) OR ( tkModel IN (50, 70, 110, 126, 36219)))
Remarks:A Server (Process Node) is required for this device OR this device cannot be assigned to a Server (ProcessNode).
Rule (RFI-115):
Type:Inter-field Condition and Constraint
Constraint:(fkProcessNode IS NULL) OR ( fkProcessNode <> '00000000-111-0000-0000-000000000000')
Remarks:Devices cannot be assigned to the reserved Enterprise Node (system Process Node).
Rule (RFI-119):
Type:Inter-field Condition and Constraint
Constraint:( fkMlppDomain IS NULL) OR ( tkClass IN (1, 2, 8, 10, 13, 18, 20, 250, 251, 252, 253, 254))
Remarks:MLPP Domain ID is not valid for this type of device.
Rule (RFI-120):
Type:Inter-field Condition and Constraint
Constraint:( RouteListEnabled <> 't') OR ( tkModel = 90)
Remarks:Route List Enabled can be true only for Route List devices.
Rule (RFI-121):
Type:Inter-field Condition and Constraint
Constraint:( fkEndUser IS NULL) OR ( tkClass IN (1, 10, 13, 253, 254))
Remarks:End Users can only own or log into Phones and CTI Route Points.
Rule (RFI-198):
Type:Inter-field Condition and Constraint
Constraint:(IsDualMode = 'f' AND tkDeviceProtocol <> 17) OR (tkRingSetting_DND = 1)
Remarks:Ring Setting for DND must be Disabled (1) for Dual Mode and Mobile Smart Client devices
Rule (RFI-262):
Type:Inter-field Condition and Constraint
Constraint:(AllowHotelingFlag='t') AND (tkStatus_DeviceMobilityMode=1) OR (tkProduct!=15)
Remarks:AllowHoteling and DeviceMobilityMode for the EMCC base phone needs to be on
Rule (RFI-310):
Type:Inter-field Condition and Constraint
Constraint:( NOT EXISTS (SELECT 1 FROM LicenseServer LS, TypeLicensingState TLS WHERE TLS.enum = LS.tkLicensingState AND NOT TLS.AllowProvisioning))
Remarks:The system has exceeded its time limit to resolve license non-compliance issue. No more provisioning operations are allowed until the license compliance issues are resolved.
Rules:
Rule (RI-2):
Type:Active (Insert)
Rule applied when record is inserted.
Rule Name:Generate CTI ID value
Description:On insert of a new record generate a unique 32-bit integer value and store the result in the CTI ID field
Test Condition:On Insert
Rule (RI-15):
Type:Documentation (Developer notes only)
Rule applied when record is inserted.
Rule Name:AnalogAccess record required
Description:Devices with the Analog Access Device Protocol should always have a corresponding record in the AnalogAccess table, and port information in the AnalogAccessPort table
Test Condition:Device.tkDeviceProtocol = 3
Rule (RI-20):
Type:Active (Insert/Update)
This table is modified by this rule.
Rule Name:Autogenerate Device Profile for EM
Description:When EM is on (Device.AllowHotelingFlag = true), if the default Device Profile (ikDevice_DefaultProfile) does not reference a User Device Profile or the AutoGenerated Device Profile for the current device, generate a profile based on the device settings (after all changes are committed), and then set ikDevice_DefaultProfile to the pkid of the autogenerated Device Profile. The Autogenerated Device Profile uses "ADP" prefixed on current MAC address for a name (in place of SEP), and contains a copy of a subset of the settings of the current device, including information in related (child) tables like Telecaster, Speed Dial, DeviceNumPlanMap, etc.
Test Condition:Device.AllowHotelingFlag = true
Rule (RI-21):
Type:Active (Update/Delete)
Rule applied when record is deleted.
Rule Name:Remove Autogenerated Device Profile
Description:When a real phone with an Autogenerated Device Profile (for Extension Mobility) is deleted, or if Device.ikDevice_DefaultProfile is cleared, the Autogenerated Device Profile must be deleted.
Test Condition:If ( (@Device.ikDevice_DefaultProfile IS NULL AND @Device.AllowHotelingFlag = FALSE) OR (Device is deleted) ) Then (DELETE FROM Device WHERE Device.pkid = @Device.ikDevice_DefaultProfile AND Device.tkDeviceProfile = 2)
Rule (RI-23):
Type:Active (Insert/Update/Delete records)
This table is modified by this rule.
Rule Name:Synchronize Autogenerated Profile
Description:If the Enterprise Parameter for Autosync Profiles is true, the device referenced by Device.ikDevice_DefaultProfile, if it is an autogenerated profile, must be updated to match the settings of the phone
Test Condition:If ( (SELECT COUNT(*) FROM ProcessConfig WHERE ParamName = 'enableAutoDeviceProfileSynChronize' AND ParamValue = 'T') AND (SELECT COUNT(*) FROM Device WHERE Device.pkid = @Device.ikDevice_DefaultProfile AND Device.tkDeviceProfile = 2) ) Then update (refresh) Autogenerated Device Profile
Rule (RI-66):
Type:Active (Insert)
Rule applied when record is inserted.
Rule Name:Set tkClass on Insert
Description:The class of a device is determined by the settings in the TypeModel table in the database. A device's class is set at insert and cannot be modified. Class is determined by Model, and Model is determined by Product.
Test Condition:SET Device.tkClass = (SELECT tkClass FROM TypeModel WHERE Enum = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct))
Rule (RI-67):
Type:Active (Insert)
Rule applied when record is inserted.
Rule Name:Set tkModel on Insert
Description:The model of a device is determined by the settings in the TypeProduct table in the database. A device's model is set at insert and cannot be modified.
Test Condition:SET Device.tkModel = (SELECT tkModel FROM TypeProduct WHERE Enum = @Device.tkProduct)
Rule (RI-100):
Type:Validation (Insert/Update)
Rule applied when record is deleted.
Rule Name:Cannot Delete Device with Logged In User
Description:Cannot delete a phone with Extension Mobility enabled while a User is logged into the device.
Test Condition:IF (Device.AllowHoteling = true) AND (Device.fkEndUser IS NOT NULL) THEN throw exception
Error Message:Extension Mobility Device cannot be deleted while a User is logged in.
Remedy:Log out the user and then delete the device.
Rule (RI-101):
Type:Active (Insert/Update/Delete records)
Rule applied when record is updated.
This table is modified by this rule.
Rule Name:Sync Device Profile on Device Changes
Description:If the information related to a device with an autogenerated device profile changes, and the enterprise parameter for autosync profiles is true, then the autogenerated device profile must be re-generated. This includes changes to the DeviceAddonModuleMap, Telecaster, Telecaster SubscribedServices, SpeedDial, and DeviceNumPlanMap tables.
Test Condition:(SELECT COUNT(*) FROM ProcessConfig WHERE (ParamName = 'AutosyncDeviceProfile') AND (ParamValue = 'T') > 0) AND (SELECT tkDeviceProfile FROM Device WHERE (pkid = @Device.ikDevice_DefaultDeviceProfile) = 2) AND (SELECT LoginTime FROM Device WHERE (pkid = @Device.pkid) != 0)
Rule (RI-188):
Type:Active (Insert)
Rule applied when record is inserted.
This table is modified by this rule.
Rule Name:Insert Media Streaming Devices
Description:When a ProcessNodeService record for a Media Streaming service is inserted, database automatically inserts the four media streaming Device records for the service: Annunciator, Software Conference Bridge, Music On Hold, and Software MTP. In addition, a MOHServer record is inserted for the MOH device, and a MediaMixer record is inserted for the MTP device.
Test Condition:On Insert to ProcessNodeService WHERE tkService=3
Rule (RI-202):
Type:Active (Insert/Update/Delete records)
Rule applied when record is inserted or updated.
This table is modified by this rule.
Rule Name:Generate Default Device Profile for Model
Description:Create a Default Device Profile for a device type if one does not already exist, and extension mobility is enabled on a device of that type (e.g., create the Default Device Profile for a Cisco 7960 if it does not exist and EM is enabled on a 7960).
Test Condition:IF (NEW.AllowHotelingFlag is true) and ((select count(*) from device where tkmodel = NEW.tkmodel and tkdeviceprofile = 3) = 0)
Error Message:No default model profile, no mismatch login performed
Rule (RI-310):
Type:Active (Update)
Rule applied when record is updated.
Rule Name:(obsolete) Insert DeviceEMSyn record if auto sync of auto generated profile is needed
Description:When EM is on (Device.AllowHotelingFlag = true), if the default Device Profile is the auto generated Device Profile for the current device, and the value of service parameter (enableAutoDeviceProfileSynChronize) is true, then insert a record into DeviceEMSyn table with the pkid of auto-generated profile and the pkid of the current device. Later DbMon will process the change notification of DeviceEMSyn to re-generate the auto-generated profile of the current device.
Test Condition:Device.AllowHotelingFlag = true
Rule (RI-468):
Type:Active (Delete)
Rule applied when record is deleted.
Rule Name:Remove default intercom device from Numplan when Device is Deleted
Description:When a device is deleted, update all Numplan records where this device is used as fkDevice_IntercomDefault
Test Condition:ON DELETE in Device: UPDATE Numplan set fkDevice_IntercomDefault = NULL WHERE fkDevice_IntercomDefault = @pkid

 
2.3.85 deviceaddonmodulemap (TI-167)
Description:Map device to phone template for add-on-modules
Fields:
2.3.85.1 fkdevice (FI-979)
Type:guid (Cascade Delete)
Rule (RI-77):
Type:Validation (Insert/Update)
Rule Name:DeviceAddOnModule Limit & KEM(s) can only be added to devices that support them
Description:The number of Add-on Modules supported by a device (phone) is indicated in the MaxAddOnModules column of the TypeProduct table. When a record is inserted into the DeviceAddonModuleMap table, the number of records for the specified device cannot exceed the MaxAddOnModules for that device type (product). Also, The KEM can only be assigned to a phone that supports it.
Test Condition:ON INSERT/UPDATE INTO DeviceAddonModuleMap (IF (SELECT COUNT(*) FROM DeviceAddonModuleMap WHERE fkDevice = @Device.pkid) > (SELECT MaxAddOnModules FROM TypeProduct WHERE Enum = @Device.tkProduct) THEN throw exception.
Error Message:Cannot insert additional Add-on Modules for this device OR This Device Model does not support this type of expansion module.
Remedy:Check the number of Add-on Modules supported and configured for this device and try again OR this Device Model does not support this type of expansion module.
Rule (RI-176):
Type:Validation (Insert/Update)
Rule Name:Device Add-on Module Map Model Restriction
Description:The model referenced by a DeviceAddonModuleMap record must be in the Add-on Module class (16).
Test Condition:IF (@DeviceAddonModuleMap.tkModel NOT IN (SELECT Enum FROM TypeModel WHERE tkClass = 16)) THEN throw exception
Error Message:The specified Model is not an Add-on Module.
Remedy:Check the class of the model you selected to make sure it is an addon module, and try again.
Rule (RI-284):
Type:Active (Insert/Update/Delete records)
Rule Name:deviceaddonmodulemap versionstamp
Description:on change to anything in deviceaddonmodulemap table, update devicerelatedversionstamp versionstamp
Test Condition:update devicerelatedversionstamp
Rule (RI-469):
Type:Validation (Insert/Update)
Rule Name:KEM(s) cannot not be mixed on the same device
Description:If the KEM has been set to one type on a given device it cannot be assigned a second KEM of another type
Test Condition:ON INSERT/UPDATE IN DeviceAddOnModuleMap: SELECT tkmodel INTO theModel from DeviceAddOnModuleMap where pkid <> new_Pkid and fkdevice = new_fkdevice; IF (new_tkmodel <> theModel) THEN theMoniker='DEVICE_KEM_MIXED_TYPES'; END IF;
Error Message:Expansion Modules can not be of mixed types.
Remedy:Two types of Expansion Modules have been selected for the same Device. Please select only one type of Expansion Module.
2.3.85.2 moduleindex (FI-981)
Type:long
Rule (RI-76):
Type:Documentation (Developer notes only)
This field is modified by this rule.
Rule Name:DeviceAddOnModule Index
Description:The configured Add-on Modules for a device (phone) should always start with ModuleIndex = 1 for that device. Whenever an Add-on Module is deleted from the DeviceAddonModuleMap table, the remaining record(s) are re-indexed to make sure that there is a module with ModuleIndex = 1.
Test Condition:SELECT * FROM DeviceAddonModuleMap WHERE fkDevice = @Device.pkid ORDER BY ModuleIndex; DECL @Index = 1; FOR EACH record in resultset (SET ModuleIndex = @Index; @Index = @Index + 1)
2.3.85.3 pkid (FI-978)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-469):
Type:Validation (Insert/Update)
Rule Name:KEM(s) cannot not be mixed on the same device
Description:If the KEM has been set to one type on a given device it cannot be assigned a second KEM of another type
Test Condition:ON INSERT/UPDATE IN DeviceAddOnModuleMap: SELECT tkmodel INTO theModel from DeviceAddOnModuleMap where pkid <> new_Pkid and fkdevice = new_fkdevice; IF (new_tkmodel <> theModel) THEN theMoniker='DEVICE_KEM_MIXED_TYPES'; END IF;
Error Message:Expansion Modules can not be of mixed types.
Remedy:Two types of Expansion Modules have been selected for the same Device. Please select only one type of Expansion Module.
2.3.85.4 specialloadinformation (FI-988)
Type:string [32] (Null OK)
Default Value:NULL
Validation:^[a-zA-Z0-9._-]{0,32}$
Remarks:used only by addon with firmware
2.3.85.5 tkmodel (FI-1620)
Type:enum
Default Value:124
Rule (RI-77):
Type:Validation (Insert/Update)
Rule Name:DeviceAddOnModule Limit & KEM(s) can only be added to devices that support them
Description:The number of Add-on Modules supported by a device (phone) is indicated in the MaxAddOnModules column of the TypeProduct table. When a record is inserted into the DeviceAddonModuleMap table, the number of records for the specified device cannot exceed the MaxAddOnModules for that device type (product). Also, The KEM can only be assigned to a phone that supports it.
Test Condition:ON INSERT/UPDATE INTO DeviceAddonModuleMap (IF (SELECT COUNT(*) FROM DeviceAddonModuleMap WHERE fkDevice = @Device.pkid) > (SELECT MaxAddOnModules FROM TypeProduct WHERE Enum = @Device.tkProduct) THEN throw exception.
Error Message:Cannot insert additional Add-on Modules for this device OR This Device Model does not support this type of expansion module.
Remedy:Check the number of Add-on Modules supported and configured for this device and try again OR this Device Model does not support this type of expansion module.
Rule (RI-469):
Type:Validation (Insert/Update)
Rule Name:KEM(s) cannot not be mixed on the same device
Description:If the KEM has been set to one type on a given device it cannot be assigned a second KEM of another type
Test Condition:ON INSERT/UPDATE IN DeviceAddOnModuleMap: SELECT tkmodel INTO theModel from DeviceAddOnModuleMap where pkid <> new_Pkid and fkdevice = new_fkdevice; IF (new_tkmodel <> theModel) THEN theMoniker='DEVICE_KEM_MIXED_TYPES'; END IF;
Error Message:Expansion Modules can not be of mixed types.
Remedy:Two types of Expansion Modules have been selected for the same Device. Please select only one type of Expansion Module.
Uniqueness:fkdevice + moduleindex is unique. (MFI-33)
Rules:
Rule (RI-76):
Type:Documentation (Developer notes only)
Rule applied when record is deleted.
Rule Name:DeviceAddOnModule Index
Description:The configured Add-on Modules for a device (phone) should always start with ModuleIndex = 1 for that device. Whenever an Add-on Module is deleted from the DeviceAddonModuleMap table, the remaining record(s) are re-indexed to make sure that there is a module with ModuleIndex = 1.
Test Condition:SELECT * FROM DeviceAddonModuleMap WHERE fkDevice = @Device.pkid ORDER BY ModuleIndex; DECL @Index = 1; FOR EACH record in resultset (SET ModuleIndex = @Index; @Index = @Index + 1)
Rule (RI-101):
Type:Active (Insert/Update/Delete records)
Rule applied when record is updated.
This table is modified by this rule.
Rule Name:Sync Device Profile on Device Changes
Description:If the information related to a device with an autogenerated device profile changes, and the enterprise parameter for autosync profiles is true, then the autogenerated device profile must be re-generated. This includes changes to the DeviceAddonModuleMap, Telecaster, Telecaster SubscribedServices, SpeedDial, and DeviceNumPlanMap tables.
Test Condition:(SELECT COUNT(*) FROM ProcessConfig WHERE (ParamName = 'AutosyncDeviceProfile') AND (ParamValue = 'T') > 0) AND (SELECT tkDeviceProfile FROM Device WHERE (pkid = @Device.ikDevice_DefaultDeviceProfile) = 2) AND (SELECT LoginTime FROM Device WHERE (pkid = @Device.pkid) != 0)

 
2.3.86 deviceautoreg (TI-2608)
Description:Stores device auto registration configuration, existence of record implies auto registration is enabled.
Fields:
2.3.86.1 autoregistrationenddn (FI-25740)
Type:long
Default Value:1999
Check Constraint:(AutoregistrationEndDN >= 0) AND (AutoregistrationEndDN < 99999999)
Remarks:This is the last directory number to use for auto-registration of devices. Specifying a valid range of directory numbers in the Starting Directory Number and Ending Directory Number fields automatically enables auto-registration. Setting the starting and ending directory numbers to the same value disables auto-registration.
Rule (RI-247):
Type:Active (Insert/Update)
Rule Name:UpdStartDNEndDN
Description:Before update, if NEW.autoregstartdn > NEW.autoregnextdn) or (NEW.autoregenddn < NEW.autoregnnextdn, then set nextdn = startdn
Test Condition:?
Error Message:?
Remedy:?
2.3.86.2 autoregistrationnextdn (FI-25741)
Type:long
Default Value:1000
Remarks:This field is incremented by Cisco CallManager after a device has autoregistered.
Rule (RI-247):
Type:Active (Insert/Update)
Rule Name:UpdStartDNEndDN
Description:Before update, if NEW.autoregstartdn > NEW.autoregnextdn) or (NEW.autoregenddn < NEW.autoregnnextdn, then set nextdn = startdn
Test Condition:?
Error Message:?
Remedy:?
Rule (RI-247):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:UpdStartDNEndDN
Description:Before update, if NEW.autoregstartdn > NEW.autoregnextdn) or (NEW.autoregenddn < NEW.autoregnnextdn, then set nextdn = startdn
Test Condition:?
Error Message:?
Remedy:?
2.3.86.3 autoregistrationstartdn (FI-25739)
Type:long
Default Value:1000
Check Constraint:(AutoregistrationStartDN >= 0) AND (AutoregistrationStartDN < 99999999)
Remarks:This is the first directory number to use for auto-registration of devices.
Rule (RI-247):
Type:Active (Insert/Update)
Rule Name:UpdStartDNEndDN
Description:Before update, if NEW.autoregstartdn > NEW.autoregnextdn) or (NEW.autoregenddn < NEW.autoregnnextdn, then set nextdn = startdn
Test Condition:?
Error Message:?
Remedy:?
2.3.86.4 enable (FI-25746)
Type:bool
Default Value:TRUE
Remarks:Indicates wheather auto-registration is enabled..
2.3.86.5 fkcallmanager (FI-25738)
Type:guid (Unique, Indexed, Cascade Delete)
Remarks:Reference to CallManager.
2.3.86.6 fkdevice (FI-25742)
Type:guid (Indexed)
Remarks:Reference to Universal device template for auto-registration
2.3.86.7 fknumplan (FI-25743)
Type:guid (Indexed)
Remarks:Reference to Universal line template for auto-registration
2.3.86.8 pkid (FI-25737)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints
Constraints:
Rule (RFI-665):
Type:Inter-field Condition and Constraint
Constraint:(AutoregistrationStartDN<AutoregistrationEndDN)
Remarks:Start must be less than end.

 
2.3.87 devicecerdynamic (TI-1066)
Description:Table for tracking off-premise capable devices for CER
Insert/Delete is not allowed.
Fields:
2.3.87.1 allowoutboundcalls (FI-10033)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:Flag to allow OutboundCall
Rule (RI-931):
Type:Active (Update)
This field is modified by this rule.
Rule Name:Update allowoutboundcalls flag
Description:Update allowoutboundcalls column according to value of tke911locationstate
Test Condition:Update allowoutboundcalls column according to value of tke911locationstate
Rule (RI-931):
Type:Active (Update)
Rule Name:Update allowoutboundcalls flag
Description:Update allowoutboundcalls column according to value of tke911locationstate
Test Condition:Update allowoutboundcalls column according to value of tke911locationstate
2.3.87.2 datetimestamp (FI-10276)
Type:long (Not Modifiable)
Default Value:0
Remarks:Time value for last change (for replication conflict resolution).
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.87.3 fkdevice (FI-10032)
Type:guid (Cascade Delete, Null OK)
Default Value:NULL
Remarks:Foreign key to Device table
2.3.87.4 pkid (FI-10031)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record
Rule (RI-931):
Type:Active (Update)
Rule Name:Update allowoutboundcalls flag
Description:Update allowoutboundcalls column according to value of tke911locationstate
Test Condition:Update allowoutboundcalls column according to value of tke911locationstate
2.3.87.5 sendxsi (FI-10034)
Type:long
Default Value:0
Remarks:Indication to CUCM for sending XSI to device
2.3.87.6 tke911locationstate (FI-10272)
Type:enum
Default Value:0
Remarks:Reference to TypeE911LocationState
Rule (RI-931):
Type:Active (Update)
Rule Name:Update allowoutboundcalls flag
Description:Update allowoutboundcalls column according to value of tke911locationstate
Test Condition:Update allowoutboundcalls column according to value of tke911locationstate
2.3.87.7 url (FI-10035)
Type:string [250]
Default Value:EMPTY
Remarks:URL to CER user page
Uniqueness:No multicolumn uniqueness constraints

 
2.3.88 devicefeaturemember (TI-209)
Description:Generic table for associating a list of features with a device
Fields:
2.3.88.1 fkdevice_group (FI-1371)
Type:guid (Cascade Delete)
2.3.88.2 member (FI-1373)
Type:string [100]
Default Value:EMPTY
2.3.88.3 pkid (FI-1370)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.88.4 selectionorder (FI-1374)
Type:long
2.3.88.5 tkdevicefeature (FI-1372)
Type:enum
Uniqueness:fkdevice_group + tkdevicefeature is unique. (MFI-35)

 
2.3.89 devicehlogdynamic (TI-437)
Description:Frequently updated settings for Hunt Group Log In/Out
Insert/Delete is not allowed.
Fields:
2.3.89.1 datetimestamp (FI-3308)
Type:long
Default Value:0
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.89.2 fkdevice (FI-3307)
Type:guid (Unique, Cascade Delete)
2.3.89.3 hlog (FI-3166)
Type:bool
Default Value:TRUE
Remarks:By default a Hunt List to which a device belongs will extend calls to the device (logged in when hlog = true). When hlog is set to false, Hunt List will not extend calls to this device (logged out swhen hlog = false)
2.3.89.4 pkid (FI-3306)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.90 devicemanagementdynamic (TI-2593)
Description:Stores the timestamp for remote wipe/lock state change request or acknowlegement for mobile devices
Fields:
2.3.90.1 datetimestamp (FI-25662)
Type:long
Default Value:0
Remarks:Time stamp for the last remote/wipe state change.
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.90.2 fkdevice (FI-25814)
Type:guid (Unique, Indexed, Cascade Delete, Not Modifiable)
Remarks:Foreign key to Device table
Rule (RI-2152):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of DeviceManagementDynamic, Set fkDevice=pkid for DeviceManagementDynamic
Description:On Insert/Update of DeviceManagementDynamic, make sure the pkid is set equal to fkDevice
Test Condition:ON INSERT/UPDATE: IF fkDevice IS NOT NULL Set pkid=fkDevice AND fkDevice=fkDevice ELSE Set pkid=pkid AND fkDevice=pkid
Rule (RI-2152):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:On Active Insert/Update of DeviceManagementDynamic, Set fkDevice=pkid for DeviceManagementDynamic
Description:On Insert/Update of DeviceManagementDynamic, make sure the pkid is set equal to fkDevice
Test Condition:ON INSERT/UPDATE: IF fkDevice IS NOT NULL Set pkid=fkDevice AND fkDevice=fkDevice ELSE Set pkid=pkid AND fkDevice=pkid
2.3.90.3 latestlockacknowledge (FI-25666)
Type:long (Null OK)
Remarks:Time stamp for last lock acknowledge.
2.3.90.4 latestlockrequest (FI-25665)
Type:long (Null OK)
Remarks:Time stamp for last lock request.
2.3.90.5 latestwipeacknowledge (FI-25664)
Type:long (Null OK)
Remarks:Time stamp for last wipe acknowledge.
2.3.90.6 latestwiperequest (FI-25663)
Type:long (Null OK)
Remarks:Time stamp for last wipe request.
2.3.90.7 pkid (FI-25661)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-2152):
Type:Active (Insert/Update)
Rule Name:On Active Insert/Update of DeviceManagementDynamic, Set fkDevice=pkid for DeviceManagementDynamic
Description:On Insert/Update of DeviceManagementDynamic, make sure the pkid is set equal to fkDevice
Test Condition:ON INSERT/UPDATE: IF fkDevice IS NOT NULL Set pkid=fkDevice AND fkDevice=fkDevice ELSE Set pkid=pkid AND fkDevice=pkid
Rule (RI-2152):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:On Active Insert/Update of DeviceManagementDynamic, Set fkDevice=pkid for DeviceManagementDynamic
Description:On Insert/Update of DeviceManagementDynamic, make sure the pkid is set equal to fkDevice
Test Condition:ON INSERT/UPDATE: IF fkDevice IS NOT NULL Set pkid=fkDevice AND fkDevice=fkDevice ELSE Set pkid=pkid AND fkDevice=pkid
Uniqueness:No multicolumn uniqueness constraints

 
2.3.91 devicemanagementinfo (TI-973)
Description:This table is used to store the http information for MCU Conference Bridge.
Fields:
2.3.91.1 conferencebridgeprefix (FI-21276)
Type:string [8]
Default Value:EMPTY
Validation:^[0-9]{0,8}$
Remarks:Conference Bridge Prefix
2.3.91.2 fkdevice (FI-9862)
Type:guid (Unique, Indexed, Cascade Delete)
Migration Source:convert from DeviceName
Remarks:Refers to the device record for MCU Conference bridge.
2.3.91.3 managementport (FI-9865)
Type:long
Default Value:80
Check Constraint:(ManagementPort >=0) AND (ManagementPort <= 65535)
Remarks:Http Port No
2.3.91.4 overridesiptrunkaddress (FI-21275)
Type:bool (Null OK)
Default Value:FALSE
Remarks:Override SIP Trunk address as HTTP address
2.3.91.5 password (FI-9864)
Type:string [128]
Validation:^[^\x00-\x1F\x7F]{1,31}$
Remarks:Used for Authentication
2.3.91.6 pkid (FI-9861)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.91.7 usehttps (FI-10183)
Type:bool
Default Value:FALSE
Remarks:Flag to use HTTPS port, this would ensure that all the message interactions are through Secure port
2.3.91.8 username (FI-9863)
Type:string [128]
Default Value:EMPTY
Validation:^[^\x00-\x1F\x7F]{1,31}$
Uniqueness:No multicolumn uniqueness constraints

 
2.3.92 devicemobilitydynamic (TI-436)
Description:Frequently updated settings for Mobility
Insert/Delete is not allowed.
Fields:
2.3.92.1 datetimestamp (FI-3305)
Type:long
Default Value:0
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.92.2 fkdevice (FI-3304)
Type:guid (Unique, Cascade Delete)
2.3.92.3 fkdevicepool_devicemobility (FI-3165)
Type:guid (Null OK)
Default Value:NULL
2.3.92.4 pkid (FI-3303)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.92.5 versionstamp (FI-3451)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid is generated every time this device is updated
Rule (RI-413):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:DeviceMobilityDynamic versionstamp
Description:update versionstamp in DeviceMobilityDynamic
Test Condition:update DeviceMobilityDynamic
Rule (RI-413):
Type:Active (Insert/Update)
Rule Name:DeviceMobilityDynamic versionstamp
Description:update versionstamp in DeviceMobilityDynamic
Test Condition:update DeviceMobilityDynamic
Uniqueness:No multicolumn uniqueness constraints

 
2.3.93 devicemobilitygroup (TI-423)
Description:Used for Device Mobility
Fields:
2.3.93.1 description (FI-3170)
Type:string [200]
Default Value:EMPTY
Validation:^[^\x00-\x1F""%&<>]{0,50}$
2.3.93.2 name (FI-3171)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
2.3.93.3 pkid (FI-3172)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.94 devicemobilityinfo (TI-427)
Description:Device Mobility Mapping
Fields:
2.3.94.1 name (FI-3173)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
2.3.94.2 pkid (FI-3174)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.94.3 subnet (FI-3175)
Type:string [15]
Validation:^(22[0-3]|2[01][0-9]|1[0-9]{2}|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9]?[0-9])){3}$
Rule (RI-349):
Type:Validation (Insert/Update)
Rule Name:DeviceMobilityInfo.SubnetMask first octect restriction
Description:The first octect of the Subnet mask for DeviceMobilityInfo must be 223 or
Test Condition:ON INSERT/UPDATE in DeviceMobilityInfo: If (first octet of dotted decimal IP address > 223) then throw exception;
Error Message:The subnet mask is out of range.
Remedy:Make sure the first octet value is 223 or less.
Rule (RI-356):
Type:Validation (Insert/Update)
Rule Name:DeviceMobilityInfo SubnetMask and Size must match
Description:The subnet mask and the mask size setting must match.
Test Condition:ON INSERT/UPDATE
Error Message:Subnet mask and mask size do not match
Remedy:Change the subnet mask to match the size
2.3.94.4 subnetmasksz (FI-3176)
Type:long
Check Constraint:(SubNetMaskSz >= 0) AND (SubNetMaskSz <= 32)
Rule (RI-356):
Type:Validation (Insert/Update)
Rule Name:DeviceMobilityInfo SubnetMask and Size must match
Description:The subnet mask and the mask size setting must match.
Test Condition:ON INSERT/UPDATE
Error Message:Subnet mask and mask size do not match
Remedy:Change the subnet mask to match the size
Uniqueness:subnet + subnetmasksz is unique. (MFI-101)

 
2.3.95 devicenumplanmap (TI-77)
Description:Ordered association of NumPlan records with a device (line appearance)
Fields:
2.3.95.1 busytrigger (FI-1350)
Type:long
Default Value:1
Check Constraint:BusyTrigger > 0
Rule (RI-79):
Type:Default (Defines a default value)
Rule Name:Busy Trigger Default Setting
Description:When a device supports Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the default for Busy Trigger is the lesser of a) the Default BusyTrigger setting in the Product Supports Feature record's parameter value or b) the MaxCalls default for the current line. If the Multiple Call Display feature is not supported, BusyTrigger defaults to 2 if the device supports CallWaiting, or 1 if the device doesn't support Call Waiting (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_CALL_WAITING).
Test Condition:SELECT ParamValue FROM ProductSupportsFeature WHERE (tkSupportsFeature = 30) AND (tkProduct = @Device.tkProduct)
Rule (RI-82):
Type:Validation (Insert/Update)
Rule Name:Busy Trigger and No Call Waiting
Description:Busy Trigger must be set to 1 if there is no record for current device type (Device.tkProduct) to indicate that the device supports Call Waiting (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_CALL_WAITING) (6)
Test Condition:IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 6 AND tkProduct = @Device.tkProduct) = 0 AND (DeviceNumPlanMap.BusyTrigger != 1) THEN throw exception
Error Message:Busy Trigger cannot be greater than 1 because the specified device type does not support Call Waiting
Remedy:Check the Call Waiting support and device type and try again. If the device does not support Call Waiting, Busy Trigger must be set to 1.
Rule (RI-94):
Type:Validation (Insert/Update)
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
Rule (RI-94):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
2.3.95.2 callinfodisplaymask (FI-1351)
Type:long
Default Value:9
Check Constraint:(CallInfoDisplayMask >= 0) AND (CallInfoDisplayMask <=15)
2.3.95.3 ctiid (FI-600)
Type:identity (Unique, Not Modifiable)
Migration Source:NumPlan.ID
Remarks:Trigger set on insert. 32 bit value for Computer Telephony Interface
Rule (RI-2):
Type:Active (Insert)
Rule Name:Generate CTI ID value
Description:On insert of a new record generate a unique 32-bit integer value and store the result in the CTI ID field
Test Condition:On Insert
Rule (RI-225):
Type:Active (Insert)
This field is modified by this rule.
Rule Name:Increment DevNumPlanMap Ctiid
Description:On Insert only
Test Condition:?
2.3.95.4 dialplanwizardgenid (FI-678)
Type:long (Indexed, Null OK)
Default Value:NULL
Remarks:This record created by DialPlanWizard
2.3.95.5 display (FI-317)
Type:string [120]
Default Value:EMPTY
Validation:^[^]""""%<>[&|{}]{0,30}$
Migration Source:NumPlan.Display
Remarks:The localized name to display for internal Caller ID
Rule (RI-83):
Type:Warning (Message for UI only)
Rule Name:Display Name (Caller ID) is a Number
Description:Internal Caller ID should not appear to be a Directory Number because this could hide the actual calling number for call information. It is allowed, but not recommeded, where a specific Calling Number should appear that is different from the actual calling number. This does not effect the calling number sent in call setup messages.
Test Condition:DeviceNumPlanMap.Display contains only digits
Error Message:Display text for a line appearance is intended for displaying text such as a name instead of the directory number for internal calls. If you specify a number, the person receiving a call may not see the proper identity of the caller.
2.3.95.6 displayascii (FI-1789)
Type:string [30]
Default Value:EMPTY
Validation:^[a-zA-Z0-9 !#$'()*+,./:;=?@\\^_`}~-]{0,30}$
Remarks:A safe version of the Caller ID Display text using only English letters (a to Z) and punctuation, used when endpoints are using different language groups.
Rule (RI-83):
Type:Warning (Message for UI only)
Rule Name:Display Name (Caller ID) is a Number
Description:Internal Caller ID should not appear to be a Directory Number because this could hide the actual calling number for call information. It is allowed, but not recommeded, where a specific Calling Number should appear that is different from the actual calling number. This does not effect the calling number sent in call setup messages.
Test Condition:DeviceNumPlanMap.Display contains only digits
Error Message:Display text for a line appearance is intended for displaying text such as a name instead of the directory number for internal calls. If you specify a number, the person receiving a call may not see the proper identity of the caller.
2.3.95.7 e164mask (FI-617)
Type:dn (Null OK)
DN Type:DN_TYPE_MASK
Default Value:NULL
Validation:^[0-9*#+X]{0,24}$
Remarks:masked against NumPlan.DnOrPattern to get full number to display on Telecaster
2.3.95.8 fkcallingsearchspace_monitoring (FI-3261)
Type:guid (Null OK)
Default Value:NULL
Remarks:CallingSearchSpace used for monitoring if supported by associated device
Rule (RI-364):
Type:Validation (Insert/Update)
Rule Name:Monitor feature restriction
Description:The Monitor CSS can only be set on a line if the device supports the Monitor feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@fkCallingSearchSpace_Monitoring IS NOT NULL) AND (SELECT tkProduct, tkDeviceProtocol from Device where pkid = @fkDevice) NOT IN (Select tkproduct, tkdeviceprotocol from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MONITOR) THEN throw exception;
Error Message:Monitoring is not supported on the device where this line appears
Remedy:Do not set a Calling Search Space for Monitoring.
Rule (RI-364):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Monitor feature restriction
Description:The Monitor CSS can only be set on a line if the device supports the Monitor feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@fkCallingSearchSpace_Monitoring IS NOT NULL) AND (SELECT tkProduct, tkDeviceProtocol from Device where pkid = @fkDevice) NOT IN (Select tkproduct, tkdeviceprotocol from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MONITOR) THEN throw exception;
Error Message:Monitoring is not supported on the device where this line appears
Remedy:Do not set a Calling Search Space for Monitoring.
2.3.95.9 fkdevice (FI-281)
Type:guid (Indexed, Cascade Delete)
Migration Source:convert from NumPlan.DeviceName
Rule (RI-82):
Type:Validation (Insert/Update)
Rule Name:Busy Trigger and No Call Waiting
Description:Busy Trigger must be set to 1 if there is no record for current device type (Device.tkProduct) to indicate that the device supports Call Waiting (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_CALL_WAITING) (6)
Test Condition:IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE tkSupportsFeature = 6 AND tkProduct = @Device.tkProduct) = 0 AND (DeviceNumPlanMap.BusyTrigger != 1) THEN throw exception
Error Message:Busy Trigger cannot be greater than 1 because the specified device type does not support Call Waiting
Remedy:Check the Call Waiting support and device type and try again. If the device does not support Call Waiting, Busy Trigger must be set to 1.
Rule (RI-86):
Type:Validation (Insert/Update)
Rule Name:Associate DNs with Devices
Description:A Directory Number (NumPlan.tkPatternUsage = 2) can only be associated with Phones (including Device Profiles), CTI Route Points, and FXS Gateway Ports
Test Condition:?
Rule (RI-87):
Type:Validation (Insert/Update)
Rule Name:Associate Route Pattern with Devices
Description:A Route Pattern (NumPlan.tkPatternUsage = 5) can only be associated with a single Gateway, Trunk, Hunt List or Route List.
Test Condition:?
Rule (RI-88):
Type:Validation (Insert/Update)
Rule Name:Associate Hunt Pilot with Hunt List
Description:A Hunt Pilot (NumPlan.tkPatternUsage = 8) can only be associated with a single device which must be a Hunt List (Device.tkProduct = ?)
Test Condition:?
Rule (RI-89):
Type:Validation (Insert/Update)
Rule Name:Route Group Member Exclusion
Description:A Route Group cannot contain a device that already has an association to a Route Pattern, nor devices that are already members of a Route Group.
Test Condition:?
Rule (RI-90):
Type:Validation (Insert/Update)
Rule Name:Gateway Port in Route Group
Description:If an individual port on a gateway is assigned to a Route Group, the entire device cannot be assigned to a Route Group, nor can it be associated with a Route Pattern. The remaining individual ports can be assigned to the same or a different Route Group.
Test Condition:?
Rule (RI-91):
Type:Validation (Insert/Update)
Rule Name:NumPlan Associated with Device
Description:Devices can only be associated with (DeviceNumPlanMap records may only reference NumPlan records for) DNs, Route Patterns and Hunt Pilots.
Test Condition:?
Rule (RI-92):
Type:Validation (Insert/Update)
Rule Name:No CTI Device in Line Group
Description:CTI Ports and CTI Route Points may not be associated with DNs that are in Line Groups. (Temporary restriction pending CTI support for Line Groups and Hunt Lists.)
Test Condition:?
Rule (RI-93):
Type:Validation (Insert/Update)
Rule Name:Shared Line Support Required
Description:If product support for shared line is not present, DN cannot be associated with more than one device.
Test Condition:IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = 8) AND (tkProduct = @Device.tkProduct) = 0) AND (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE (fkNumPlan = @NumPlan.pkid) > 1) THEN throw exception
Rule (RI-94):
Type:Validation (Insert/Update)
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
Rule (RI-96):
Type:Validation (Insert/Update)
Rule Name:AutoAnswer Device Support
Description:The AutoAnswer setting for a DN can only be on when the DN is associated with a Device (or Device Profile) type that supports the Auto Answer feature.
Test Condition:IF (NumPlan.tkAutoAnswer != 0) AND (SELECT COUNT (*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = 7) AND (tkProduct = @Device.tkProduct) = 0) THEN throw exception
Error Message:AutoAnswer is not valid for this Directory Number because it is not associated with a device that supports the AutoAnswer feature.
Remedy:Set AutoAnswer to Off or associated the DN with a device that supports AutoAnswer and try again.
Rule (RI-136):
Type:Validation (Insert/Update)
Rule Name:Device in Route Group or Route Pattern
Description:Gateways and Trunks must not be in Route Groups if they are already associated with a Route Pattern, or in the case of FXS ports associated with a DN.
Test Condition:IF (SELECT COUNT(*) FROM RouteGroupDeviceMap WHERE fkDevice = @RouteGroupDeviceMap.fkDevice AND Port = @RouteGroupDeviceMap.port) > 0) AND (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE fkDevice = @DeviceNumPlanMap.fkDevice AND NumPlanIndex = @RouteGroupDeviceMap.Port) > 0) THEN throw exception
Error Message:The selected device or part is already associated with a Route Pattern and cannot be added to a Route Group.
Remedy:Remove the device or individual port from any associated Route Patterns and try again.
Rule (RI-191):
Type:Validation (Insert/Update)
Rule Name:Devices assoc. with RP have matching Dial Plan
Description:If a device record is associated with a Route Pattern via its presence in DeviceNumPlanMap then both the referred Dial Plans should match.
Test Condition:On INSERT/UPDATE in DeviceNumPlanMap IF (@fkNumPlan.tkPatternUsage = 5) AND (@fkDevice.fkDialPlan <> @fkDevice.fkDialPlan) THEN throw Exception
Error Message:The Dial Plan of the Device should match that of the associated Route Pattern
Remedy:Add the matching Dial Plan to the associated Device
Rule (RI-207):
Type:Validation (Insert/Update)
Rule Name:Associate VM Port DN with Voice Mail Port device
Description:The NumPlan record associated with a Voice Mail Port device must be a VM Port DN (tkpatternusage = 8). VM Port cannot use a regular device DN (tkpatternusage = 2).
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF ((SELECT tkClass FROM Device WHERE pkid = @DeviceNumPlanMap.fkDevice) = 8) AND ((SELECT tkPatternUsage FROM NumPlan WHERE pkid = @DeviceNumPlanMap.fkNumPlan) <> 8) THEN throw exception
Error Message:Cannot associate a DN or Pattern that is not a Voice Mail DN with a Voice Mail Port.
Remedy:Make sure the DN or Pattern is a Voice Mail Port DN (not a regular device DN or other type of pattern).
Rule (RI-228):
Type:Validation (Insert/Update)
Rule Name:ValidateFXSPortDN
Description:For CAT6K FXS ports. Model_Elvis type devices if there are more than one device/same dn associations in devicenumplanmap then its an error.
Test Condition:?
Error Message:FXS port is not shareable.
Remedy:?
Rule (RI-229):
Type:Validation (Insert/Update)
Rule Name:ValidateDevNumPlanIndex
Description:A device (phone) cannot have the same line more than once.
Test Condition:ON INSERT/UPDATE INTO DeviceNumPlanMap IF (SELECT COUNT(*) INTO nRows FROM DeviceNumPlanMap WHERE (fkDevice = new_fkDevice) AND NumPlanIndex = new_NumPlanIndex) AND (fkPartitionUsage = new_tkPartitionUsage)) > 1 THEN throw exception;
Error Message:Duplicate phone line.
Remedy:?
Rule (RI-231):
Type:Active (Insert)
Rule Name:ValidateInsertSucceeds
Description:If a record exists in devicenumplanmap then update the corresponding numplan record to set its isCallable field to true
Test Condition:?
Error Message:Could not update isCallable field for this numplan record.
Remedy:?
Rule (RI-266):
Type:Validation (Insert/Update)
Rule Name:Assign numplan to class template for pattern_device
Description:A numplan record with (tkpatternusage = PATTERN_DEVICE_TEMPLATE) can only be assigned to a device of class template
Test Condition:?
Error Message:Could not associate fknumplan to fkdevice of class template
Remedy:?
Rule (RI-277):
Type:Active (Insert/Update/Delete records)
Rule Name:devicenumplanmap versionstamp
Description:on change to anything in devicenumplanmap table, update devicerelatedversionstamp versionstamp
Test Condition:update devicerelatedversionstamp
Rule (RI-287):
Type:Validation (Insert/Update)
Rule Name:MWL Policy feature restriction
Description:MWL Policy can be set to non-default only on devices that support the Message Waiting Lamp Policy feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@tkMWLPolicy<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MWL_POLICY) THEN throw exception
Error Message:Message Waiting Lamp Policy is not supported on the device where this line appears
Remedy:Use the default MWL Policy setting.
Rule (RI-288):
Type:Validation (Insert/Update)
Rule Name:Ring Setting feature restriction
Description:Ring Settings can be set to non-default value only for devices that support the Disable Ring feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (tkRingSetting<>0) OR (tkRingSetting_Consecutive<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_DISABLE_RING) THEN throw exception
Error Message:Ring settings are not supported on the device where this line appears.
Remedy:Use the default ring settings.
Rule (RI-350):
Type:Validation (Insert/Update)
Rule Name:Ring Setting for Pickup Alert must be supported by device type
Description:Ring Setting for Pickup Alert can only be set on lines associated with devices that support the feature
Test Condition:ON INSERT/UPDATE in DeviceNumPlanMap: SELECT tkProduct, tkDeviceProtocol INTO product, protocol FROM Device WHERE pkid = new_fkDevice; SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tkSupportsFeature = SUPPORTS_DISABLE_RING AND tkProduct = product AND tkProtocol IN (protocol, 99); IF (nRows = 0) AND (new_tkRingSetting_IdlePickupAlert IS NOT NULL) OR (new_tkRingSetting_ActivePickupAlert IS NOT NULL) THEN throw exception END IF;
Error Message:This device does not support the Pickup Alert feature
Rule (RI-361):
Type:Validation (Insert/Update)
Rule Name:Audible MWI feature restriction
Description:Audible MWI status can be set to non-default only on devices that support the Message Waiting Lamp Policy feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@tkMWLPolicy<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MWL_POLICY) THEN throw exception
Error Message:Audible Message Waiting Indicator is not supported on the device where this line appears
Remedy:Use the default Audible MWI status setting.
Rule (RI-362):
Type:Active (Insert)
Rule Name:Insert RecordDynamic record if recording is supported
Description:For each line on a device that supports Recording, insert a record in RecordDynamic with a reference back to the new DeviceNumPlanMap record
Test Condition:ON INSERT into DeviceNumPlanMap: INSERT INTO RecordDynamic (pkid, fkDeviceNumPlanMap) VALUES (newid(), @DeviceNumPlanMap.pkid)
Rule (RI-363):
Type:Validation (Insert/Update)
Rule Name:Recording feature restriction
Description:The recording profile can only be set on a line if the device supports the Recording feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@fkRecordingProfile IS NOT NULL) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_RECORD) THEN throw exception
Error Message:Recording is not supported on the device where this line appears
Remedy:Do not set a Recording Profile.
Rule (RI-364):
Type:Validation (Insert/Update)
Rule Name:Monitor feature restriction
Description:The Monitor CSS can only be set on a line if the device supports the Monitor feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@fkCallingSearchSpace_Monitoring IS NOT NULL) AND (SELECT tkProduct, tkDeviceProtocol from Device where pkid = @fkDevice) NOT IN (Select tkproduct, tkdeviceprotocol from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MONITOR) THEN throw exception;
Error Message:Monitoring is not supported on the device where this line appears
Remedy:Do not set a Calling Search Space for Monitoring.
Rule (RI-419):
Type:Validation (Insert/Update)
Rule Name:Intercom not compatible with Extension Mobility
Description:An Intercom DN cannot be configured for a User Device Profile, even if that profile has a phone button template with the Intercom Feature.
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap: SELECT tkpatternusage INTO patternusage FROM NUMPLAN WHERE pkid = new_fkNumPlan; SELECT tkDeviceProfile INTO profiletype FROM Device WHERE pkid = new_fkDevice; IF (patternusage = 13 AND profiletype <> 0) THEN throw exception END IF;
Error Message:Cannot assign an Intercom DN to a Device Profile or BAT Template
Remedy:Intercom DN is not compatible with Extension Mobility. Assign Intercom DN directly to phones.
Rule (RI-488):
Type:Validation (Insert/Update)
Rule Name:Log Missed Calls Option Restriction
Description:Log Missed Calls Option (DeviceNumPlanMap.LogMissedCalls) can only be enabled if the device product and protocol support the Log Missed Calls Option feature (typesupportsfeature = 92)
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap: IF (NOT default option) THEN SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tksupportsfeature = 92 and tkproduct = (new_tkproduct) and tkdeviceprotocol IN (new_tkdeviceprotocol, 99); IF (nRows = 0) THEN throw exception; END IF; END IF;
Error Message:Log Missed Calls option can only be set for devices that support the feature.
Remedy:Make sure the product and protocol support setting Log Missed Calls options, or leave the setting at its default.
Rule (RI-601):
Type:Validation (Insert/Update)
Rule Name:SAF CCD or EMCC or ViPR trunk not used by Route Group or Route Pattern
Description:SAF CCD or EMCC or ViPR trunk can not be used by Route Group or Route Pattern
Test Condition:SAF CCD or EMCC or ViPR trunk can not be added to Route Group or assigned to Route Pattern
Error Message:SAF CCD or EMCC Trunk or ViPR can not be added to Route Group or assigned to Route Pattern
Rule (RI-942):
Type:Active (Delete)
Rule Name:Remove Associated Hunt Pilot Queue
Description:When a hunt list is deleted, all associated huntpilotqueue table rows should to be deleted.
Test Condition:ON DELETE FROM Device (DELETE FROM HuntPilotQueue WHERE fkNumplan_Pilot = DeviceNumplanMap.fkNumPlan)
Rule (RI-960):
Type:Validation (Insert/Update)
Rule Name:PreferredMediaSource can only be Phone if related device type supports full recoding
Description:When line appearance has PreferredMediaSource set to phone, the associated device must fully support recording
Test Condition:On INSERT / UPDATE on DEVICENUMPLANMAP IF tkPreferredMediaSource = PREFERRED_MEDIA_SOURCE_PHONE THEN IF Device D WHERE D.pkid = fkDevice AND productsupportsfeature where tksupportsfeature = SUPPORTS_FEATURE_RECORD AND param in (empty or full) AND d.tkdeviceprotocol AND D.tkproduct
Error Message:Device type does not support recording from through phone
Remedy:Set preferred media source to gateway.
2.3.95.10 fknumplan (FI-316)
Type:guid (Cascade Delete, Null OK)
Migration Source:convert from NumPlan.DirectoryNumber
Rule (RI-85):
Type:Active (Delete)
Rule Name:Set unassociated DN IsCallable to False
Description:When the last association between a DN and a device or profile is removed, set the IsCallable field for the DN's NumPlan record to false.
Test Condition:ON DELETE from DeviceNumPlanMap IF (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE (fkNumPlan = @NumPlan.pkid) = 0) THEN SET NumPlan.isCallable = 'F'
Rule (RI-86):
Type:Validation (Insert/Update)
Rule Name:Associate DNs with Devices
Description:A Directory Number (NumPlan.tkPatternUsage = 2) can only be associated with Phones (including Device Profiles), CTI Route Points, and FXS Gateway Ports
Test Condition:?
Rule (RI-87):
Type:Validation (Insert/Update)
Rule Name:Associate Route Pattern with Devices
Description:A Route Pattern (NumPlan.tkPatternUsage = 5) can only be associated with a single Gateway, Trunk, Hunt List or Route List.
Test Condition:?
Rule (RI-88):
Type:Validation (Insert/Update)
Rule Name:Associate Hunt Pilot with Hunt List
Description:A Hunt Pilot (NumPlan.tkPatternUsage = 8) can only be associated with a single device which must be a Hunt List (Device.tkProduct = ?)
Test Condition:?
Rule (RI-91):
Type:Validation (Insert/Update)
Rule Name:NumPlan Associated with Device
Description:Devices can only be associated with (DeviceNumPlanMap records may only reference NumPlan records for) DNs, Route Patterns and Hunt Pilots.
Test Condition:?
Rule (RI-92):
Type:Validation (Insert/Update)
Rule Name:No CTI Device in Line Group
Description:CTI Ports and CTI Route Points may not be associated with DNs that are in Line Groups. (Temporary restriction pending CTI support for Line Groups and Hunt Lists.)
Test Condition:?
Rule (RI-93):
Type:Validation (Insert/Update)
Rule Name:Shared Line Support Required
Description:If product support for shared line is not present, DN cannot be associated with more than one device.
Test Condition:IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = 8) AND (tkProduct = @Device.tkProduct) = 0) AND (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE (fkNumPlan = @NumPlan.pkid) > 1) THEN throw exception
Rule (RI-96):
Type:Validation (Insert/Update)
Rule Name:AutoAnswer Device Support
Description:The AutoAnswer setting for a DN can only be on when the DN is associated with a Device (or Device Profile) type that supports the Auto Answer feature.
Test Condition:IF (NumPlan.tkAutoAnswer != 0) AND (SELECT COUNT (*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = 7) AND (tkProduct = @Device.tkProduct) = 0) THEN throw exception
Error Message:AutoAnswer is not valid for this Directory Number because it is not associated with a device that supports the AutoAnswer feature.
Remedy:Set AutoAnswer to Off or associated the DN with a device that supports AutoAnswer and try again.
Rule (RI-171):
Type:Validation (Insert/Update)
Rule Name:Multiple DeviceNumPlanMap for Shared DN Only
Description:DeviceNumPlanMap may contain multiple records with the same fkNumPlan only if the referenced NumPlan record is a DN (type = Device).
Test Condition:IF ((SELECT Count(*) FROM DeviceNumPlanMap WHERE fkNumPlan = @DeviceNumPlanMap.fkNumPlan) > 1 AND (SELECT tkPatternUsage FROM NumPlan WHERE pkid = @DeviceNumPlanMap.fkNumPlan) != 2) THEN throw exception
Error Message:Only directory numbers can be shared by more than one device.
Remedy:Check the type of NumPlan record you are associating with a device to make sure it is a DN, or if it is not a DN, check to make sure no other devices are associated with it.
Rule (RI-191):
Type:Validation (Insert/Update)
Rule Name:Devices assoc. with RP have matching Dial Plan
Description:If a device record is associated with a Route Pattern via its presence in DeviceNumPlanMap then both the referred Dial Plans should match.
Test Condition:On INSERT/UPDATE in DeviceNumPlanMap IF (@fkNumPlan.tkPatternUsage = 5) AND (@fkDevice.fkDialPlan <> @fkDevice.fkDialPlan) THEN throw Exception
Error Message:The Dial Plan of the Device should match that of the associated Route Pattern
Remedy:Add the matching Dial Plan to the associated Device
Rule (RI-207):
Type:Validation (Insert/Update)
Rule Name:Associate VM Port DN with Voice Mail Port device
Description:The NumPlan record associated with a Voice Mail Port device must be a VM Port DN (tkpatternusage = 8). VM Port cannot use a regular device DN (tkpatternusage = 2).
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF ((SELECT tkClass FROM Device WHERE pkid = @DeviceNumPlanMap.fkDevice) = 8) AND ((SELECT tkPatternUsage FROM NumPlan WHERE pkid = @DeviceNumPlanMap.fkNumPlan) <> 8) THEN throw exception
Error Message:Cannot associate a DN or Pattern that is not a Voice Mail DN with a Voice Mail Port.
Remedy:Make sure the DN or Pattern is a Voice Mail Port DN (not a regular device DN or other type of pattern).
Rule (RI-228):
Type:Validation (Insert/Update)
Rule Name:ValidateFXSPortDN
Description:For CAT6K FXS ports. Model_Elvis type devices if there are more than one device/same dn associations in devicenumplanmap then its an error.
Test Condition:?
Error Message:FXS port is not shareable.
Remedy:?
Rule (RI-229):
Type:Validation (Insert/Update)
Rule Name:ValidateDevNumPlanIndex
Description:A device (phone) cannot have the same line more than once.
Test Condition:ON INSERT/UPDATE INTO DeviceNumPlanMap IF (SELECT COUNT(*) INTO nRows FROM DeviceNumPlanMap WHERE (fkDevice = new_fkDevice) AND NumPlanIndex = new_NumPlanIndex) AND (fkPartitionUsage = new_tkPartitionUsage)) > 1 THEN throw exception;
Error Message:Duplicate phone line.
Remedy:?
Rule (RI-231):
Type:Active (Insert)
Rule Name:ValidateInsertSucceeds
Description:If a record exists in devicenumplanmap then update the corresponding numplan record to set its isCallable field to true
Test Condition:?
Error Message:Could not update isCallable field for this numplan record.
Remedy:?
Rule (RI-232):
Type:Active (Update)
Rule Name:checkIsCallableOnUpdate
Description:Set isCallable field in numplan to true or false based on the fact if that numplan is referenced in DeviceNumPlanMap table.
Test Condition:?
Error Message:resetIsCallable update did not succeed
Remedy:?
Rule (RI-266):
Type:Validation (Insert/Update)
Rule Name:Assign numplan to class template for pattern_device
Description:A numplan record with (tkpatternusage = PATTERN_DEVICE_TEMPLATE) can only be assigned to a device of class template
Test Condition:?
Error Message:Could not associate fknumplan to fkdevice of class template
Remedy:?
Rule (RI-277):
Type:Active (Insert/Update/Delete records)
Rule Name:devicenumplanmap versionstamp
Description:on change to anything in devicenumplanmap table, update devicerelatedversionstamp versionstamp
Test Condition:update devicerelatedversionstamp
Rule (RI-366):
Type:Validation (Insert/Update)
Rule Name:Intercom Line is not Shareable
Description:An Intercom DN can appear on only one real device (but can also appear on a device profile)
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (SELECT COUNT(*) INTO nRows FROM DeviceNumPlanMap map INNER JOIN NumPlan ON NumPlan.pkid = map.fkNumPlan INNER JOIN Device ON Device.pkid = map.fkDevice WHERE NumPlan.tkPatternUsage = 13 AND Device.tkDeviceProfile = 0 AND map.fkNumPlan = new_fkNumPlan) > 1 THEN throw exception
Error Message:Intercom DNs cannot appear on multiple devices
Remedy:Create a separate Intercom DN for each device that requires intercom.
Rule (RI-419):
Type:Validation (Insert/Update)
Rule Name:Intercom not compatible with Extension Mobility
Description:An Intercom DN cannot be configured for a User Device Profile, even if that profile has a phone button template with the Intercom Feature.
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap: SELECT tkpatternusage INTO patternusage FROM NUMPLAN WHERE pkid = new_fkNumPlan; SELECT tkDeviceProfile INTO profiletype FROM Device WHERE pkid = new_fkDevice; IF (patternusage = 13 AND profiletype <> 0) THEN throw exception END IF;
Error Message:Cannot assign an Intercom DN to a Device Profile or BAT Template
Remedy:Intercom DN is not compatible with Extension Mobility. Assign Intercom DN directly to phones.
Rule (RI-473):
Type:Validation (Insert/Update)
Rule Name:DN restrictions for Protected device (secure tone)
Description:Do not allow a "protected" phone to have a shared line
Test Condition:ON INSERT/UPDATE IN Device, DeviceNumplanMap:
Error Message:Protected device can not support shared line.
Remedy:Protected device does not support shared line.
Rule (RI-942):
Type:Active (Delete)
Rule Name:Remove Associated Hunt Pilot Queue
Description:When a hunt list is deleted, all associated huntpilotqueue table rows should to be deleted.
Test Condition:ON DELETE FROM Device (DELETE FROM HuntPilotQueue WHERE fkNumplan_Pilot = DeviceNumplanMap.fkNumPlan)
2.3.95.11 fkrecordingprofile (FI-3260)
Type:guid (Null OK)
Default Value:NULL
Remarks:Profile used for Call Recording if supported by associated device
Rule (RI-363):
Type:Validation (Insert/Update)
Rule Name:Recording feature restriction
Description:The recording profile can only be set on a line if the device supports the Recording feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@fkRecordingProfile IS NOT NULL) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_RECORD) THEN throw exception
Error Message:Recording is not supported on the device where this line appears
Remedy:Do not set a Recording Profile.
Rule (RI-363):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Recording feature restriction
Description:The recording profile can only be set on a line if the device supports the Recording feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@fkRecordingProfile IS NOT NULL) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_RECORD) THEN throw exception
Error Message:Recording is not supported on the device where this line appears
Remedy:Do not set a Recording Profile.
2.3.95.12 label (FI-288)
Type:string [120]
Default Value:EMPTY
Validation:^[^""""]{0,30}$
Migration Source:NULL
Remarks:The text that appears for the line button (allows Unicode).
2.3.95.13 labelascii (FI-1788)
Type:string [30]
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$%&'()*+<>=,./:;?@^[_`{|}~\\-]{0,30}$
Remarks:A safe version of the Line Button Label using only English letters (a to Z) and punctuation.
2.3.95.14 logmissedcalls (FI-3712)
Type:bool
Default Value:TRUE
Remarks:Determines whether missed calls on this line appearance are shown in the call history for the phone.
Rule (RI-488):
Type:Validation (Insert/Update)
Rule Name:Log Missed Calls Option Restriction
Description:Log Missed Calls Option (DeviceNumPlanMap.LogMissedCalls) can only be enabled if the device product and protocol support the Log Missed Calls Option feature (typesupportsfeature = 92)
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap: IF (NOT default option) THEN SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tksupportsfeature = 92 and tkproduct = (new_tkproduct) and tkdeviceprotocol IN (new_tkdeviceprotocol, 99); IF (nRows = 0) THEN throw exception; END IF; END IF;
Error Message:Log Missed Calls option can only be set for devices that support the feature.
Remedy:Make sure the product and protocol support setting Log Missed Calls options, or leave the setting at its default.
Rule (RI-488):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Log Missed Calls Option Restriction
Description:Log Missed Calls Option (DeviceNumPlanMap.LogMissedCalls) can only be enabled if the device product and protocol support the Log Missed Calls Option feature (typesupportsfeature = 92)
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap: IF (NOT default option) THEN SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tksupportsfeature = 92 and tkproduct = (new_tkproduct) and tkdeviceprotocol IN (new_tkdeviceprotocol, 99); IF (nRows = 0) THEN throw exception; END IF; END IF;
Error Message:Log Missed Calls option can only be set for devices that support the feature.
Remedy:Make sure the product and protocol support setting Log Missed Calls options, or leave the setting at its default.
2.3.95.15 maxnumcalls (FI-1349)
Type:long
Default Value:2
Check Constraint:(MaxNumCalls > 0)
Rule (RFI-145):
Type:Inter-field Condition and Constraint
Test Condition:tkPartitionUsage = 13
Constraint:(MaxNumCalls = 1)
Remarks:MaxNumCalls for an Intercom line must be set to 1
Rule (RI-80):
Type:Default (Defines a default value)
Rule Name:Max Calls Default Setting
Description:Maximum Calls for a Line Appearance is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), defaults are read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The default MaxCalls for a device that supports this feature is the lesser of a) the Default MaxCalls setting in the parameter value or b) the total MaxCalls for the device minus the sum of MaxCalls settings for all other lines on the current device (excluding the current line). If the feature is not supported, MaxCalls is set to 2.
Test Condition:SELECT ParamValue FROM ProductSupportsFeature WHERE (tkSupportsFeature = 30) AND (tkProduct = @Device.tkProduct)
Rule (RI-94):
Type:Validation (Insert/Update)
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
Rule (RI-94):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
2.3.95.16 numplanindex (FI-282)
Type:long
Migration Source:NumPlan.Line
Remarks:While this is unique per device, there is no requirement for the index to be sequential nor to begin with a particular value per device.
Rule (RI-86):
Type:Validation (Insert/Update)
Rule Name:Associate DNs with Devices
Description:A Directory Number (NumPlan.tkPatternUsage = 2) can only be associated with Phones (including Device Profiles), CTI Route Points, and FXS Gateway Ports
Test Condition:?
Rule (RI-87):
Type:Validation (Insert/Update)
Rule Name:Associate Route Pattern with Devices
Description:A Route Pattern (NumPlan.tkPatternUsage = 5) can only be associated with a single Gateway, Trunk, Hunt List or Route List.
Test Condition:?
Rule (RI-89):
Type:Validation (Insert/Update)
Rule Name:Route Group Member Exclusion
Description:A Route Group cannot contain a device that already has an association to a Route Pattern, nor devices that are already members of a Route Group.
Test Condition:?
Rule (RI-90):
Type:Validation (Insert/Update)
Rule Name:Gateway Port in Route Group
Description:If an individual port on a gateway is assigned to a Route Group, the entire device cannot be assigned to a Route Group, nor can it be associated with a Route Pattern. The remaining individual ports can be assigned to the same or a different Route Group.
Test Condition:?
Rule (RI-95):
Type:Warning (Message for UI only)
Rule Name:Deleting Line 1 from Phone
Description:Warn user if Line 1 of a phone is not configured (or DN is removed)
Test Condition:IF (SELECT COUNT (*) FROM DeviceNumPlanMap WHERE (NumPlanIndex = 1) AND (fkDevice = @Device.pkid) = 0) THEN warn
Error Message:Deleting the directory number for Line 1 is not recommended because basic phone features require Line 1 to operate correctly.
Remedy:Add a new DN to Line 1 of this phone to ensure that the other lines on this phone will work properly.
Rule (RI-229):
Type:Validation (Insert/Update)
Rule Name:ValidateDevNumPlanIndex
Description:A device (phone) cannot have the same line more than once.
Test Condition:ON INSERT/UPDATE INTO DeviceNumPlanMap IF (SELECT COUNT(*) INTO nRows FROM DeviceNumPlanMap WHERE (fkDevice = new_fkDevice) AND NumPlanIndex = new_NumPlanIndex) AND (fkPartitionUsage = new_tkPartitionUsage)) > 1 THEN throw exception;
Error Message:Duplicate phone line.
Remedy:?
2.3.95.17 pkid (FI-280)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:generated, new table gets all records in NumPlan
Remarks:Unique ID to identify a record.
Rule (RI-94):
Type:Validation (Insert/Update)
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
Rule (RI-225):
Type:Active (Insert)
Rule Name:Increment DevNumPlanMap Ctiid
Description:On Insert only
Test Condition:?
Rule (RI-228):
Type:Validation (Insert/Update)
Rule Name:ValidateFXSPortDN
Description:For CAT6K FXS ports. Model_Elvis type devices if there are more than one device/same dn associations in devicenumplanmap then its an error.
Test Condition:?
Error Message:FXS port is not shareable.
Remedy:?
Rule (RI-362):
Type:Active (Insert)
Rule Name:Insert RecordDynamic record if recording is supported
Description:For each line on a device that supports Recording, insert a record in RecordDynamic with a reference back to the new DeviceNumPlanMap record
Test Condition:ON INSERT into DeviceNumPlanMap: INSERT INTO RecordDynamic (pkid, fkDeviceNumPlanMap) VALUES (newid(), @DeviceNumPlanMap.pkid)
2.3.95.18 speeddial (FI-3254)
Type:dn (Null OK)
DN Type:DN_TYPE_ALL_DIGITS
Default Value:NULL
Validation:^[0-9*#+]{0,48}$
Remarks:This is the number that the system dials when the user presses the feature (Intercom) button.
2.3.95.19 tkmwlpolicy (FI-1076)
Type:enum
Default Value:0
Rule (RFI-146):
Type:Inter-field Condition and Constraint
Test Condition:tkPartitionUsage = 13
Constraint:(tkMWLPolicy = 0)
Remarks:MWL Policy cannot be set for an Intercom line
Rule (RI-287):
Type:Validation (Insert/Update)
Rule Name:MWL Policy feature restriction
Description:MWL Policy can be set to non-default only on devices that support the Message Waiting Lamp Policy feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@tkMWLPolicy<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MWL_POLICY) THEN throw exception
Error Message:Message Waiting Lamp Policy is not supported on the device where this line appears
Remedy:Use the default MWL Policy setting.
2.3.95.20 tkpartitionusage (FI-3253)
Type:enum (Not Modifiable)
Default Value:99
Check Constraint:tkPartitionUsage!=21
Remarks:Identifies entries belonging to Line or Intercom features
Rule (RI-93):
Type:Validation (Insert/Update)
Rule Name:Shared Line Support Required
Description:If product support for shared line is not present, DN cannot be associated with more than one device.
Test Condition:IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = 8) AND (tkProduct = @Device.tkProduct) = 0) AND (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE (fkNumPlan = @NumPlan.pkid) > 1) THEN throw exception
Rule (RI-94):
Type:Validation (Insert/Update)
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
Rule (RI-229):
Type:Validation (Insert/Update)
Rule Name:ValidateDevNumPlanIndex
Description:A device (phone) cannot have the same line more than once.
Test Condition:ON INSERT/UPDATE INTO DeviceNumPlanMap IF (SELECT COUNT(*) INTO nRows FROM DeviceNumPlanMap WHERE (fkDevice = new_fkDevice) AND NumPlanIndex = new_NumPlanIndex) AND (fkPartitionUsage = new_tkPartitionUsage)) > 1 THEN throw exception;
Error Message:Duplicate phone line.
Remedy:?
2.3.95.21 tkpreferredmediasource (FI-21026)
Type:enum
Default Value:1
Remarks:where is recording controlled from.
Rule (RI-960):
Type:Validation (Insert/Update)
Rule Name:PreferredMediaSource can only be Phone if related device type supports full recoding
Description:When line appearance has PreferredMediaSource set to phone, the associated device must fully support recording
Test Condition:On INSERT / UPDATE on DEVICENUMPLANMAP IF tkPreferredMediaSource = PREFERRED_MEDIA_SOURCE_PHONE THEN IF Device D WHERE D.pkid = fkDevice AND productsupportsfeature where tksupportsfeature = SUPPORTS_FEATURE_RECORD AND param in (empty or full) AND d.tkdeviceprotocol AND D.tkproduct
Error Message:Device type does not support recording from through phone
Remedy:Set preferred media source to gateway.
Rule (RI-960):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:PreferredMediaSource can only be Phone if related device type supports full recoding
Description:When line appearance has PreferredMediaSource set to phone, the associated device must fully support recording
Test Condition:On INSERT / UPDATE on DEVICENUMPLANMAP IF tkPreferredMediaSource = PREFERRED_MEDIA_SOURCE_PHONE THEN IF Device D WHERE D.pkid = fkDevice AND productsupportsfeature where tksupportsfeature = SUPPORTS_FEATURE_RECORD AND param in (empty or full) AND d.tkdeviceprotocol AND D.tkproduct
Error Message:Device type does not support recording from through phone
Remedy:Set preferred media source to gateway.
2.3.95.22 tkringsetting (FI-575)
Type:enum
Default Value:4
Migration Source:DeviceNumPlanMap.ringDisable
Rule (RFI-147):
Type:Inter-field Condition and Constraint
Test Condition:tkPartitionUsage = 13
Constraint:(tkRingSetting = 4)
Remarks:Ring Setting (Idle) cannot be set for an Intercom line
Rule (RI-175):
Type:Validation (Insert/Update)
Rule Name:Ring Setting Options for Idle Device
Description:The options for Ring Setting on an idle phone do not include the beep option that is available when the phone is off-hook. Beep is not a valid option for the idle ring setting of a line (tkRingSetting), but is valid for the ring setting in active state (tkRingSetting_Consecutive).
Test Condition:IF (@DeviceNumPlanMap.tkRingSetting NOT IN (SELECT Enum FROM TypeRingSetting WHERE isLineCompatible = 1)) THEN throw exception
Error Message:The specified Ring Setting is not valid.
Remedy:Use a Ring Setting that is line compatible (TypeRingSetting.isLineCompatible = 1).
Rule (RI-288):
Type:Validation (Insert/Update)
Rule Name:Ring Setting feature restriction
Description:Ring Settings can be set to non-default value only for devices that support the Disable Ring feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (tkRingSetting<>0) OR (tkRingSetting_Consecutive<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_DISABLE_RING) THEN throw exception
Error Message:Ring settings are not supported on the device where this line appears.
Remedy:Use the default ring settings.
Rule (RI-288):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Ring Setting feature restriction
Description:Ring Settings can be set to non-default value only for devices that support the Disable Ring feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (tkRingSetting<>0) OR (tkRingSetting_Consecutive<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_DISABLE_RING) THEN throw exception
Error Message:Ring settings are not supported on the device where this line appears.
Remedy:Use the default ring settings.
2.3.95.23 tkringsetting_activepickupalert (FI-3177)
Type:enum (Null OK)
Default Value:NULL
Check Constraint:(tkRingSetting_ActivePickupAlert = 0) OR (tkRingSetting_ActivePickupAlert = 1) OR (tkRingSetting_ActivePickupAlert = 5)
Remarks:Pickup Audio Alert Settings
Rule (RFI-149):
Type:Inter-field Condition and Constraint
Test Condition:tkPartitionUsage = 13
Constraint:(tkRingSetting_ActivePickupAlert IS NULL)
Remarks:Ring Setting (Idle Pickup Alert) cannot be set for an Intercom line (must be NULL)
Rule (RI-350):
Type:Validation (Insert/Update)
Rule Name:Ring Setting for Pickup Alert must be supported by device type
Description:Ring Setting for Pickup Alert can only be set on lines associated with devices that support the feature
Test Condition:ON INSERT/UPDATE in DeviceNumPlanMap: SELECT tkProduct, tkDeviceProtocol INTO product, protocol FROM Device WHERE pkid = new_fkDevice; SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tkSupportsFeature = SUPPORTS_DISABLE_RING AND tkProduct = product AND tkProtocol IN (protocol, 99); IF (nRows = 0) AND (new_tkRingSetting_IdlePickupAlert IS NOT NULL) OR (new_tkRingSetting_ActivePickupAlert IS NOT NULL) THEN throw exception END IF;
Error Message:This device does not support the Pickup Alert feature
Rule (RI-350):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Ring Setting for Pickup Alert must be supported by device type
Description:Ring Setting for Pickup Alert can only be set on lines associated with devices that support the feature
Test Condition:ON INSERT/UPDATE in DeviceNumPlanMap: SELECT tkProduct, tkDeviceProtocol INTO product, protocol FROM Device WHERE pkid = new_fkDevice; SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tkSupportsFeature = SUPPORTS_DISABLE_RING AND tkProduct = product AND tkProtocol IN (protocol, 99); IF (nRows = 0) AND (new_tkRingSetting_IdlePickupAlert IS NOT NULL) OR (new_tkRingSetting_ActivePickupAlert IS NOT NULL) THEN throw exception END IF;
Error Message:This device does not support the Pickup Alert feature
2.3.95.24 tkringsetting_consecutive (FI-1220)
Type:enum (Null OK)
Default Value:0
Rule (RFI-148):
Type:Inter-field Condition and Constraint
Test Condition:tkPartitionUsage = 13
Constraint:(tkRingSetting_Consecutive IS NULL) OR (tkRingSetting_Consecutive = 0)
Remarks:Ring Setting (Active) cannot be set for an Intercom line
Rule (RI-288):
Type:Validation (Insert/Update)
Rule Name:Ring Setting feature restriction
Description:Ring Settings can be set to non-default value only for devices that support the Disable Ring feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (tkRingSetting<>0) OR (tkRingSetting_Consecutive<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_DISABLE_RING) THEN throw exception
Error Message:Ring settings are not supported on the device where this line appears.
Remedy:Use the default ring settings.
Rule (RI-288):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Ring Setting feature restriction
Description:Ring Settings can be set to non-default value only for devices that support the Disable Ring feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (tkRingSetting<>0) OR (tkRingSetting_Consecutive<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_DISABLE_RING) THEN throw exception
Error Message:Ring settings are not supported on the device where this line appears.
Remedy:Use the default ring settings.
2.3.95.25 tkringsetting_idlepickupalert (FI-3178)
Type:enum (Null OK)
Default Value:NULL
Check Constraint:(tkRingSetting_IdlePickupAlert =0) OR (tkRingSetting_IdlePickupAlert =1) OR (tkRingSetting_IdlePickupAlert =3)
Remarks:Pickup Audio Alert Settings
Rule (RFI-150):
Type:Inter-field Condition and Constraint
Test Condition:tkPartitionUsage = 13
Constraint:(tkRingSetting_IdlePickupAlert IS NULL)
Remarks:Ring Setting (Active Pickup Alert) cannot be set for an Intercom line (must be NULL)
Rule (RI-350):
Type:Validation (Insert/Update)
Rule Name:Ring Setting for Pickup Alert must be supported by device type
Description:Ring Setting for Pickup Alert can only be set on lines associated with devices that support the feature
Test Condition:ON INSERT/UPDATE in DeviceNumPlanMap: SELECT tkProduct, tkDeviceProtocol INTO product, protocol FROM Device WHERE pkid = new_fkDevice; SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tkSupportsFeature = SUPPORTS_DISABLE_RING AND tkProduct = product AND tkProtocol IN (protocol, 99); IF (nRows = 0) AND (new_tkRingSetting_IdlePickupAlert IS NOT NULL) OR (new_tkRingSetting_ActivePickupAlert IS NOT NULL) THEN throw exception END IF;
Error Message:This device does not support the Pickup Alert feature
Rule (RI-350):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Ring Setting for Pickup Alert must be supported by device type
Description:Ring Setting for Pickup Alert can only be set on lines associated with devices that support the feature
Test Condition:ON INSERT/UPDATE in DeviceNumPlanMap: SELECT tkProduct, tkDeviceProtocol INTO product, protocol FROM Device WHERE pkid = new_fkDevice; SELECT count(*) INTO nRows FROM ProductSupportsFeature WHERE tkSupportsFeature = SUPPORTS_DISABLE_RING AND tkProduct = product AND tkProtocol IN (protocol, 99); IF (nRows = 0) AND (new_tkRingSetting_IdlePickupAlert IS NOT NULL) OR (new_tkRingSetting_ActivePickupAlert IS NOT NULL) THEN throw exception END IF;
Error Message:This device does not support the Pickup Alert feature
2.3.95.26 tkstatus_audiblemwi (FI-3277)
Type:enum
Default Value:2
Remarks:On/Off/Default setting for Audible Message Waiting Indication on a line appearance
Rule (RI-361):
Type:Validation (Insert/Update)
Rule Name:Audible MWI feature restriction
Description:Audible MWI status can be set to non-default only on devices that support the Message Waiting Lamp Policy feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@tkMWLPolicy<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MWL_POLICY) THEN throw exception
Error Message:Audible Message Waiting Indicator is not supported on the device where this line appears
Remedy:Use the default Audible MWI status setting.
Rule (RI-361):
Type:Validation (Insert/Update)
This field is modified by this rule.
Rule Name:Audible MWI feature restriction
Description:Audible MWI status can be set to non-default only on devices that support the Message Waiting Lamp Policy feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (@tkMWLPolicy<>0) AND (SELECT tkProduct from Device where pkid = @fkDevice) NOT IN (Select tkproduct from PSF where tkSupportsFeature = SUPPORTS_FEATURE_MWL_POLICY) THEN throw exception
Error Message:Audible Message Waiting Indicator is not supported on the device where this line appears
Remedy:Use the default Audible MWI status setting.
Uniqueness:fkdevice + fknumplan is unique. (MFI-6)
Constraints:
Rule (RFI-109):
Type:Inter-field Condition and Constraint
Constraint:BusyTrigger <= MaxNumCalls
Remarks:Busy Trigger must be less than or equal to Max Calls setting for a line appearance.
Rules:
Rule (RI-2):
Type:Active (Insert)
Rule applied when record is inserted.
Rule Name:Generate CTI ID value
Description:On insert of a new record generate a unique 32-bit integer value and store the result in the CTI ID field
Test Condition:On Insert
Rule (RI-84):
Type:Active (Insert/Update/Delete records)
Rule applied when record is inserted or updated.
Rule Name:AutoAnswer Off for Shared Line
Description:If the number of devices (not including Extension Mobility Device Profiles) associated with a DN is greater than 1, the AutoAnswer setting must be OFF (0).
Test Condition:?
Rule (RI-85):
Type:Active (Delete)
Rule applied when record is inserted or updated.
Rule Name:Set unassociated DN IsCallable to False
Description:When the last association between a DN and a device or profile is removed, set the IsCallable field for the DN's NumPlan record to false.
Test Condition:ON DELETE from DeviceNumPlanMap IF (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE (fkNumPlan = @NumPlan.pkid) = 0) THEN SET NumPlan.isCallable = 'F'
Rule (RI-93):
Type:Validation (Insert/Update)
Rule applied when record is inserted or updated.
Rule Name:Shared Line Support Required
Description:If product support for shared line is not present, DN cannot be associated with more than one device.
Test Condition:IF (SELECT COUNT(*) FROM ProductSupportsFeature WHERE (tkSupportsFeature = 8) AND (tkProduct = @Device.tkProduct) = 0) AND (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE (fkNumPlan = @NumPlan.pkid) > 1) THEN throw exception
Rule (RI-94):
Type:Validation (Insert/Update)
Rule applied when record is inserted or updated.
Rule Name:Maximum MaxCalls Per Device/Line
Description:The upper limit for Maximum Calls for a Line Appearance (DeviceNumPlanMap.MaxCalls) is calculated on a per-line basis as follows: If the device supports feature Multiple Call Display (ProductSupportsFeature.tkSupportsFeature = SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY), the limit is read from the parameter in ProductSupportsFeature. The parameter indicates MaxCalls (total for device) : Default Max Calls : Default Busy Trigger. The current value must be less than MaxCalls limit for the device minus the sum of MaxCalls configured for all lines on the phone excluding the current line. If Multiple Call Display is not supported, MaxCalls is set to 2
Test Condition:?
Rule (RI-101):
Type:Active (Insert/Update/Delete records)
Rule applied when record is updated.
This table is modified by this rule.
Rule Name:Sync Device Profile on Device Changes
Description:If the information related to a device with an autogenerated device profile changes, and the enterprise parameter for autosync profiles is true, then the autogenerated device profile must be re-generated. This includes changes to the DeviceAddonModuleMap, Telecaster, Telecaster SubscribedServices, SpeedDial, and DeviceNumPlanMap tables.
Test Condition:(SELECT COUNT(*) FROM ProcessConfig WHERE (ParamName = 'AutosyncDeviceProfile') AND (ParamValue = 'T') > 0) AND (SELECT tkDeviceProfile FROM Device WHERE (pkid = @Device.ikDevice_DefaultDeviceProfile) = 2) AND (SELECT LoginTime FROM Device WHERE (pkid = @Device.pkid) != 0)
Rule (RI-170):
Type:Active (Insert/Update/Delete records)
Rule applied when record is deleted.
Rule Name:DN Not Callable when removed from last Device
Description:If a DN is no longer used by any device, it is automatically marked not callable in the database. The Administrator may then manually mark the DN callable again so that forwarding is enabled for that DN.
Test Condition:ON DELETE FROM DeviceNumPlanMap IF ((SELECT COUNT(*) FROM DeviceNumPlanMap WHERE DeviceNumPlanMap.fkNumPlan = @fkNumPlan) = 0) THEN UPDATE NumPlan SET IsCallable = 0 WHERE pkid = @fkNumPlan
Rule (RI-171):
Type:Validation (Insert/Update)
Rule applied when record is inserted.
Rule Name:Multiple DeviceNumPlanMap for Shared DN Only
Description:DeviceNumPlanMap may contain multiple records with the same fkNumPlan only if the referenced NumPlan record is a DN (type = Device).
Test Condition:IF ((SELECT Count(*) FROM DeviceNumPlanMap WHERE fkNumPlan = @DeviceNumPlanMap.fkNumPlan) > 1 AND (SELECT tkPatternUsage FROM NumPlan WHERE pkid = @DeviceNumPlanMap.fkNumPlan) != 2) THEN throw exception
Error Message:Only directory numbers can be shared by more than one device.
Remedy:Check the type of NumPlan record you are associating with a device to make sure it is a DN, or if it is not a DN, check to make sure no other devices are associated with it.
Rule (RI-212):
Type:Validation (Insert/Update)
Rule applied when record is inserted or updated.
Rule Name:Only one DN (line) associated with Pilot Point
Description:CTI Route Point used as Pilot Point may have only one associated DN (DeviceNumPlanMap record).
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMap IF (SELECT COUNT(*) FROM DeviceNumPlanMap WHERE DeviceNumPlanMap.fkDevice = Device.pkid) > 1 THEN throw exception.
Error Message:Pilot Point may have only one line (associated Directory Number).
Remedy:Remove existing DN from Pilot Point and try again.
Rule (RI-215):
Type:Validation (Insert/Update)
Rule applied when record is inserted or updated.
Rule Name:CTI Device lines must allow CTI Control
Description:The lines (NumPlan records) associated with a CTI Route Point or CTI Port must allow CTI Control. CTI Control can be restricted only for other non-CTI types of devices.
Test Condition:ON INSERT/UPDATE IN NumPlan, DeviceNumPlanMap IF (SELECT COUNT(*) FROM NumPlan n INNER JOIN DeviceNumPlanMap map ON n.pkid = map.fkNumPlan INNER JOIN Device d ON d.pkid = map.fkDevice WHERE n.pkid = @NumPlan.pkid AND n.AllowCTIControlFlag = FALSE AND d.tkModel IN (72,73)) > 0 THEN throw exception
Error Message:Cannot disable CTI Control on a line that is associated with a CTI Port or CTI Route Point.
Remedy:Allow CTI Control for the line (NumPlan record), or remove any association with CTI Port or CTI Route Point devices.

 
2.3.96 devicenumplanmapendusermap (TI-438)
Description:Settings for SIP Publication of line status for presence
Fields:
2.3.96.1 fkdevicenumplanmap (FI-3274)
Type:guid (Cascade Delete)
Remarks:Line appearance being monitored for status
Rule (RI-365):
Type:Validation (Insert/Update)
Rule Name:Maximum 5 EndUsers per line appearance for SIP Publish
Description:No more than 5 endusers can be associated with a line appearance (DeviceNumPlanMap record) for SIP Publish feature
Test Condition:ON INSERT/UPDATE IN DeviceNumPlanMapEndUserMap: IF (SELECT COUNT(*) INTO nRows FROM DeviceNumPlanMapEndUserMap WHERE fkDeviceNumPlanMap = new_fkDeviceNumPlanMap) > 5 THEN throw exception
Error Message:No more than 5 EndUsers can be subscribed to receive status for a line appearance.
2.3.96.2 fkenduser (FI-3275)
Type:guid (Cascade Delete)
Remarks:EndUser to whom status information is be published
2.3.96.3 pkid (FI-3273)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:fkdevicenumplanmap + fkenduser is unique. (MFI-100)

 
2.3.97 devicenumplanmapremdestmap (TI-454)
Description:Maps Remote Destinations to the template or dual mode phone lines with which they are used
Fields:
2.3.97.1 fkdevicenumplanmap (FI-3407)
Type:guid (Cascade Delete)
Remarks:Line from template or Dual Mode phone that is used for Remote Destination
2.3.97.2 fkremotedestination (FI-3406)
Type:guid (Cascade Delete)
Remarks:Remote Destination using the line for Single Number Reach (SNR)
2.3.97.3 pkid (FI-3405)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints
Constraints:
Rule (RFI-667):
Type:Inter-field Condition and Constraint
Constraint:(NOT EXISTS (SELECT 1 FROM devicenumplanmapremdestmap M WHERE pkid != M.pkid AND fkremotedestination = M.fkremotedestination AND fkdevicenumplanmap = M.fkdevicenumplanmap))
Remarks:Cannot add the same Remote Destination to the same device or profile more than once.

 
2.3.98 devicepool (TI-13)
Description:Common collections of device attributes
Fields:
2.3.98.1 calledinternationalprefix (FI-3872)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called International Prefix
2.3.98.2 calledinternationalstripdigits (FI-3883)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledInternationalStripDigits >= 0) AND (CalledInternationalStripDigits <= 24)
Remarks:Called International Strip Digits
2.3.98.3 callednationalprefix (FI-3871)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called National Prefix
2.3.98.4 callednationalstripdigits (FI-3882)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledNationalStripDigits >= 0) AND (CalledNationalStripDigits <= 24)
Remarks:Called National Strip Digits
2.3.98.5 calledsubscriberprefix (FI-3874)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called Subscriber Prefix
2.3.98.6 calledsubscriberstripdigits (FI-3885)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledSubscriberStripDigits >= 0) AND (CalledSubscriberStripDigits <= 24)
Remarks:Called Subscriber Strip Digits
2.3.98.7 calledunknownprefix (FI-3873)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Called Unknown Prefix
2.3.98.8 calledunknownstripdigits (FI-3884)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(CalledUnknownStripDigits >= 0) AND (CalledUnknownStripDigits <= 24)
Remarks:Called Unknown Strip Digits
2.3.98.9 connectionmonitorduration (FI-2096)
Type:long
Default Value:-1
Check Constraint:(ConnectionMonitorDuration >= -1) AND (ConnectionMonitorDuration <= 2592000)
2.3.98.10 fkaarneighborhood (FI-3179)
Type:guid (Null OK)
Default Value:NULL
2.3.98.11 fkcallingsearchspace_aar (FI-3180)
Type:guid (Null OK)
Default Value:NULL
2.3.98.12 fkcallingsearchspace_adjunct (FI-3998)
Type:guid (Null OK)
Default Value:NULL
Remarks:For emergency call during cross cluster EM login
2.3.98.13 fkcallingsearchspace_autoregistration (FI-589)
Type:guid (Null OK)
Default Value:NULL
Remarks:This is the calling search space to assign to devices in this device pool that auto-registers with Cisco CallManager. The calling search space specifies partitions that devices can search when attempting to complete a call.
2.3.98.14 fkcallingsearchspace_calledintl (FI-3887)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party International Number
2.3.98.15 fkcallingsearchspace_callednational (FI-3886)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party National Number
2.3.98.16 fkcallingsearchspace_calledsubscriber (FI-3889)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party Subscriber Number
2.3.98.17 fkcallingsearchspace_calledunknown (FI-3888)
Type:guid (Null OK)
Default Value:NULL
Remarks:Called Party Unknown Number
2.3.98.18 fkcallingsearchspace_cdpntransform (FI-3508)
Type:guid (Null OK)
Default Value:NULL
Remarks:If useDevicePoolCdpnTransformCSS is set to True this transformation will be applied on the called party
2.3.98.19 fkcallingsearchspace_cgpningressdn (FI-10179)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling search space applied to calling party number on ingress from the calling device
2.3.98.20 fkcallingsearchspace_cgpnintl (FI-5120)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party International Number
2.3.98.21 fkcallingsearchspace_cgpnnational (FI-5119)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party National Number
2.3.98.22 fkcallingsearchspace_cgpnsubscriber (FI-5122)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party Subscriber Number
2.3.98.23 fkcallingsearchspace_cgpntransform (FI-3520)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party Transformation Number
2.3.98.24 fkcallingsearchspace_cgpnunknown (FI-5121)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Party Unknown Number
2.3.98.25 fkcallingsearchspace_cntdpntransform (FI-5754)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Search Space for Connected Party Name Transformation Pattern
2.3.98.26 fkcallingsearchspace_mobility (FI-3181)
Type:guid (Null OK)
Default Value:NULL
2.3.98.27 fkcallingsearchspace_rdntransform (FI-9927)
Type:guid (Null OK)
Default Value:NULL
Remarks:If useDevicePoolRdnTransformCSS is set to True this transformation will be applied on the Redirecting Number
2.3.98.28 fkcallmanagergroup (FI-151)
Type:guid
Migration Source:convert from CallManagerGroup
Remarks:This is the Cisco CallManager group to assign to devices in this device pool. A Cisco CallManager group specifies a prioritized list of up to three Cisco CallManagers. The first Cisco CallManager in the list serves as the primary Cisco CallManager for that group, and the other members of the group serve as backup Cisco CallManagers for redundancy.
2.3.98.29 fkdatetimesetting (FI-150)
Type:guid
Migration Source:convert from DateTimeGroup
Remarks:This is the date/time group to assign to devices in this device pool. The date/time group specifies the time zone and the display formats for date and time.
2.3.98.30 fkdevicemobilitygroup (FI-3182)
Type:guid (Null OK)
Default Value:NULL
2.3.98.31 fkelingroup (FI-26913)
Type:guid (Null OK)
Remarks:ELINGroup record used by this DevicePool
2.3.98.32 fkgeolocation (FI-5004)
Type:guid (Null OK)
Default Value:NULL
2.3.98.33 fkgeolocationfilter_lp (FI-5005)
Type:guid (Null OK)
Default Value:NULL
2.3.98.34 fklocation (FI-3183)
Type:guid (Null OK)
Default Value:NULL
2.3.98.35 fkmediaresourcelist (FI-995)
Type:guid (Null OK)
Default Value:NULL
Remarks:This is the media resource group list associated with the device pool. A media resource group list specifies a prioritized list of media resource groups. An application selects the required media resource (for example, a music on hold server, transcoder, or conference bridge) from the available media resource groups according to the priority order that is defined in a media resource group list.
2.3.98.36 fkphysicallocation (FI-3184)
Type:guid (Null OK)
Default Value:NULL
2.3.98.37 fkregion (FI-149)
Type:guid
Migration Source:convert from Region
Remarks:This is the Cisco CallManager region to assign to devices in this device pool. The Cisco CallManager region settings specify voice codec that can be used for calls within a region and between other regions.
2.3.98.38 fksrst (FI-1218)
Type:guid
Default Value:cd241e11-4a58-4d3d-9661-f06c912a18a3
Remarks:This is the survivable remote site telephony (SRST) reference to assign to devices in this device pool.
2.3.98.39 fkviprpublisheddidpatterngroup (FI-5289)
Type:guid (Null OK)
Default Value:NULL
2.3.98.40 fkwirelesslanprofilegroup (FI-25714)
Type:guid (Null OK)
Remarks:Reference to Wireless LAN Profile Group.
2.3.98.41 internationalprefix (FI-3517)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:International Prefix
2.3.98.42 internationalstripdigits (FI-5116)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(InternationalStripDigits >= 0) AND (InternationalStripDigits <= 24)
Remarks:International Strip Digits
2.3.98.43 name (FI-148)
Type:string [50] (Unique)
Validation:^[a-zA-Z 0-9._-]{1,50}$
Migration Source:DevicePoolName
Remarks:A unique name.
2.3.98.44 nationalprefix (FI-3516)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:National Prefix
2.3.98.45 nationalstripdigits (FI-5115)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(NationalStripDigits >= 0) AND (NationalStripDigits <= 24)
Remarks:National Strip Digits
2.3.98.46 pkid (FI-147)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
2.3.98.47 resettoggle (FI-3072)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
2.3.98.48 subscriberprefix (FI-3519)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Subscriber Prefix
2.3.98.49 subscriberstripdigits (FI-5118)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(SubscriberStripDigits >= 0) AND (SubscriberStripDigits <= 24)
Remarks:Subscriber Strip Digits
2.3.98.50 tkbarge (FI-3468)
Type:enum
Default Value:3
2.3.98.51 tkcountry (FI-1037)
Type:enum (Null OK)
Default Value:NULL
2.3.98.52 tkreset (FI-3073)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
2.3.98.53 tkrevertpriority (FI-3185)
Type:enum
Default Value:0
2.3.98.54 tkstatus_joinacrosslines (FI-3467)
Type:enum
Default Value:2
2.3.98.55 unknownprefix (FI-3518)
Type:string [16]
Default Value:Default
Validation:^([0-9*#+]{0,16}|[Dd]efault)$
Remarks:Unknown Prefix
2.3.98.56 unknownstripdigits (FI-5117)
Type:long (Null OK)
Default Value:NULL
Check Constraint:(UnknownStripDigits >= 0) AND (UnknownStripDigits <= 24)
Remarks:Unknown Strip Digits
2.3.98.57 versionstamp (FI-3116)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid plus seconds past midnight 1970 are concatenated
Rule (RI-216):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
Rule (RI-216):
Type:Active (Insert/Update)
Rule Name:device versionstamp
Description:on change to anything in device xml file, update versionstamp
Test Condition:update device
Uniqueness:No multicolumn uniqueness constraints

 
2.3.99 devicepooldevicemobilityinfomap (TI-422)
Description:Used for DeviceMobility.
Fields:
2.3.99.1 fkdevicemobilityinfo (FI-3186)
Type:guid (Cascade Delete)
2.3.99.2 fkdevicepool (FI-3187)
Type:guid (Cascade Delete)
2.3.99.3 pkid (FI-3188)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Uniqueness:fkdevicemobilityinfo + fkdevicepool is unique. (MFI-97)

 
2.3.100 devicepoolroutegroupmap (TI-2131)
Description:Used for mapping multiple Route Groups to a Device Pool. According to the Multiple Local Route Group feature, we can assign more than one Route Groups to a Device Pool. So this table is used for mapping between the two.
Fields:
2.3.100.1 fkdevicepool (FI-21155)
Type:guid (Cascade Delete, Null OK)
Remarks:reference to device pool
Rule (RI-962):
Type:Validation (Insert/Update)
Rule Name:Insert/Update on DevicePoolRouteGroupMap
Description:On insert/update on the DevicePoolRouteGroupMap table, the fkRouteGroup_local should contain the fk to RouteGroup only if isLocalRouteGroup is set to true and fkRouteGroup should contain the fk to RouteGroup only if isLocalRouteGroup is set to false. Also it checks for the combination of fkDevicePool and fkRouteGroup_Local to be unique.
Test Condition:On I/U on DevicePoolRouteGroupMap, SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup_Local; IF (isLRG <> 't') THEN throw exception; SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup; IF (isLRG <> 'f') THEN throw exception; IF EXISTS (SELECT 1 FROM DevicePoolRouteGroupMap WHERE fkDevicePool=new_fkDevicePool AND fkRouteGroup_Local=new_fkRouteGroup_Local) THEN throw exception;
2.3.100.2 fkroutegroup (FI-21157)
Type:guid (Cascade Delete)
Remarks:fkRouteGroup should contain the fk to route group only if isLocalRouteGroup is set to false. This field is mandatory as it will point to the actual Route Group that will be used for handling all the Route related activities.
Rule (RI-962):
Type:Validation (Insert/Update)
Rule Name:Insert/Update on DevicePoolRouteGroupMap
Description:On insert/update on the DevicePoolRouteGroupMap table, the fkRouteGroup_local should contain the fk to RouteGroup only if isLocalRouteGroup is set to true and fkRouteGroup should contain the fk to RouteGroup only if isLocalRouteGroup is set to false. Also it checks for the combination of fkDevicePool and fkRouteGroup_Local to be unique.
Test Condition:On I/U on DevicePoolRouteGroupMap, SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup_Local; IF (isLRG <> 't') THEN throw exception; SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup; IF (isLRG <> 'f') THEN throw exception; IF EXISTS (SELECT 1 FROM DevicePoolRouteGroupMap WHERE fkDevicePool=new_fkDevicePool AND fkRouteGroup_Local=new_fkRouteGroup_Local) THEN throw exception;
2.3.100.3 fkroutegroup_local (FI-21156)
Type:guid (Cascade Delete, Null OK)
Default Value:NULL
Remarks:fkRouteGroup_local should contain the fk to route group only if isLocalRouteGroup is set to true. The value in this field will just be used to give a name to the actual route group that is being used.
Rule (RI-962):
Type:Validation (Insert/Update)
Rule Name:Insert/Update on DevicePoolRouteGroupMap
Description:On insert/update on the DevicePoolRouteGroupMap table, the fkRouteGroup_local should contain the fk to RouteGroup only if isLocalRouteGroup is set to true and fkRouteGroup should contain the fk to RouteGroup only if isLocalRouteGroup is set to false. Also it checks for the combination of fkDevicePool and fkRouteGroup_Local to be unique.
Test Condition:On I/U on DevicePoolRouteGroupMap, SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup_Local; IF (isLRG <> 't') THEN throw exception; SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup; IF (isLRG <> 'f') THEN throw exception; IF EXISTS (SELECT 1 FROM DevicePoolRouteGroupMap WHERE fkDevicePool=new_fkDevicePool AND fkRouteGroup_Local=new_fkRouteGroup_Local) THEN throw exception;
2.3.100.4 pkid (FI-21154)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
Rule (RI-962):
Type:Validation (Insert/Update)
Rule Name:Insert/Update on DevicePoolRouteGroupMap
Description:On insert/update on the DevicePoolRouteGroupMap table, the fkRouteGroup_local should contain the fk to RouteGroup only if isLocalRouteGroup is set to true and fkRouteGroup should contain the fk to RouteGroup only if isLocalRouteGroup is set to false. Also it checks for the combination of fkDevicePool and fkRouteGroup_Local to be unique.
Test Condition:On I/U on DevicePoolRouteGroupMap, SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup_Local; IF (isLRG <> 't') THEN throw exception; SELECT IsLocalRouteGroup INTO isLRG FROM RouteGroup WHERE pkid = new_fkRouteGroup; IF (isLRG <> 'f') THEN throw exception; IF EXISTS (SELECT 1 FROM DevicePoolRouteGroupMap WHERE fkDevicePool=new_fkDevicePool AND fkRouteGroup_Local=new_fkRouteGroup_Local) THEN throw exception;
Uniqueness:No multicolumn uniqueness constraints

 
2.3.101 deviceprivacydynamic (TI-435)
Description:Frequently updated settings for Privacy
Insert/Delete is not allowed.
Fields:
2.3.101.1 datetimestamp (FI-3302)
Type:long
Default Value:0
Rule (RI-400):
Type:Active (Insert/Update)
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
Rule (RI-400):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:Update the DateTimeStamp for Dynamic records
Description:When a record in a Dynamic table is updated, set the DateTimeStamp to the current time value
Test Condition:ON INSERT/UPDATE INTO *Dynamic: LET currentTime = dbinfo('utc_current'); return currentTime (INTO DateTimeStamp);
2.3.101.2 fkdevice (FI-3301)
Type:guid (Unique, Cascade Delete)
2.3.101.3 pkid (FI-3300)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.101.4 tkstatus_callinfoprivate (FI-1305)
Type:enum
Default Value:2
Remarks:display call info to caller?
Uniqueness:No multicolumn uniqueness constraints

 
2.3.102 deviceprovidermap (TI-975)
Description:CUBA: This table will contains information about device configuration to provider mapping, so admin will know using which provider device is configured
Is not replicated.
Fields:
2.3.102.1 fkdevice (FI-6211)
Type:guid (Unique, Indexed, Cascade Delete)
Remarks:Device for providerdevicemap record
2.3.102.2 fkprovider (FI-6212)
Type:guid (Indexed)
Remarks:Provider for providerdevicemap record
2.3.102.3 pkid (FI-6210)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique identifier for providerdevicemap record
2.3.102.4 tkcubadevice (FI-6213)
Type:enum
Remarks:CubaDevice type for providerdevicemap record
2.3.102.5 versionnumber (FI-6214)
Type:long
Remarks:This will store the version number of the provider in providerdevicemap
Uniqueness:No multicolumn uniqueness constraints

 
2.3.103 devicerelatedversionstamp (TI-626)
Description:List of Devices that requires versionstamp update
Insert/Delete is not allowed.
Fields:
2.3.103.1 fkdevice (FI-5652)
Type:guid (Unique, Indexed, Cascade Delete)
Migration Source:convert from Device
Remarks:Pkid of the Device
2.3.103.2 pkid (FI-5651)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.103.3 versionstamp (FI-5653)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid plus seconds past midnight 1970 are concatenated and is generated every time this device is updated
Uniqueness:No multicolumn uniqueness constraints

 
2.3.104 devicereset (TI-253)
Description:For device reset functionality. Records inserted into this table will inform CCM to reset the device.
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.104.1 devicepkid (FI-2098)
Type:guid (Not Modifiable, Null OK)
Default Value:NULL
Remarks:Set by DeviceReset stored procedure.
2.3.104.2 fkcallmanager (FI-2046)
Type:guid (Cascade Delete, Not Modifiable)
Remarks:Set by DeviceReset stored procedures.
2.3.104.3 name (FI-1781)
Type:string [129] (Not Modifiable, Null OK)
Default Value:EMPTY
Remarks:Set by DeviceReset stored procedure.
2.3.104.4 pkid (FI-1780)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.104.5 resetgrouping (FI-3021)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record. will be same for all reset requests
2.3.104.6 tkmodel (FI-1783)
Type:enum (Not Modifiable)
Remarks:Set by DeviceReset stored procedure.
2.3.104.7 tkreset (FI-1782)
Type:enum (Not Modifiable)
Remarks:Set by DeviceReset stored procedure.
2.3.104.8 tkresethandshake (FI-3018)
Type:enum (Not Modifiable)
Remarks:Set the reset to ensure tftp reacts to it before actual device reset.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.105 devicesipdevicemap (TI-2156)
Description:Keep multi function device records for mapping between Device and SIPDeivce record.
Fields:
2.3.105.1 fkdevice (FI-21273)
Type:guid (Indexed, Cascade Delete)
Remarks:Reference to a specific Device
2.3.105.2 fksipdevice (FI-21274)
Type:guid (Indexed)
Remarks:Points to the corresponding SIP Device record.
2.3.105.3 pkid (FI-21272)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Uniqueness:No multicolumn uniqueness constraints

 
2.3.106 devicetftpdynamic (TI-465)
Description:VersionStamp Mismatch Recovery
Fields:
2.3.106.1 fkdevice (FI-3470)
Type:guid (Unique, Indexed, Cascade Delete, Not Modifiable)
Migration Source:convert from DeviceName
Remarks:Points to the device record being "subclassed." Device.tkModel must be tkclass=1.
2.3.106.2 pkid (FI-3469)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.106.3 rebuildtoggle (FI-3471)
Type:bool
Default Value:FALSE
Remarks:Should this device be rebuilt
Uniqueness:No multicolumn uniqueness constraints

 
2.3.107 devicexml16k (TI-937)
Description:Defines the product specific configuration for devices:16K
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.107.1 fkdevice (FI-5740)
Type:guid (Unique, Indexed, Cascade Delete)
Migration Source:convert from Device
Remarks:Pkid of the Device corresponding to the XML column of DeviceXML16L table
2.3.107.2 pkid (FI-5739)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.107.3 xml (FI-5741)
Type:string [16000]
Migration Source:Device.xml
Remarks:Product configuration XML for DeviceXML16K
Uniqueness:No multicolumn uniqueness constraints

 
2.3.108 devicexml4k (TI-934)
Description:Defines the product specific configuration for devices:4K
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.108.1 fkdevice (FI-5702)
Type:guid (Unique, Indexed, Cascade Delete)
Migration Source:convert from Device
Remarks:Pkid of the Device corresponding to the XML column of DeviceXML4K table
2.3.108.2 pkid (FI-5701)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.108.3 xml (FI-5704)
Type:string [4000] (Null OK)
Default Value:NULL
Migration Source:Device.xml
Remarks:Product configuration XML for DeviceXML4K
Uniqueness:No multicolumn uniqueness constraints

 
2.3.109 devicexml8k (TI-936)
Description:Defines the product specific configuration for devices:8K
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.109.1 fkdevice (FI-5737)
Type:guid (Unique, Indexed, Cascade Delete)
Migration Source:convert from Device
Remarks:Pkid of the Device corresponding to the XML column of DeviceXML8K table
2.3.109.2 pkid (FI-5736)
Type:guid (Unique, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.109.3 xml (FI-5738)
Type:string [8000]
Migration Source:Device.xml
Remarks:Product configuration XML for DeviceXML8K
Uniqueness:No multicolumn uniqueness constraints

 
2.3.110 dhcpserver (TI-292)
Description:(not supported yet)DHCP server configuration
Fields:
2.3.110.1 arpcachetimeout (FI-2055)
Type:long
Default Value:0
Check Constraint:(ARPCacheTimeout >=0) AND (ARPCacheTimeout < 1073741824)
Remarks:server
2.3.110.2 domainname (FI-2034)
Type:string [64]
Default Value:EMPTY
Validation:^[a-zA-Z 0-9._-]{1,64}$
Remarks:domain name
2.3.110.3 domainnameserver1 (FI-2029)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for primary dns
2.3.110.4 domainnameserver2 (FI-2030)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for secondary dsn
2.3.110.5 fkprocessnode (FI-2028)
Type:guid (Unique, Cascade Delete)
Remarks:Associated server
2.3.110.6 ipaddrleasetime (FI-2056)
Type:long
Default Value:0
Check Constraint:(IPAddrLeaseTime >=0) AND (IPAddrLeaseTime < 1073741824)
Remarks:server
2.3.110.7 nextserver (FI-2033)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for the next server cisco tftp
2.3.110.8 pkid (FI-2026)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.110.9 t1 (FI-2057)
Type:long
Default Value:0
Check Constraint:(T1 >= 0) AND (T1 < 1073741824)
Remarks:server
2.3.110.10 t2 (FI-2058)
Type:long
Default Value:0
Check Constraint:(T2 >= 0) AND (T2 < 1073741824)
Remarks:server
2.3.110.11 tftpserver1 (FI-2031)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for the primary cisco tftp
2.3.110.12 tftpserver2 (FI-2032)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for secondary cisco tftp
2.3.110.13 tftpservername (FI-2082)
Type:string [64]
Default Value:EMPTY
Validation:^[0-9a-zA-Z._-]{0,64}$
Remarks:tftp server name (option 150)
Uniqueness:No multicolumn uniqueness constraints

 
2.3.111 dhcpsubnet (TI-293)
Description:(not supported yet)DHCP subnet configuration
Fields:
2.3.111.1 arpcachetimeout (FI-2045)
Type:long
Default Value:0
Check Constraint:(ARPCacheTimeout >= 0) AND (ARPCacheTimeout < 1073741824)
Remarks:subnet
2.3.111.2 domainname (FI-2044)
Type:string [64]
Default Value:EMPTY
Validation:^[a-zA-Z 0-9._-]{1,64}$
Remarks:subnet
2.3.111.3 domainnameserver1 (FI-2083)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for primary dns
2.3.111.4 domainnameserver2 (FI-2084)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for secondary dsn
2.3.111.5 fkdhcpserver (FI-2035)
Type:guid (Cascade Delete)
Remarks:Associated server
2.3.111.6 ipaddrfrom1 (FI-2037)
Type:string [17]
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.7 ipaddrfrom2 (FI-2038)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.8 ipaddrleasetime (FI-2088)
Type:long
Default Value:0
Check Constraint:(IPAddrLeaseTime >= 0) AND (IPAddrLeaseTime < 1073741824)
Remarks:server
2.3.111.9 ipaddrto1 (FI-2039)
Type:string [17]
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.10 ipaddrto2 (FI-2040)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.11 nextserver (FI-2089)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for the next server cisco tftp
2.3.111.12 pkid (FI-2027)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.111.13 router1 (FI-2041)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.14 router2 (FI-2042)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.15 subnet (FI-2036)
Type:string [17]
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.16 subnetmask (FI-2043)
Type:string [17]
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:subnet
2.3.111.17 t1 (FI-2091)
Type:long
Default Value:0
Check Constraint:(T1 >= 0) AND (T1 < 1073741824)
Remarks:server
2.3.111.18 t2 (FI-2092)
Type:long
Default Value:0
Check Constraint:(T2 >= 0) AND (T2 < 1073741824)
Remarks:server
2.3.111.19 tftpserver1 (FI-2085)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for the primary cisco tftp (option 66)
2.3.111.20 tftpserver2 (FI-2086)
Type:string [17]
Default Value:EMPTY
Validation:^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])$
Remarks:IP Address for secondary cisco tftp (option 66)
2.3.111.21 tftpservername (FI-2093)
Type:string [64]
Default Value:EMPTY
Validation:^[0-9a-zA-Z._-]{0,64}$
Remarks:tftp server name (option 150)
Uniqueness:fkdhcpserver + subnet is unique. (MFI-69)

 
2.3.112 dialplan (TI-107)
Description:List of known dial plans
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.112.1 description (FI-552)
Type:string [50] (Not Modifiable)
Default Value:EMPTY
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{0,50}$
Migration Source:automatic
2.3.112.2 name (FI-550)
Type:string [50] (Unique, Not Modifiable)
Validation:^[]a-zA-Z0-9 !#$'()*+,./:;=?@[^_`{|}~-]{1,50}$
Migration Source:automatic
2.3.112.3 pkid (FI-549)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.112.4 version (FI-3032)
Type:string [15]
Default Value:1.1(0)
Remarks:Version number of the installed Dial Plan
Uniqueness:No multicolumn uniqueness constraints

 
2.3.113 dialplandetails (TI-573)
Description:CUBA: This table will be used to store different parameters for dial plan e.g. Extension no length, FeaturePrefix etc.
Is not replicated.
Fields:
2.3.113.1 defaultvalue (FI-6003)
Type:string [40] (Null OK)
Remarks:Default value for parameters in dialplandetail table
2.3.113.2 paramname (FI-6001)
Type:string [50]
Remarks:ParamName for dialplandetails
2.3.113.3 paramvalue (FI-6002)
Type:string [40]
Validation:^[a-zA-Z 0-9,#@-]{1,40}$
Remarks:ParamValue for dialplandetails
2.3.113.4 pkid (FI-6000)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique id for dialplandetails table
Uniqueness:No multicolumn uniqueness constraints

 
2.3.114 dialplantag (TI-97)
Description:Tag name for a portion of a directory number used by digit analysis
Records may be modified only by installation and/or DB triggers.
Fields:
2.3.114.1 fkdialplan (FI-561)
Type:guid (Cascade Delete, Not Modifiable)
2.3.114.2 pkid (FI-392)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.114.3 suppressfromroutefilter (FI-762)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:Don't show this tag in RouteFilterMember.
2.3.114.4 tag (FI-455)
Type:string [50] (Not Modifiable)
Default Value:EMPTY
Migration Source:automatic
2.3.114.5 tkoperator_max (FI-761)
Type:enum (Not Modifiable)
Default Value:3
Remarks:Maximum value for operator in RouteFilterMember for this tag
Uniqueness:tag + fkdialplan is unique. (MFI-23)

 
2.3.115 dialrules (TI-330)
Description:Dial Rules
Fields:
2.3.115.1 description (FI-2854)
Type:string [100] (Null OK)
Default Value:EMPTY
Remarks:Description of the dial rule
2.3.115.2 isstandard (FI-2459)
Type:bool (Not Modifiable)
Default Value:FALSE
Remarks:Whether standard dial rule
2.3.115.3 name (FI-2457)
Type:string [50] (Unique, Indexed)
Remarks:Name of dial rule
2.3.115.4 pkid (FI-2456)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
Rule (RI-301):
Type:Active (Insert/Update)
Rule Name:dialrules versionstamp
Description:on change to anything in dialrules, update versionstamp in dialrules table
Test Condition:update dialrules
2.3.115.5 resettoggle (FI-3074)
Type:bool
Default Value:FALSE
Remarks:Should this device or group be reset
Rule (RI-301):
Type:Active (Insert/Update)
Rule Name:dialrules versionstamp
Description:on change to anything in dialrules, update versionstamp in dialrules table
Test Condition:update dialrules
2.3.115.6 tkdialpattern (FI-2458)
Type:enum
Default Value:2
Remarks:Pkid of Dial Pattern record
2.3.115.7 tkreset (FI-3075)
Type:enum
Default Value:2
Remarks:Set by DeviceReset stored procedure.
2.3.115.8 versionstamp (FI-3117)
Type:string [47] (Null OK)
Default Value:0000000000-c7a6c673-7479-46b0-839e-014d3d093963
Remarks:New guid plus seconds past midnight 1970 are concatenated
Rule (RI-301):
Type:Active (Insert/Update)
This field is modified by this rule.
Rule Name:dialrules versionstamp
Description:on change to anything in dialrules, update versionstamp in dialrules table
Test Condition:update dialrules
Rule (RI-301):
Type:Active (Insert/Update)
Rule Name:dialrules versionstamp
Description:on change to anything in dialrules, update versionstamp in dialrules table
Test Condition:update dialrules
Uniqueness:No multicolumn uniqueness constraints

 
2.3.116 dialrulespatternmap (TI-329)
Description:DialRules Pattern Map
Fields:
2.3.116.1 description (FI-2871)
Type:string [100] (Null OK)
Default Value:EMPTY
Remarks:Description of pattern on dial rule
2.3.116.2 fkdialrules (FI-2453)
Type:guid (Cascade Delete)
Remarks:Pkid of DialRules record
Rule (RI-260):
Type:Active (Insert/Update/Delete records)
Rule Name:dialrules versionstamp
Description:on change to anything in dialrulespatternmap, patternparametermap, update versionstamp in dialrules table
Test Condition:update dialrules
2.3.116.3 pkid (FI-2452)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.116.4 selectionorder (FI-2455)
Type:long
Remarks:Selection order
2.3.116.5 tkpattern (FI-2454)
Type:enum
Remarks:Enum of TypePattern record
Uniqueness:No multicolumn uniqueness constraints

 
2.3.117 digitalaccessbri (TI-223)
Description:Digital access BRI information not in Device table
Fields:
2.3.117.1 acceptinboundrdnis (FI-1608)
Type:bool
Default Value:FALSE
2.3.117.2 calleriddn (FI-1587)
Type:dn (Null OK)
DN Type:DN_TYPE_MASK
Default Value:NULL
Validation:^[0-9*#+X]{0,32}$
2.3.117.3 dchannelenable (FI-1600)
Type:bool
Default Value:TRUE
2.3.117.4 displayie (FI-1605)
Type:bool
Default Value:FALSE
2.3.117.5 firstdelay (FI-1584)
Type:long
2.3.117.6 fkdevice (FI-1575)
Type:guid (Indexed, Cascade Delete)
Remarks:device::tModel must be digital access
Rule (RI-104):
Type:Validation (Insert/Update)
Rule Name:DigitalAccessBri device
Description:The records in DigitalAccessBri table must reference a device using DigitalAccessBri device protocol (10).
Test Condition:DigitalAccessBri.fkDevice IN (SELECT pkid FROM Device where tkDeviceProtocol = 10)
Error Message:DigitalAccessBri table may only reference devices with matching Device Protocol (DigitalAccessBri).
Remedy:Correct the fkDevice value to refer to a Digital Access BRI device.
2.3.117.7 gclearenable (FI-10004)
Type:bool
Default Value:FALSE
Remarks:Enables G.Clear support for a BRI trunk (using values specified in G.Clear related Service Parameters)
2.3.117.8 intradelay (FI-1585)
Type:long
2.3.117.9 numberie (FI-1606)
Type:bool
Default Value:FALSE
2.3.117.10 numdigits (FI-1580)
Type:long
Check Constraint:((NumDigits >= 0) AND (NumDigits <= 32)) OR (NumDigits = 99)
2.3.117.11 pkid (FI-1574)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Remarks:Unique ID to identify a record.
2.3.117.12 prefix (FI-1578)
Type:dn (Null OK)
DN Type:DN_TYPE_ALL_DIGITS
Default Value:NULL
Validation:^[0-9*#+]{0,50}$
2.3.117.13 sendrestart (FI-1583)
Type:bool
2.3.117.14 setupnonisdnpiflag (FI-1607)
Type:bool
Default Value:FALSE
2.3.117.15 sigdigits (FI-1579)
Type:bool
Default Value:FALSE
Remarks:Must be 1 if (NumDigits >= 0) AND (NumDigits <= 32), or 0 if (NumDigits = 99)
2.3.117.16 stablein4 (FI-2166)
Type:bool
Default Value:FALSE
2.3.117.17 statuspoll (FI-1581)
Type:bool
2.3.117.18 stripcountout (FI-1586)
Type:long
2.3.117.19 tkbriprotocol (FI-1576)
Type:enum
2.3.117.20 tkcallingpartyselection (FI-1589)
Type:enum
Remarks:Source of the calling party number: originator = 1, first redirect = 2, last redirect = 3
2.3.117.21 tkclockreference (FI-1588)
Type:enum
Remarks:Indicates if the device sync up with the Network clock or use it's own clock for timing
2.3.117.22 tkcsuparam (FI-1591)
Type:enum
Remarks:TX-level CSU parameter for PRI interface
2.3.117.23 tkencode (FI-1592)
Type:enum
Default Value:1
Migration Source:chanie
2.3.117.24 tkfdlchannel (FI-1603)
Type:enum
Default Value:0
2.3.117.25 tkframing (FI-1602)
Type:enum
Default Value:1
2.3.117.26 tknumberingplan_called (FI-1595)
Type:enum
Default Value:0
2.3.117.27 tknumberingplan_calling (FI-1596)
Type:enum
Default Value:0
2.3.117.28 tkpresentationbit (FI-1590)
Type:enum
Remarks:CLID presentationBit: allowed = 1, restricted = 2
2.3.117.29 tkpriofnumber_called (FI-1594)
Type:enum
Default Value:0
2.3.117.30 tkpriofnumber_calling (FI-1593)
Type:enum
Default Value:0
2.3.117.31 tktrunklevel (FI-1599)
Type:enum
Default Value:7
2.3.117.32 tktrunkpad_rx (FI-1597)
Type:enum
Default Value:32
2.3.117.33 tktrunkpad_tx (FI-1598)
Type:enum
Default Value:32
2.3.117.34 tktrunkselectionorder (FI-1577)
Type:enum
Default Value:1
Migration Source:Direction
2.3.117.35 tkyellowalarm (FI-1604)
Type:enum
Default Value:1
2.3.117.36 tkzerosuppression (FI-1601)
Type:enum
Default Value:0
Uniqueness:No multicolumn uniqueness constraints

 
2.3.118 digitalaccesspri (TI-14)
Description:Digital access PRI information not in Device table
Fields:
2.3.118.1 acceptinboundrdnis (FI-1087)
Type:bool
Default Value:TRUE
2.3.118.2 calleriddn (FI-56)
Type:dn (Null OK)
DN Type:DN_TYPE_MASK
Default Value:NULL
Validation:^[0-9*#+X]{0,32}$
Migration Source:CallerID
2.3.118.3 dchannelenable (FI-710)
Type:bool
Default Value:TRUE
2.3.118.4 displayie (FI-775)
Type:bool
Default Value:TRUE
2.3.118.5 enableprotectedfacilityie (FI-3686)
Type:bool
Default Value:FALSE
Remarks:Allows use of secure calls (on PRI E1 trunks only)
Rule (RFI-192):
Type:Inter-field Condition and Constraint
Test Condition:tkPriProtocol <> 9
Constraint:(EnableProtectedFacilityIE = 'f')
Remarks:EnableProtectedFacilityIE can be True only for DigitalAccessPri gateways configured to use the PRI-EURO protocol
2.3.118.6 firstdelay (FI-53)
Type:long
Default Value:32
Migration Source:FirstDelay
2.3.118.7 fkcallingsearchspace_cntdpntransform (FI-21160)
Type:guid (Null OK)
Default Value:NULL
Remarks:Calling Search Space for Connected Party Number Transformation Pattern
2.3.118.8 fkdevice (FI-42)
Type:guid (Indexed, Cascade Delete)
Migration Source:convert from Device
Remarks:device::tModel must be digital access
Rule (RI-28):
Type:Active (Insert/Update)
Rule Name:Set QSIG on DigitalAccessPri device and Configuration of E1 links that are PRI EURO protocol type for MLPP is allowed.
Description:Update the QSIG setting on the Digital Access device whenever the PRI Protocol settings is changed from QSIG to non-QSIG, or non-QSIG to QSIG. And if device is E1 and MLPP Indication <> 0 Or MLPP Preemption <> 0 Then if PriProtocol <> PRI_EURO then throw exception
Test Condition:ON INSERT/UPDATE/DELETE IN DigitalAccessPRI IF (@tkPriProtocol <> tkPriProtol) THEN (set tkqsig on device where device.pkid = digitalaccesspri.fkdevice)
Rule (RI-40):
Type:Validation (Update)
Rule Name:QSIG Protocol Change Restriction
Description:If a Digital Access PRI gateway is a member of a Route Group, the PRI Protocol of the gateway cannot be changed from a non-QSIG protocol to QSIG, or from a QSIG to non-QSIG PRI Protocol.
Test Condition:SELECT COUNT(*) FROM RouteGroupDeviceMap WHERE fkDevice = @Device.pkid AND Device.tkDeviceProtocol = 1
Error Message:Cannot change a QSIG device to a non-QSIG PRI Protocol while the device is a member of a Route Group.
Remedy:Remove the device from the Route Group to which it belongs and then change the PRI Protocol.
Rule (RI-105):
Type:Validation (Insert/Update)
Rule Name:DigitalAccessPri device
Description:The records in DigitalAccessPri table must reference a device using DigitalAccessPri device protocol (1)
Test Condition:DigitalAccessPri.fkDevice IN (SELECT pkid FROM Device where tkDeviceProtocol = 1)
Error Message:DigitalAccessPri table may only reference devices with matching Device Protocol (DigitalAccessPri).
Remedy:Correct the fkDevice value to refer to a Digital Access PRI device.
Rule (RI-599):
Type:Validation (Insert/Update)
Rule Name:GClear can not be enabled for E1 gateway
Description:GClear can not be enabled for E1 gateway
Test Condition:On Insert or Update DigitalAccessPri
Error Message:GClear can not be enabled for E1 gateway
Rule (RI-632):
Type:Validation (Insert/Update)
Rule Name:Route Class Signaling support required for Route Class Signaling Enable
Description:Route Class Signaling Enabled setting must be OFF for devices that do not support Route Class Signaling feature (tkSupportsFeature = 94)
Test Condition:ON INSERT/UPDATE IN DigitalAccessPRI:
Error Message:This Device does not support Route Class Signaling (RouteClassSignalingEnabled setting)
Remedy:Set RouteClassSignalingEnabled to off and try again
Rule (RI-716):
Type:Validation (Insert/Update)
Rule Name:G.Clear is not supported on the PRI interface on this type of gateway. Make sure EnableGClear is set to false and try again.
Description:G.Clear is not supported on the PRI interface on this type of gateway. Make sure EnableGClear is set to false and try again.
Test Condition:On Insert or Update DigitalAccessPri
Error Message:G.Clear is not supported on the PRI interface on this type of gateway. Make sure EnableGClear is set to false and try again.
2.3.118.9 gclearenable (FI-3483)
Type:bool
Default Value:FALSE
Remarks:Enables G.Clear support for a PRI trunk (using values specified in G.Clear related Service Parameters)
Rule (RI-599):
Type:Validation (Insert/Update)
Rule Name:GClear can not be enabled for E1 gateway
Description:GClear can not be enabled for E1 gateway
Test Condition:On Insert or Update DigitalAccessPri
Error Message:GClear can not be enabled for E1 gateway
Rule (RI-716):
Type:Validation (Insert/Update)
Rule Name:G.Clear is not supported on the PRI interface on this type of gateway. Make sure EnableGClear is set to false and try again.
Description:G.Clear is not supported on the PRI interface on this type of gateway. Make sure EnableGClear is set to false and try again.
Test Condition:On Insert or Update DigitalAccessPri
Error Message:G.Clear is not supported on the PRI interface on this type of gateway. Make sure EnableGClear is set to false and try again.
2.3.118.10 interfaceidentifierpresent (FI-773)
Type:bool
Default Value:FALSE
2.3.118.11 interfaceidentifiervalue (FI-774)
Type:long
Default Value:0
2.3.118.12 intradelay (FI-54)
Type:long
Default Value:4
Migration Source:IntraDelay
2.3.118.13 mcdnenable (FI-1180)
Type:bool
Default Value:FALSE
2.3.118.14 numberie (FI-776)
Type:bool
Default Value:TRUE
2.3.118.15 numdigits (FI-48)
Type:long
Check Constraint:((NumDigits >= 0) AND (NumDigits <= 32)) OR (NumDigits = 99)
Migration Source:NumDigits
2.3.118.16 passingprecedencelevelthroughuuie (FI-2167)
Type:bool
Default Value:FALSE
2.3.118.17 pkid (FI-41)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.118.18 prefix (FI-46)
Type:dn (Null OK)
DN Type:DN_TYPE_ALL_DIGITS
Default Value:NULL
Validation:^[0-9*#+]{0,50}$
Migration Source:Prefix
2.3.118.19 protocolprofile91nameonly (FI-2168)
Type:bool
Default Value:FALSE
2.3.118.20 securityaccesslevel (FI-2169)
Type:long
Default Value:2
Check Constraint:(SecurityAccessLevel >= 0) AND (SecurityAccessLevel <= 99)
2.3.118.21 sendcallingnameinfacilityie (FI-1361)
Type:bool
Default Value:FALSE
2.3.118.22 sendexleadingcharindispie (FI-1026)
Type:bool
Default Value:TRUE
2.3.118.23 sendrestart (FI-52)
Type:bool
Default Value:TRUE
Migration Source:SendRestart
2.3.118.24 setupnonisdnpiflag (FI-992)
Type:bool
Default Value:FALSE
2.3.118.25 sigdigits (FI-47)
Type:bool
Default Value:FALSE
Migration Source:SigDigits
Remarks:Must be 1 if (NumDigits >= 0) AND (NumDigits <= 32), or 0 if (NumDigits = 99)
2.3.118.26 smdibaseport (FI-1221)
Type:long
Default Value:0
Check Constraint:(SMDIBasePort>= 0) AND (SMDIBasePort<= 4096)
2.3.118.27 span (FI-43)
Type:long
Check Constraint:(Span >= 0) AND (Span <= 1)
Migration Source:Span
2.3.118.28 statuspoll (FI-49)
Type:bool
Migration Source:StatusPoll
2.3.118.29 stripcountout (FI-55)
Type:long
Default Value:0
Migration Source:StripCountOut
2.3.118.30 tkasn1roseoidencoding (FI-3766)
Type:enum
Default Value:0
Rule (RI-583):
Type:Validation (Insert/Update)
Rule Name:DigitalAccessPRI.tkASN1RoseOidEncoding and DigitalAccessPRI.tkQSIGVariant Change Restriction
Description:If tkPriProtocol is not enabled for qsigthen tkASN1RoseOidEncoding or tkQSIGVariant in the DigitalAccessPRI table should not be allowed to change from DEFAULT to NON DEFAULT
Test Condition:ON INSERT or UPDATE in DigitalAccessPRI: SELECT count(enum) INTO nRows from typepriprotocol where enum = new.tkpriprotocol and isqsig = 't'; IF (nrows=0) throw exception END IF;
Error Message:Cannot modify the value since qsig is not enabled for this device
Remedy:Enable the QSIG and change the value
2.3.118.31 tkcallingpartyselection (FI-59)
Type:enum
Default Value:1
Migration Source:CallingPartySelection
Remarks:Source of the calling party number: originator = 1, first redirect = 2, last redirect = 3
2.3.118.32 tkclockreference (FI-58)
Type:enum
Migration Source:ClockReference
Remarks:Indicates if the device sync up with the Network clock or use it's own clock for timing
2.3.118.33 tkconnectedpbx (FI-1334)
Type:enum
Default Value:0
2.3.118.34 tkcsuparam (FI-62)
Type:enum
Migration Source:CSUParam
Remarks:TX-level CSU parameter for PRI interface
2.3.118.35 tkencode (FI-640)
Type:enum
Default Value:1
2.3.118.36 tkfdlchannel (FI-715)
Type:enum
Default Value:0
2.3.118.37 tkframing (FI-713)
Type:enum
Default Value:1
2.3.118.38 tknumberingplan_called (FI-687)
Type:enum
Default Value:0
2.3.118.39 tknumberingplan_calling (FI-688)
Type:enum
Default Value:0
2.3.118.40 tkpresentationbit_callingline (FI-1335)
Type:enum
Default Value:0
Migration Source:PresentationBit
Remarks:CLID presentationBit: allowed = 1, restricted = 2
2.3.118.41 tkpresentationbit_connectedline (FI-1333)
Type:enum
Default Value:0
Migration Source:PresentationBit
Remarks:CLID presentationBit: allowed = 1, restricted = 2
2.3.118.42 tkprichanie (FI-50)
Type:enum
Default Value:2
Migration Source:ChanIE
2.3.118.43 tkpriofnumber_called (FI-674)
Type:enum
Default Value:0
Migration Source:based on TypePriOfNumber
2.3.118.44 tkpriofnumber_calling (FI-673)
Type:enum
Default Value:0
Migration Source:based on TypePriOfNumber
2.3.118.45 tkpriprotocol (FI-44)
Type:enum
Migration Source:Protocol
Rule (RI-28):
Type:Active (Insert/Update)
Rule Name:Set QSIG on DigitalAccessPri device and Configuration of E1 links that are PRI EURO protocol type for MLPP is allowed.
Description:Update the QSIG setting on the Digital Access device whenever the PRI Protocol settings is changed from QSIG to non-QSIG, or non-QSIG to QSIG. And if device is E1 and MLPP Indication <> 0 Or MLPP Preemption <> 0 Then if PriProtocol <> PRI_EURO then throw exception
Test Condition:ON INSERT/UPDATE/DELETE IN DigitalAccessPRI IF (@tkPriProtocol <> tkPriProtol) THEN (set tkqsig on device where device.pkid = digitalaccesspri.fkdevice)
Rule (RI-40):
Type:Validation (Update)
Rule Name:QSIG Protocol Change Restriction
Description:If a Digital Access PRI gateway is a member of a Route Group, the PRI Protocol of the gateway cannot be changed from a non-QSIG protocol to QSIG, or from a QSIG to non-QSIG PRI Protocol.
Test Condition:SELECT COUNT(*) FROM RouteGroupDeviceMap WHERE fkDevice = @Device.pkid AND Device.tkDeviceProtocol = 1
Error Message:Cannot change a QSIG device to a non-QSIG PRI Protocol while the device is a member of a Route Group.
Remedy:Remove the device from the Route Group to which it belongs and then change the PRI Protocol.
Rule (RI-583):
Type:Validation (Insert/Update)
Rule Name:DigitalAccessPRI.tkASN1RoseOidEncoding and DigitalAccessPRI.tkQSIGVariant Change Restriction
Description:If tkPriProtocol is not enabled for qsigthen tkASN1RoseOidEncoding or tkQSIGVariant in the DigitalAccessPRI table should not be allowed to change from DEFAULT to NON DEFAULT
Test Condition:ON INSERT or UPDATE in DigitalAccessPRI: SELECT count(enum) INTO nRows from typepriprotocol where enum = new.tkpriprotocol and isqsig = 't'; IF (nrows=0) throw exception END IF;
Error Message:Cannot modify the value since qsig is not enabled for this device
Remedy:Enable the QSIG and change the value
2.3.118.46 tkqsigvariant (FI-3768)
Type:enum
Default Value:0
Rule (RI-583):
Type:Validation (Insert/Update)
Rule Name:DigitalAccessPRI.tkASN1RoseOidEncoding and DigitalAccessPRI.tkQSIGVariant Change Restriction
Description:If tkPriProtocol is not enabled for qsigthen tkASN1RoseOidEncoding or tkQSIGVariant in the DigitalAccessPRI table should not be allowed to change from DEFAULT to NON DEFAULT
Test Condition:ON INSERT or UPDATE in DigitalAccessPRI: SELECT count(enum) INTO nRows from typepriprotocol where enum = new.tkpriprotocol and isqsig = 't'; IF (nrows=0) throw exception END IF;
Error Message:Cannot modify the value since qsig is not enabled for this device
Remedy:Enable the QSIG and change the value
2.3.118.47 tkstatus_routeclasssignalingenabled (FI-3935)
Type:enum (Indexed)
Default Value:0
Remarks:Indicates whether Route Class Signaling is enabled on a PRI trunk
Rule (RFI-250):
Type:Inter-field Condition and Constraint
Test Condition:tkPriProtocol NOT IN (2,3,4,5,6,7,8,9,10,22)
Constraint:(tkStatus_RouteClassSignalingEnabled = 0)
Remarks:tkStatus_RouteClassSignalingEnabled MUST be Off for PRI protocols that don't suppport the feature (see Help pages for list of supported protocols)
Rule (RI-632):
Type:Validation (Insert/Update)
Rule Name:Route Class Signaling support required for Route Class Signaling Enable
Description:Route Class Signaling Enabled setting must be OFF for devices that do not support Route Class Signaling feature (tkSupportsFeature = 94)
Test Condition:ON INSERT/UPDATE IN DigitalAccessPRI:
Error Message:This Device does not support Route Class Signaling (RouteClassSignalingEnabled setting)
Remedy:Set RouteClassSignalingEnabled to off and try again
2.3.118.48 tktrunklevel (FI-709)
Type:enum
Default Value:7
2.3.118.49 tktrunkpad_rx (FI-707)
Type:enum
Default Value:32
2.3.118.50 tktrunkpad_tx (FI-708)
Type:enum
Default Value:32
2.3.118.51 tktrunkselectionorder (FI-45)
Type:enum
Default Value:1
Migration Source:Direction
2.3.118.52 tkyellowalarm (FI-717)
Type:enum
Default Value:1
2.3.118.53 tkzerosuppression (FI-711)
Type:enum
Default Value:0
2.3.118.54 usedpconnectedpartytransformationcss (FI-21159)
Type:bool
Default Value:TRUE
Remarks:If set to true fkCallingSearchSpace_CntdPNTransform setting from Device Pool will be used and if false use setting on DigitalAccessPri including NULL to mean no Calling Search Space. The Default value is TRUE
Uniqueness:No multicolumn uniqueness constraints

 
2.3.119 digitalaccesst1 (TI-15)
Description:Digital access T1 information not in Device table
Fields:
2.3.119.1 encodevoicerouteclass (FI-3937)
Type:bool
Default Value:FALSE
Remarks:TRUE if this T1 (CAS) i/f should signal the voice route class digit
2.3.119.2 fkdevice (FI-64)
Type:guid (Indexed, Cascade Delete)
Migration Source:convert from Device
Rule (RI-108):
Type:Validation (Insert/Update)
Rule Name:DigitalAccessT1 device
Description:The records in DigitalAccessT1 table must reference a device using DigitalAccessT1 device protocol.
Test Condition:DigitalAccessT1.fkDevice IN (SELECT pkid FROM Device where tkDeviceProtocol = 4)
Error Message:DigitalAccessT1 table may only reference devices with matching Device Protocol (DigitalAccessT1).
Remedy:Correct the fkDevice value to refer to an Digital Access T1 device.
2.3.119.3 handledtmfprecedencesignals (FI-1336)
Type:bool
Default Value:FALSE
2.3.119.4 pkid (FI-63)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.119.5 releaseguardtimer (FI-10003)
Type:long (Null OK)
Default Value:2000
Check Constraint:(ReleaseGuardTimer>= 1) AND (ReleaseGuardTimer<= 2000)
Remarks:This timer is used by gateway to release the channel back to idle state on receiving clear-forward from the far end,This timer is used to protect gateway from any race conditions that could occur when we receive Release from both sides
2.3.119.6 seizureacktime (FI-9945)
Type:long (Null OK)
Check Constraint:(SeizureAckTime>= 2) AND (SeizureAckTime<= 100)
Remarks:This is the delay (in milliseconds) between the gateway that receives seizure and sends seizure acknowledgment (ACK)
2.3.119.7 smdibaseport (FI-1222)
Type:long
Default Value:0
Check Constraint:(SMDIBasePort>= 0) AND (SMDIBasePort<= 4096)
2.3.119.8 tkclockreference (FI-67)
Type:enum
Migration Source:ClockReference
2.3.119.9 tkcsuparam (FI-69)
Type:enum
Migration Source:CSUParam
2.3.119.10 tkdigitsending (FI-1024)
Type:enum
Default Value:0
Remarks:DTMF or MF
2.3.119.11 tkencode (FI-66)
Type:enum
Migration Source:EncodeType
2.3.119.12 tkfdlchannel (FI-716)
Type:enum
Default Value:3
2.3.119.13 tkframing (FI-714)
Type:enum
Default Value:1
2.3.119.14 tkstatus_routeclasssignalingenabled (FI-3936)
Type:enum (Indexed)
Default Value:0
Remarks:Indicates whether Route Class Signaling is enabled on a CAS trunk
2.3.119.15 tktrunkselectionorder (FI-65)
Type:enum
Migration Source:TrunkSelectionOrder
2.3.119.16 tkyellowalarm (FI-718)
Type:enum
Default Value:1
2.3.119.17 tkzerosuppression (FI-712)
Type:enum
Default Value:0
Uniqueness:No multicolumn uniqueness constraints

 
2.3.120 digitalaccesst1port (TI-16)
Description:Ports on a Digital Access T1
Fields:
2.3.120.1 attendantdn (FI-75)
Type:dn (Null OK)
DN Type:DN_TYPE_ALL_DIGITS
Default Value:NULL
Validation:^[0-9*#+]{0,50}$
Migration Source:AttendantNumber
Remarks:If Inbound type call and Loop Start are Ground Start Attendant Number is needed
2.3.120.2 calleriddn (FI-90)
Type:dn (Null OK)
DN Type:DN_TYPE_MASK
Default Value:NULL
Validation:^[0-9*#+X]{0,32}$
Migration Source:CallerId
2.3.120.3 endpointid (FI-563)
Type:string [129]
Default Value:EMPTY
Migration Source:new
Remarks:User may only change the PhysicalLocation and not @domain part. Default is PhysicalLocation from MGCPDeviceTable + portNum + @domain
2.3.120.4 expecteddigits (FI-79)
Type:long
Check Constraint:(ExpectedDigits >= 0) AND (ExpectedDigits <= 32)
Migration Source:ExpectedDigits
2.3.120.5 fkdevice (FI-71)
Type:guid (Indexed, Cascade Delete)
Migration Source:convert from Device
Rule (RI-109):
Type:Validation (Insert/Update)
Rule Name:DigitalAccessT1Port device
Description:The records in DigitalAccessT1Port table must reference a device using DigitalAccessT1 device protocol (4).
Test Condition:DigitalAccessT1Port.fkDevice IN (SELECT pkid FROM Device where tkDeviceProtocol = 4)
Error Message:DigitalAccessT1Port table may only reference devices with matching Device Protocol (DigitalAccessT1).
Remedy:Correct the fkDevice value to refer to an Digital Access T1 device.
2.3.120.6 inboundcalleridenable (FI-89)
Type:bool
Migration Source:InboundCallerIdEnable
2.3.120.7 numdigits (FI-77)
Type:long
Check Constraint:(NumDigits >= 0) AND (NumDigits <= 32)
Migration Source:NumDigits
Remarks:Maximum number of digits to collect. Collects least significant to NumDigits selected
2.3.120.8 pkid (FI-70)
Type:guid (Unique, Indexed, Not Modifiable)
Default Value:newid()
Migration Source:Generated
Remarks:Unique ID to identify a record.
2.3.120.9 portnum (FI-72)
Type:long
Migration Source:PortNum
Remarks:fkDevice+PortNum are unique; 1-24; 1-8 For Vega
2.3.120.10 prefix (FI-76)
Type:dn (Null OK)
DN Type:DN_TYPE_ALL_DIGITS
Default Value:NULL
Validation:^[0-9*#+]{0,50}$
Migration Source:Prefix
Remarks:Prefix digits to apply in inbound call only.
2.3.120.11 sigdigits (FI-78)
Type:bool
Migration Source:SigDigits
Remarks:Obsolete - NumDigits is always used. Flag to allow only certain amount of digits.
2.3.120.12 timer1 (FI-83)
Type:long
Check Constraint:Timer1>= 0
Migration Source:Timer1
Remarks:In Milliseconds
2.3.120.13 timer2 (FI-84)
Type:long
Check Constraint:Timer2>= 0
Migration Source:Timer2
Remarks:In Milliseconds
2.3.120.14 timer3 (FI-85)
Type:long
Check Constraint:Timer3>= 0
Migration Source:Timer3
Remarks:In Milliseconds
2.3.120.15 timer4 (FI-86)
Type:long
Check Constraint:Timer4>= 0
Migration Source:Timer4
Remarks:In Milliseconds
2.3.120.16 timer5 (FI-87)
Type:long
Check Constraint:Timer5>= 0
Migration Sourc