Prime Cable Provisioning supports these versions of the PacketCable specifications: 1.0, 1.5 and 2.0.

Prime Cable Provisioning also supports two variants of PacketCable voice services: the default Secure mode and the non-secure Basic mode. PacketCable Basic is much the same as the standard PacketCable, except for the lack of security found in the non-secure variant.

This section identifies the tasks that you must perform for each variant.

• PacketCable Basic

• PacketCable Secure

  Note	The workflows in this section assume that you have loaded an appropriate PacketCable configuration file and the correct MIBs.

Prime Cable Provisioning supports sub-option 123 of option 125 specified in RFC 3925 and sub-option 2171 of option 17 specified in RFC 3315 for provisioning PacketCable 2.0 devices. To provide server identification in DHCPv6, Prime Cable Provisioning uses the CableLabs-specific DHCP Server Selection Identifier. The eCM is provided with a primary and secondary DHCP Server Selection Identifier via sub-options 1 and 2 within DHCPv4 option CL_V4OPTION_CCCV6 (123) or DHCPv6 option CL_OPTION_CCCV6 (2171).

The value set for the DHCP Server Selection Identifier defines whether the device can provision or not. By default this value is set to ff:ff:ff:ff when packet cable is disabled. You can configure this value at the time of installation of CPNR-EP component or Using changeNRProperties.sh.

For example, if the eCM obtains a value ff:ff:ff:ff in sub-option 1 of CL_V4OPTION_CCCV6 or CL_OPTION_CCCV6, then the eUE is free to accept a valid DHCPv6 Advertise from any server, regardless of that server's DHCP Server Selection Identifier. Similarly, a value of 00:00:00:00 indicates that the eUE will not provision.

For more information about option 17.2171 and 125.123, see Option 17.2171 or 125.123 and Prime Cable Provisioning Property Comparison.

The DHCP options for DSS_ID and IP Preference will be added to the response only when the Provisioning group capability IPv6 - PacketCable 2.0 is enabled (ProvGroupCapabilitiesKeys. PACKET_CABLE_V6).

The below options will be ignored (or filtered) while generating the DHCP instructions whenever the PG capability IPv6 - PacketCable 2.0 is disabled.

• CL_V4OPTION_CCCV6(123)

• CL_V4OPTION_IP_PREF(124)

• CL_OPTION_CCCV6(2171)

• CL_OPTION_IP_PREF(39)

Note	The above options can be added to the DHCP instructions whenever IPv6 - PacketCable 2.0 capability is enabled. However the inclusion/ignoring of these options will be controlled by the following properties: /pktcbl/ipPreference /pktcbl/dssid/processing/enable

The property, /pktcbl/dssid/processing/enable (PacketCableDefaultKeys. PKTCBL_OPTION_DSS_ID_PROCESSING_ENABLE) is available to control the inclusion of DSS_ID options while generating the DHCP instructions. If this Boolean property is disabled then the below options will be ignored (or filtered) while generating the DHCP instruction.

• CL_V4OPTION_CCCV6 (123)

• CL_OPTION_CCCV6(2171)

In admin UI, DSS_ID processing options can be set at Device, Class of Service, DOCSIS Defaults, PacketCable Defaults and DHCP Criteria level in the RDU using the property /pktcbl/dssid/processing/enable. By default, the DSS_ID processing option will be disabled.

Prime Cable Provisioning now supports DHCP IP preference options CL_V4OPTION_IP_PREF (125.124) and CL_OPTION_IP_PREF (17.39). The IP preference option is requested by the DOCSIS modem (eCM:EDVA) when it is provisioned in a network. These options indicate whether the eUE must operate in single stack mode or dual stack mode for most operations (e.g., media, SIP signaling). RDU assigns IP Preference value to the PacketCable device based on its single stack or dual stack capability. These DHCP IP preference options indicate if IPv4 or IPv6 address must used for the eUE provisioning.

In the Admin UI, IP preference value can be set at Device, Class of Service, DOCSIS Defaults, and DHCP Criteria level in the RDU using the property /pcktcbl/ipPreference. This can also be configured from RDU API at any acceptable point in the property hierarchy such as, Device, Provisioning Group, Class of Service, DHCP Criteria, and Technology Defaults. By default, the IP preference value at the RDU is set to 0.

The following table describes all the IP preference values that can be set in the RDU and the corresponding Provisioning Flow.

The following table describes all the IP preference values that is sent from the device and the interpretation of the RDU for the corresponding values.

If the device does not support dual stack mode and IP Preference values set on RDU is dual stack mode value (5 or 6) then the IP preference value in the response DHCP packet will be adjusted to devices' capability.

For example, if device does not send any value for IP preference and IP Preference value set in the RDU is 5 or 6, then IP preference value sent in DHCP ack or reply packet will be set to the corresponding single stack mode values i.e., 1 or 2 respectively.

If IP preference is not set at the RDU and the device has not sent a IP preference value, RDU will ignore the generation of IP preference DHCP options for the eUE.

