Q. What is V5?

V5 Interface specifies the physical, procedural and protocol requirements for interfaces between Access Network (AN) and Local Exchange (LE). The V5 specification is split into two types. V5.1 interface supports only one E1 link whereas V5.2 may use up to sixteen (16) E1 links on one interface. Association of bearer channel to user ports in V5.1 interface shall be provisioned and the equipment may have a pre-defined association of bearer channels to user ports. V5.2 adds to V5.1 ability by allocating the timeslots on E1-link to user ports on demand via a Bearer Channel Control (BCC) protocol.

Q. Why is V5 required? The evolution of V5 standards provides the standard interface between the Access Network and Local Exchange. User ports (PSTN/ISDN) interface terminates on the AN instead of directly terminating on the LE (Local Exchange). Access Network provides the narrow-band services to the users ports connected to it. Call control responsibility still resides at the Local Exchange. .

What are the advantages of V5 interface? Allow the AN to multiplex/de-multiplex user signaling and data streams from several user ports in a cost-effective manner. Allow network management of Access Network via Q3 interface Administration of resources in access network Maintenance of resources in access network Allow user selection of the Local Exchange Effective usage of bandwidth available

V5 R2MF Channel Associated Signaling No protection against link failure AN subscriber can not access all LE service AN acts more like another Switch / PABX Requires extra h/w in AN Arcaic techniques that differ substantially from country to country ISDN BRI/PRI cannot be supported Common Channel signaling which gives much higher throughput Protection mechanism built in for link protection LE services are transparent to AN and can be accessed by all the end subscriber AN truly acts as an access carrier Message based signaling in which no extra h/w is required Standardized interface that allows national adaptation ISDN BRI/PRI (even broadband ISDN) can be supported

Clock Sync For V5.2 interface the clock has to be derived from LE. The external clock can be derived only through VIMC0 and VIMC1, so it is necessary that at least one of these VIMC's be configured in the V5 interface. If both are available then one of the VIMC cards can be configured as primary clock deriving source and the other card can be assigned as the secondary clock deriving source. Clock sync can be programmed using command sys-setclock-priority Configured clock sync can be displayed by using the command dissys- clock-priority. Clock synchronization parameters can be changed temporarily (only in case of external clock sync.) by the operator by using the command sys-updateclockpriority.

Program Frequencies Supported by Base Stations The DECT RLL Base Station can support a maximum of 10 DECT frequencies. Out of these 10 DECT frequencies, the System Administrator can mask certain frequencies based on the requirement. Frequencies can be selected/deselected by executing the command chgdect-freqinfo The supported and unsupported frequencies are displayed by executing the command disdect-freq-info. Once this is done, rebooting the system is necessary, as this information needs to be transmitted to all Base Stations. Rebooting can be done through the command, sys-shut-restart with level 1 which will do a total reboot. Note: System should be in Simplex when doing the above configuration.

V5.2 Related Configuration corDECT in V5.2 Access Network (AN) mode can be connected to any Local Exchange (LE) which has V5.2 interface support at the LE. All the services and . features provided by the LE are applicable to corDECT subscribers. The call processing, billing, tone generation, announcement generation, DTMF detection is done by LE. The corDECT in V5.2 AN mode can support one V5.2 interface up to 8 E1 links.

Interface configuration The V5.2 interface has to be configured at both corDECT V5 AN and at LE for the interface to become operational. The parameters which are shown in * below have to be negotiated with the LE administration and must be in consensus with them. Only one interface can be present at any time in the system. The following are the necessary parameters, which need to be known while configuring the interface: *Interface Id: A unique number which identifies a V5 interface between the Access Network (AN) and the Local Exchange (LE).

*Variant Id: A provisioning variant is a unique label of a complete provisioning data set applied via the interface. It is a unique value, which identifies the provisioning variant of the interface. Its range is 0 - 127. *Persistency Count: The values of the Persistence check timer of the Layer 1 FSM (Finite State Machine) to evaluate the E1 link status. The persistence is to be configured for operational to non-operational link status and conversely from nonoperational to operational link status. The persistence range is between 100ms to 25s in steps of 100ms. *No. of Links: It is the number of E1 links on the V5.2 interface. The maximum number of E1 links supported by the V5.2 interface on corDECT AN is 8.

*Link Id: A number, which identifies a link, associated to V5.2 interface. Its range is 0 255. *Card Id: A number, which identifies a card, associated with each E1 link. Its range is 0 - 7 i.e. 0 for VMC 0, 1 for VMC 1 and so on. *Common Channel Id: A number that identifies the common logical signaling channel for Bearer Channel Connection (BCC), Control, Link Control and PSTN. The range is 0 to 216-1. *Primary Link Id: It is the link Id configured to carry the Common Signaling Channel. Its value can be any of the link ids. *Secondary Link id: It is the link Id configured to become the standby link for the Primary link.

*PSTN Channel Id: A number that identifies the PSTN logical signaling channel. *PSTN Link Id: It is the link Id for the link, which carries the PSTN signaling. Its value can be any of the link ids. *PSTN Slot Id: It is the Slot Id of the 64 kbps time slot for PSTN signaling on the E1 link. It can have values of 15, 16 or 31. *No. of Protection Group 2 Standby Channels: A logical signaling channel configured to carry PSTN signaling when the current PSTN signaling channel fails. It has a link Id and a slot Id that have to be provided.

*Protection Group 2 Standby Channels Link Id: It is the link Id. of the Protection Group 2 standby channel. *Protection Group 2 Standby Channels Slot Id: It is the time-slot Id of the Protection Group 2 standby channel. V5.2 interface can be configured/added by using the command "v52-configinterface- insert". The configured V5.2 interface and all its parameters can be displayed by executing the command v52-config-interface-read

 The configured V5.2 interface Id and its status (OOS/IS) can be displayed by executing the command v52-disp-ifcid. The V5.2 interface can be deleted by executing the command v52configinterface- delete. A V5.2 E1 link can be added to increase the voice channels by executing the command v52-config-interface-modify-links To reduce the no of voice channels, delete a link by using the command v52- config-interface-modify-links. Executing the command "v52-interface-modify-persist" can modify the persistency count, which is used to perturbations in E1 link. Both operational to non-operational and non-operational to operational persistence timers are modifiable.

LE specific configurable parameters Although V5.2 though country independent, due to compliance with different versions of standard, vendors may not support all V5.2 procedures. To satisfy the interconnectivity with different vendors, corDECT V5 provides certain procedures to be enabled/disabled and certain values to be configured when interconnecting with LE. These parameters are classified into Startup, System, and Tester. The startup category contains the procedures to be Enabled/Disabled during V5 interface startup like link Id check, PSTN restart procedure, Port alignment procedure etc. The system category contains global parameters, which will affect the way the system will react to certain situations. Examples of such parameters are whether calling party or called party priorities in case of call collision, whether CRC should be enabled/disabled while transmitting messages towards LE (some LE doesn't support CRC). The tester settings are not normally modified unless specific instructions. These parameters are to change certain environmental parameters that are needed for interacting with protocol testers. The LE specific configurable parameters are to be given suitable values before connecting to a Local Exchange. These configurable parameters are classified in to three separate groups.

Startup Parameters Parameters, which are essential for starting up an interface, are grouped under this section. These parameters are to be analyzed and setup for accordingly. Protection Data Link Establish Mode This option specifies whether to establish all the data links in a parallel or sequential mode. Default: Parallel mode. Startup Threshold Timer When the V5 interface is not up. The system tries continuously to startup the interface till this amount of time, which is specified as startup timer. Its value ranges from 0-300 sec. After this period elapses the startup procedure shall be repeated if the interface is not up. This procedure is continuously repeated. Default: 100 sec.

Link Id Check Procedure Link Id check procedure is a protocol defined procedure which checks whether the same logical link Id is used on both AN and LE, for a given physical link. This can be enabled or disabled basing on LE behavior at startup. Default: Enabled. PSTN Restart Procedure PSTN restart procedure is used to bring the entire user port states to Null State. This can be enabled or disabled. This can be enabled or disabled basing on LE behavior at startup. Default: Enabled Port Alignment Procedure Port Alignment procedure synchronizes the blocking states of all user ports on both AN and LE. This option indicates whether AN shall initiate this procedure or not. This can be enabled or disabled. This can be enabled or disabled basing on LE behavior at startup. Default: Enabled.

Global Startup Timer This timer specifies how long the AN should try starting up the interface in the configured Primary Link. After this the system shall trying starting up the interface in the Secondary Link. Default: 300 sec. Ignore Port Alignment This option shall be given only when the Port Alignment Procedure option is enabled. This option shall inform the system whether the AN initiated Port Alignment Procedure is mandatory or optional during interface startup. Default: Disabled.

Startup switchover mode This option shall be used to attempt interface startup in either negotiated or nonnegotiated mode. By negotiated means LE permits protection switch over during interface startup and by non-negotiated means the LE does not respond, so AN does an internal switchover and tries to bring up the interface in the secondary link. Default: Negotiated System Parameters System related parameters are grouped under this section. Like Startup parameters this too can be set according to a particular LE. Variant ID Re-Provisioning Protocol defined variant Id re-provisioning procedure allows the user to change the variant Id in AN and LE sides. This can be enabled or disabled. Default: Disabled.

Data Link Timer T200 This option configures the value of timer T200 in the data link. This ranges from 0 to 3 sec's in steps of 0.1s. Default: 1.5 sec. CRC Mode This option can be used to enable or disable CRC Mode. Default: Enabled. Link Id Reject Retry Count Its the no of times the system should retry if the Link Id is not matching between AN and LE. Default: 3 times. PSTN T2 Timer Value This option sets the PSTN T2 timer value Default: 5 sec. Call Priority When there is a Call collision there exists an option whether to give priority for Originating or Terminating Subscriber. This can be handled by setting the Call priority option. Default: Terminating.

Reject In Local Block Flag This option shall be set when a reject needs to be generated if the user port is already blocked. This option can be Enabled or Disabled. Default: Disabled Protection Re-establish Flag This option can be Enabled or Disabled. Default: Disable Tester Parameters Tester Parameters unlike other two groups are provided only for Tester (Protocol tester) Specific configuration changes. These parameters are to be modified only under specific instructions from designers of the system Override Q3 This parameter can either be Enabled or Disabled. Default: Disabled.

Tester Flag This parameter can either be Enabled or Disabled. Default: Disabled. Port Unblock Flag This parameter can either be Enabled or Disabled. Default: Disabled. The parameters under each classification can be changed using v52-chgconfigparams. The configured values of startup, system or tester parameters can be displayed using v52-disp-config-params. By default the parameters, which requires changes will be in startup category only. User port configuration The user port configuration for IP service is present in IP related configuration. This section presents the user port configuration for voice service via V5 interface. For a subscriber to be functional it has to be provisioned both at corDECT V5 AN and at LE. The subscriber addition can be considered as a 2-phase operation. Phase 1 is the addition of subscriber at the DECT end. Phase 2 is the association of the phase 1

completed subscriber to the V5 interface. Phase 1 and phase 2 can be completed sequentially, or only phase 2 can be postponed. The subscriber will become fully functional only when both the phases of provisioning are complete and provisioning at the LE is also complete. For completing phase 1 of subscription process a 10 digit unique IPEI (International Portable Equipment Identity) and an 8-digit authentication code (AC) has to be given. IPEI is nothing but unique equipment (Wallset) number and AC is an 8-digit code. The system shall then generate a string, which will give Wallset enough information about the DIU to which it should lock to. For completing the phase 2 provisioning at corDECT V5 AN, a unique (for that interface) L3 address needs to be given. The L3 address should be same for that subscriber at LE also, and is provided by the LE. After adding the subscriber, his DECT related security parameters needs to be looked in to. The administrator can enable/disable the different security features like Authentication, Encryption & Zap. If authentication is enabled then the wallset will be checked for uniqueness while initiating/receiving every call. If encryption is enabled then all the important information's transmitted on air will be encrypted during each and every call. Zap will take care of restricting calls from cloned wallsets. Encryption and zap can be enabled only when authentication is enabled. By default authentication is enabled. (refer operational manual)

 The command chgsub-add is used to add user subscribers If the L3 address/Interface Id is not known during provisioning of the subscriber, the phase 2 operations (association of subscriber to the V5 interface) can be postponed for a later point of time. L3 address for a phase 1 completed (DECT only subscribed) subscriber can be configured using the command chgsub-l3addr. A subscriber can be associated to the interface only once using this command for security reasons. To change the l3 address once again the subscriber will have to be deleted and re-subscribed once more. The wallset of a subscriber can be changed using the command "chgsub-moddectinfo". This will be useful whenever the wallset has to be changed if it is found faulty. This command will reset all the DECT related security features to default values. If the subscriber is having IP service too then te IP service would have to be removed and then wallset changed.

 The existing user port can be deleted by executing the command chgsubdel. The number of user ports configured in the system can be perceived using the command dissub-lst. The interface id and the L3 address will also be displayed if provisioned. The user port configuration can be displayed by executing the command dissub-con. The DECT related security features can be changed using the command "chgsub-security-feature". The DECT related security information about the subscriber could be displayed using the command disdect-mm-info. The list of free subscriber nos. that is available for voice service will be listed by the command "dissub-spare".

The list of subscribers who are still not associated to the v5 interface will be displayed by the command "dissub-v5-pndg".

IP related configuration IP services can be provided for subscribers who are already having voice subscription completed. The IP calls donot go through the V5 interface, the calls are instead routed via RIMC to RAS. Thus the IP calls can go through even if the interface were not configured. The maximum number of RIMCs configurable in a DIU is 6, with a maximum of 1000 subscribers configurable with IP service. The IP service for a subscriber is available by configuring the following Slot Route Code RIMC ports Exchange IP code Adding IP service to subscribers. Subscribers can have upto 70 KBPS IP service with configurable IP service options such as donot disturb, 35/70 KBPS. The IP configuration is priority based. After configuring RIMC slots, route codes are defined which would be the number dialed by the IP port of the wallset. Since every IP service for a subscriber is priority based, the RIMC ports are configured to a route code with a priority. On availability of a free RIMC port with suitable priority the subscriber calls are routed to that RIMC port. The exchange would have a IP code configured, to facilitate the RAS to track billing at RADIUS.

Slot configuration For facilitating IP subscribers at least one of the slots configured as VIMC has to be reconfigured as RIMC. VIMC 0 and VIMC 1 cannot be configured as RIMC because we can use only these 2 VIMC to slots derive clock from LE. Whenever a VIMC is converted to RIMC, we get 30 RIMC ports, which can be later used in the configuration. In this way a maximum of 6 cards can be converted in to RIMC which will give utmost 180 RIMC ports in a system. The command "sys-config-vimc-slot" will show the present configuration of all the 8 VIMC slots. The user can change one or more slots as RIMC and save the configuration.

Route codes Route codes have to be created in order to enable the subscriber to dial up the ISP. There can be a maximum of 8 route codes. Each route code can be up to 8 digits in length. The concept of different route codes comes into picture when the operator is having more than 1 way of routing his IP traffic to external world. The route code number is what the subscriber will dial to seize a port. Command "chgxchg-ip-routecode" can be used to Add/Del a routecode. Command "disxchg-ip-routecode" is used to display all the route codes configured in a system.

RIMC ports Every RIMC port has to be mapped/associated to a particular route code. There can be any number of RIMC ports associated with a route code. Each RIMC port has to be given a priority level between 0 to 7 where 0 is the highest level of priority. Priority 0 is a one to one mapping between the RIMC port and the subscriber. The priority 0 port shall always be mapped to a subscriber who also should be in 0 priority. Command "chgxchg-ports-in-route" can be used to Add/Delete a set of ports in a route. Command "disxchg-ports-in-route" can be used to display all the mapped ports in a route. Command "chgxchg-port-priority" can be used to change the priority of a set of ports in a route. Command "disxchg-port-priority" can be used to display the ports in a particular priority level All the ports configured in a route code and their priorities can be obtained using the command "sys-print-ip-route-info"

Exchange IP code Each corDECT IP system should be configured to have an IP code (equivalent to exchange code and not to be confused with IP route codes) The IP operator shall give a unique code (7-digit maximum) for all the corDECT IP systems he is having. When an IP call is made from the Wallset-IP, the system will send the 3-digit subscriber number (as known in the corDECT system) prefixed with the configured IP code of that system as the CLI information to the RAS. This feature can be used to identify the DIU from which the call originated and can be used for billing purposes. The IP code of a system can be configured by using the command "chgxchgipcode". If the IP code is already configured, it can be reconfigured using the same command. The configured IP code can be displayed by using the command "disxchg-iproutecode".

Adding IP services IP service must be given a priority level while configuring the service for a subscriber. Thus for a subscriber with an IP priority 'N', any RIMC port belonging to that route having a priority level greater than or equal to N (where N is between 1 & 7) will be seized. Subscriber having IP service priority level 0 must have a dedicated RIMC port mapped to the subscriber. The mapping for 0-priority subscriber should be done explicitly after adding that subscriber. Otherwise that subscriber shall never be able to seize a port. The priority of the IP service shall initially be given while configuring the IP service. The same "chgsub-add" command can be used to add the IP service for a subscriber. "chgsub-ip-params" to set the IP service configuration. "dissub-ip-params" to view the IP service configuration. Command "chgsub-priority-lvl" can be used to change the priority level of a particular subscriber. Command "dissub-con" can be used to view the IP priority level and mapped port (for 0-priority subscriber) for the subscriber.