[Index]
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 ref.: relation/HcsAssociateSipLocalGwToSiteREL
The full URL would include the host-proxy name: https://[host-proxy].
Variables are enclosed in square brackets.