The following table describes the IP preference value sent in DHCP ack or reply packet depending on the IP preference values sent from the device and values set in the RDU.

A dial plan is provisioned on the UE to inform the UE about how dialed digits should be interpreted. A dial plan is an ordered set of regular expressions combined with some special tokens that represent actions to be carried out by the UE when a regular expression is matched.

The dial plan is organized into a list of rules. The UE must apply the dial plan rules sequentially and upon matching a pattern, including timers, the UE must perform the specified action or actions.

To create a dial plan you must be familiar with the notation and content of Augmented Backus-Naur Form (ABNF) defined in RFC 4234. Below is a sample dial plan that you can use as a reference.

Note	If any issues are encountered while determining the device capabilities, Prime Cable Provisioning defaults to the Secure mode. While adding a dial plan, you can either use a groovy script or a binary file but not a template.

A sample groovy file to create a dial plan

def dialPlan = '''
            TIMER S=4.000000
            TIMER Z=2.000000

            domain = "@ims.packetcable.com"
            dialString = ";user=dialstring"
            dialPhone = ";user=phone"

            homeEmergencyNumber = "911"
            localEmergencyNumber = "911"

            MAP MainTable =
            "0S" : MAKE-CALL
            "0#" : MAKE-CALL
            "00" : MAKE-CALL
            "(=Emergency)" : EMERGENCY-CALL("sip:" "911" =domain =dialPhone)
            "(=N11)" : MAKE-CALL("sip:" #1v =domain =dialString)
            "(=SpeedDial)" : MAKE-CALL("sip:" #1v =domain =dialString)
            "(=PhoneNumber)" : MAKE-CALL("sip:" #1v =domain =dialPhone)
            "(=ImmediateVSCs)" : RETURN
            "(=DelayedVSCs)" : RETURN
            "(x{1-20})S" : MAKE-CALL("sip:" #1 =domain =dialPhone)
            "(x{1-20})#" : MAKE-CALL("sip:" #1 =domain =dialPhone)
'''
* PKTC-IETF-MTA-MIB pktcMtaDevEnabled (1.3.6.1.2.1.140.1.1.6.0)
*/
configFile.add(TLV_SNMP("1.3.6.1.2.1.140.1.1.6.0", "Integer", "1"))
/*
* Device Level Configuration (Secure flow only):
* Include required Secure-flow realm TLVs
*/
if (isSecureProvFlowMode)
{
   // PKTC-IETF-MTA-MIB pktcMtaDevRealmName.1 (1.3.6.1.2.1.140.1.3.6.1.2.1)
   configFile.add(
       TLV_SNMP("1.3.6.1.2.1.140.1.3.6.1.2.1", "STRING", realmName))
   // PKTC-IETF-MTA-MIB pktcMtaDevRealmOrgName.1 (1.3.6.1.2.1.140.1.3.6.1.5.1)
       configFile.add(
       TLV_SNMP("1.3.6.1.2.1.140.1.3.6.1.5.1", "STRING", realmOrgName))
}

configFile.add(option.createOptionValue(OptionSyntax.SNMP,"64",[".pktcEUERSTDMValue.1","STRING",dialPlan]));

Note

The sample PacketCable 2.0 groovy script (example_edva.groovy) uses numeric OIDs for the PacketCable Secure-mode SNMP TLVs (pktcMtaDevRealmName, pktcMtaDevRealmOrgName). If the TLV length of Option 64 exceeds 4500, you must update the property /default/asnParser/bufferLength=20000 in /opt/CSCObac/api/conf/api.properties and in /opt/CSCObac/rdu/conf/rdu.properties.

Prime Cable Provisioning lets you enable an external network manager for SNMPv3 access to MTA devices. Additionally, the RDU is capable of performing SNMPv3 operations in a specific MTA.

To enable this capability, set the security key material at the DPEs and RDU. After the key material has been set, the Prime Cable Provisioning application programming interface (API) calls that are used to create cloned SNMPv3 entries are enabled.

Note	Enabling this capability impacts provisioning performance.

Euro-PacketCable services are essentially the European equivalent of North American PacketCable services with the following differences:

• Euro PacketCable uses different MIBs.

• Euro PacketCable uses a different set of device certificates (MTA_Root.cer) and service provider certificates (Service Provider Root).

  For Euro-PacketCable certificates, the kdc.ini file must have the euro-packetcable property set to true. The KDC supports Euro-PacketCable (tComLabs) certificate chains. The following is a sample Euro PacketCable-enabled KDC configuration file.

  
  [general]
  interface address = 10.10.10.1
  FQDN = servername.cisco.com
  maximum log file size = 10000
  n saved log files = 100
  log debug level = 5 minimum
  ps backoff = 150 maximum
  ps backoff = 300
  euro-packetcable = true
  

  When using Euro PacketCable, ensure that the value of the PacketCable property /pktcbl/prov/locale is set to EURO. The default is NA (for North America). You can specify the locale in the Configuration File utility. See Using Configuration File Utility for Template, for more information.

To configure CableHome support on the RDU, perform these configurations: