Line Class Codes are provided as an extension to allow you to perform routing that is specific to your deployment and cannot be controlled by other attributes; many deployments may not require them.
The Line Class Code (LCC) object is a child of the Line Class Codes object. It allows you to define a name for a Line Class Code, how it is used, and optionally one or more values that can be used for this code and their meanings.
The MetaSwitch Class 4/5 Softswitch does not assign a specific meaning to any particular Line Class Code or its value. You can define a maximum of 20 codes, each with a meaning specific to your deployment, and assign numeric values as required.
Parameter |
Access |
Description |
Index | Create | The EMS's identifier for this Line Class Code object. Specify a number in the range 1 - 20. |
Display name | Change | Optional user-friendly text description identifying the meaning of this Line Class Code. This is used to identify the Line Class Code wherever it appears in subscriber or routing configuration (for example in the field name shown for this Line Class Code in the Individual Line object, or in the attribute name shown for this Line Class Code when you select it as a routing attribute). If you specify a display name, it must not match the display name of any other Line Class Code. |
Access | Change | Specifies whether EMS users can modify the value of this Line Class Code on an active Individual Line, Business Group Line or PBX. Values:
|
Allow inheritance | Change | Specifies whether the value for this Line Class Code can be inherited as a default (using the Use default option) when configuring an Individual Line, Business Group Line, or PBX. Values:
|
Variant | Change | Specifies whether the value of this code in the configuration of an Individual Line, Business Group Line, PBX, or Persistent Profile can be any numeric value, or must be one of the values specified in the Values field below. Values:
|
Values | Change | One or more valid values for this Line Class Code. The values you specify here will be available for selection when you are configuring a value for this code in routing or subscriber configuration. If Variant is set to Validated, you must specify at least one value.
This field is a text field in which you can copy, cut, and paste text. To add or edit code values in this field, specify each code on its own line, terminated by a carriage return.
201200 Jersey City, NJ 201201 Elsewhere in NJ 201205 201999 All other states |
Export - number of objects exported | Read only | The total number of objects (including child objects) written to the export file so far in the current or most recent export operation. |
Export - status | Read only | The status of the current or most recent export operation, if any. Values:
|
Export - file | Change | The name of the text file (in the EMS User's home directory on the EMS Server) to which configuration information for this object will be exported. The maximum length of the filename is 32 characters. |
Export - log correlator | Read only | If the export status is Failed, this field contains a correlator for the log message that contains details of the failure. Click on the 'go to log' button next to this field to jump to this message in the EMS log viewer window. |
Export - correlator metaswitch | Read only | If the export status is Failed, this field contains the name of the EMS Server or MetaSwitch Network Element that generated the failure log. You may need this information to find the log in the EMS log viewer window. |