[Index]

Model: relation/HcsAssociateSipLocalGwToSiteREL

ASSOCIATE SIP LOCAL GATEWAY TO SITE

Associating a SIP Local gateway to a site hierarchy node will trigger registered IOS Builder events and will trigger registered dial plan schema group custom workflows. Only SIP Local gateways that share a common CUCM cluster as specified in the site NDL and have the same country as the site can be associated with a site hierarchy node.

SHARED GATEWAY CAVEATS

Sites with the same area code(s)

In this scenario there are two possibilities: 1) All sites share the same TDM trunks to the provider -- this is supported with the default IOS Command Builder templates 2) Each site has its own TDM trunk to the provider -- this is not supported with the default IOS Command Builder templates

Sites with different area codes

In this scenario, it is unlikely the sites will be sharing the same TDM trunks. However even if they do share the same TDM trunks, it is not currently supported without having to manually modify the default IOS Command Builder templates. If the admin does deploy a shared LBO gateway to two or more sites with different area codes using the default IOS Command Builder templates, calls from one of these sites to a number that is in the same area code as another site sharing the same trunk will be treated as a local/subscriber call.

A site with its own trunk is also not supported without modifying the default IOS Command Builder templates.

Model Details

Title Description Details
SIP Local Gateway SIP Local gateway to bind to the current site. The selected SIP Local gateway must be associated with the same CUCM cluster that is referenced in the site NDL and must be targeted for the same country as the site country.
  • Field Name: sipLocalGwName
  • Type: String
  • Target: data/HcsSipLocalGwDAT
  • Target attr: name
  • MaxLength: 1024
  • Format: uri
Info Message This is a purely informative message string used to provide feedback in the CUCDM GUI when associating a SIP Local gateway to a site. When adding an instance through either the bulk loader or REST API, the value for this field does not need to be provided. Default: {{ fn.localize data.HcsLocalizedStringDat.value | key:lbo_associatetositenotice }}
  • Field Name: infoMsg
  • Type: String
  • Default: {{ fn.localize data.HcsLocalizedStringDat.value | key:lbo_associatetositenotice }}
  • MaxLength: 1024
Shadow
  • Field Name: shadow.[n]
  • Type: Array
  • Cardinality: [0..1]
Name *
  • Field Name: shadow.[n].name
  • Type: String
  • MaxLength: 1024
API reference for relation/HcsAssociateSipLocalGwToSiteREL