Bulk import for Entity Links

Last Updated : Jan 12, 2017 |
Prolog information
Metadata
Keywords:
When creating an XML bulk import file:
  • The name of an Entity Link must be unique.
  • <entityName1> , <entityName2> must refer to an existing SIP Entity with the exact same name. It must either appear in the System Manager database or in an import file that exists in the same import operation as the Entity Link.
  • The values in <transportProtocol> must appear exactly same, being case sensitive, as they appear in the System Manager user interface.
Example
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<entitylinkFullTOList>
    <buildNumber>0</buildNumber>
    <implementationVersion>0</implementationVersion>
    <specificationVersion>0</specificationVersion>
    <EntitylinkFullTO>
        <connectionPolicy>trusted</connectionPolicy>
        <listenPortEntity1>5060</listenPortEntity1>
        <listenPortEntity2>5060</listenPortEntity2>
        <name>asm18 to cpv4</name>
        <serviceState>normal</serviceState>
        <transportProtocol>TCP</transportProtocol>
        <trusted>true</trusted>
        <entityName1>asmblade18</entityName1>
        <entityName2>cpvirtual4</entityName2>
    </EntitylinkFullTO>
    <EntitylinkFullTO>
        <notes></notes>
        <connectionPolicy>trusted</connectionPolicy>
        <listenPortEntity1>17000</listenPortEntity1>
        <listenPortEntity2>17000</listenPortEntity2>
        <name>asmblade10_asmblade24_17000_TCP</name>
        <serviceState>normal</serviceState>
        <transportProtocol>TCP</transportProtocol>
        <trusted>true</trusted>
        <entityName1>asmblade10</entityName1>
        <entityName2>asmblade24</entityName2>
    </EntitylinkFullTO>
    <EntitylinkFullTO>
        <notes></notes>
        <connectionPolicy>trusted</connectionPolicy>
        <listenPortEntity1>5060</listenPortEntity1>
        <listenPortEntity2>5060</listenPortEntity2>
        <name>asmblade10_FakeSM_5060_TCP</name>
        <serviceState>normal</serviceState>
        <transportProtocol>TCP</transportProtocol>
        <trusted>true</trusted>
        <entityName1>asmblade10</entityName1>
        <entityName2>FakeSM</entityName2>
    </EntitylinkFullTO>
</entitylinkFullTOList>
Example for IPv6 and IPv4
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<entitylinkFullTOList>
<buildNumber>0</buildNumber>
<implementationVersion>0</implementationVersion>
<specificationVersion>0</specificationVersion>
<EntitylinkFullTO>
<notes></notes>
<connectionPolicy>trusted</connectionPolicy>
<ipaddr_family>IPv6</ipaddr_family>
<listenPortEntity1>5060</listenPortEntity1>
<listenPortEntity2>5060</listenPortEntity2>
<name>sm-169_cmdummy_5060_UDP</name>
<serviceState>normal</serviceState>
<transportProtocol>UDP</transportProtocol>
<trusted>true</trusted>
<entityName1>sm-169</entityName1>
<entityName2>cmdummy</entityName2>
</EntitylinkFullTO>
<EntitylinkFullTO>
<notes></notes>
<connectionPolicy>trusted</connectionPolicy>
<ipaddr_family>IPv4</ipaddr_family>
<listenPortEntity1>5061</listenPortEntity1>
<listenPortEntity2>5061</listenPortEntity2>
<name>import sm_import cm_5061_TLS</name>
<serviceState>normal</serviceState>
<transportProtocol>TLS</transportProtocol>
<trusted>true</trusted>
<entityName1>import sm</entityName1>
<entityName2>import cm</entityName2>
</EntitylinkFullTO>
</entitylinkFullTOList>