Schedule 1 Small EPABX Systems Configuaration

ANNEXURE-A DETAILED SPECIFICATION FOR EPABX SYSTEMS 1. GENERAL a) The EPABX system should be Digital Microprocessor based stored program control with latest Software Version. It should have facility to connect Computer Terminal,Telephone, and Paging System through suitable Interface common to all such devices. Tenderers shall indicate full details of the system offered including CPU speed. b) The system shall be capable of working in a suitably ventilated non-air-conditioned environment. System design shall be immune to noise from various sources like power supplies, lighting system etc., c) The System shall ensure a very high degree of availability and maintainability through use of highly reliable components and appropriate structural & functional units. Provision of redundant control units in a suitable configuration shall be provided as an option. d) All components should be rated for continuous operation of the system. It should be designed in such a way that any damage in any circuit/subassembly/assembly should be self-containing and should not be propagate to other parts of the system. e) The EPABX shall be capable of pulse to tone conversion and vice versa to enable correct operation (originating & receiving calls) with the DTMF and dial pulse signaling having a speed range of 8-12 PPS and break ratio of 50 to 80%. Dialing out shall meet following limits. Dial Speed : 10+/0.5 PPS Make/break ratio : 1:2, normal with break period between 65 to 68%. IDP : >550 ms. f) Call buffer memory shall be at least 1350 for Small Systems and 5000 for LargeSystems. The tenderer shall indicate call buffer memory capacity offered. g) The equipment shall be capable of working under the howling line & junction limits as under: i. Extension loop resistance of 1200 ohms for large systems and 600 ohm for small systems. ii. Junction Loop up to 1800 ohms. iii. Insulation lower limit 20 k ohms. h) Flexibility of opening & closing of limits & modification in class of service will be provided. i) There must be protection of EPABX System from high voltage/current transient occurring on junction lines to the Exchange. j) Power fail cut through shall be provided as specified under clause'3y'of SYSTEM FEATURE.

k) All cards of the same type & design shall be interchangeable without necessitating special adjustments.System would be offered by the firms with Hot standby facility if they have provision for the same. l) Cabinet design shall provide for adequate ventilation to dissipate heat due to energy loss. m) The points for connecting supplies, the power supply to the different plug-in cards shall be standardized & mechanically interchangeable to prevent damage due to accidental interchange of cards. n) Sub-assemblies & printed cards in the equipment shall be suitably marked Identification of a type of card in its connector shall be possible without necessitating its removal. Any plug-in component shall be marked with sufficient information for its complete identification. o) All instructions labels or any other marking on the equipment shall be perfectly legible. p) Connecting cables between jacks shall be marked in their extremities with identical designation as on the fixed connecting flanges. q) Fuses used shall have a suitable marking for the different rating to enable easy identification and replacement. r) The items quoted shall have TEC approval for interconnection.TEC Approval will not be necessary for IP Gateways and DECT. Tenders shall furnish a copy of TEC approval certificate along with tender for each item quoted and it should be valid on the date of tender opening. It will be the responsibility of the supplier to keep the TEC approval valid during the currency of the Rate Contract. s) No. of extensions specified for each configurations are exclusive of I.P. Gateways and DECT extensions. t) DECT Phones shall have a minimum talk time of 20 hours and a range of min.50 mtrs. u) Each DECT Base Station shall be capable of handling minimum of 48 DECT Phones calls simultaneously. 2. POWER SUPPLY a) The EPABX shall be suitable for operation on 230V +/- 10%, 50 +/-2 Hz AC or on 48 V DC power supply as per the customer requirement. b) EPABXs operating on 230V+or_10% AC shall have in built battery charging arrangement for providing battery back up for 2 h minimum. Batteries for this purpose shall be ordered separately. c) Power back up for 230V systems can also be provided by external UPS which will also be ordered separately. There is a separate DGS&D Rate Contract for UPSs.

d) Power back up for 48V systems can be provided by Float Cum Boost Charger (FCBC) which has been included as a separate schedule and has to be ordered separately. The ratings of FCBC and batteries can be decided by the DDOs depending upon their power back up needs. e) The derived power supply shall be suitably protected on the input side against over current and accidental reversal of polarity and on the output side against over current and over voltage. Automatic recovery shall be possible. 3. SYSTEM FEATURES a) The EPABX System should have Digital PCM/TDM (non-blocking) technology. They shall indicate the switching IC/CHIP used. They shall furnish calculation showing the non blocking technology /switching. b) Tone and Ringing: The System shall provide the standard tones and ringing current as in the Public Telephone Network as follows: (i) Ringing 75 V AC , 25 Hz. (ii) Ring back tone 400 Hz. 0.4 sec ON, 0.4 sec OFF. (iii) Dial tone 400 Hz modulated by 25 Hz. (iv) Busy tone 400 Hz, 0.75 sec ON, 0.75 sec OFF. (v) Operating Voltage 48 V +/- 4 V DC. c) The equipment and circuits for tones and ringing shall form part of main PABX equipment. d) The equipment should have Automatic Route Selection facility to determine least cost route automatically based on class of service. e) Extension-to-Extension Dialing: It shall be possible to establish internal calls automatically by dialing any number without assistance of the attendant. f) Direct Outward Dialing: It shall be possible to establish external calls automatically by dialing any number without the assistance of the attendant (subject to class of service). g) Provision of DID & DISA: It shall have facility for direct inward dialing and direct inward station access. h) Direct Outwards Station Access (DOSA): Any Extension can access the trunk lines of the System through personal pass code to make outward calls from outside. All DOSA calls remain in account of that particular Extension. i) Direct Station Selection (DSS): Just pressing a single key the operator or extension can directly call an extension or access the trunk line without hassles of pressing 3 digits. j) Multi Level Voice DISA: When ordered as an extra feature/card, this will enable the systems to provide auto attendant service to outside callers to directly access the desired extension by surpassing the operator. The caller should be step wise guided by multi-level voice messages.

k) Access To Exchange Network: It shall be possible for an extension to get access to public network with or without the attendant in such cases, facility shall exist for the attendant to either dial the required No. or to merely extend the junction to the extension and permit the subscriber to dial the number. l) Privacy Of Call: Full privacy of conversation shall be available on all calls whether established directly or by the attendant. A warning tone of a specified frequency shall be applied when trunk-offering facility is exercised by the attendant on an extension user. m) Class Of Service: It shall be possible to allow an extension control over the telephone usage by providing him suitable class of service. n) The coding technique to be used is ALAW/CODEC per channel. o) System should have provision for Automatic Last Number Redial up to 20 times on Junction Line. p) During night, when the board is shut, external lines should be linked to any predefined extensions. q) Provision for connecting recorded voice / answering to make available extensions to an incoming call without the help of operator. r) Flexible Numbering Scheme: System should have provision for flexible numbering plan up to four digits for extensions. s) Trunk Support: The System should support a following connectivity to satisfy all type of trunks & tie circuits. Analog for all For ISDN compatibility In case of Small EPABX Systems : ISDN BRI In case of Large EPABX Systems : ISDN BRI & ISDN PRI For Networking Compatibility In case of Small EPABX Systems : Digital ISDN and VOIP In case of Large EPABX Systems : Digital ISDN,E1,E&M and VOIP Generally system supporting ISDN PRI shall also compatible to E1 connectivity. t) Universal Port Configuration: All ports of the System should be identical to facilitate flexible configuration of the System as per user needs. u) Discriminate Ringing: The System should support discriminate ringing to indicate internal & external calls. v) Multiple Consoles: The System should support multiple numbers of consoles for large EPBAX Systems.

w) Mixed Station Dialing: To support all the features irrespective of type of telephone instruments i.e., DTMF or DECADIC. x) Versatile ASMDR The System should support ASMDR, which is a call accounting application that can record & print up to at least 3500 calls without dedicated printer. y) Power Failure Transfer: In the case of power failure all P&T / CO lines become available on the pre-set Extensions. Provision for Availability of Junction Lines shall be as under: System of 4 & 8 Junctions: Availability of 2 Junctions System of 24 & 32 Junctions: Availability of 4 Junctions System of 64 Junctions: Availability of 8 Junctions z) Programmable Class Of Service The System should support programmable class of service for P&T (STD/ISD/LOCAL) dialing as per need. i) Direct Call Billing In Rupees: The System should support direct call billing (near value) through parallel/serial port printer without computer. ii) Call Billing Printout Options: The System should support versatile multiple combinations of direct printout options with total amount viz., Extension wise, Trunkwise. Today?s call print out, Group wise printout, Particular date, Particular Month, Particular Time, Particular Phone etc. iii) Calling Line Identification (CLIP) : This is an optional feature and when ordered it enables the incoming calling No. is displayed on Key/Analog Phone even if the call is transferred by the operator, it is compatible to DTMF (Optional). iv) Remote Maintenance: The System programming can even be done from remote locations. 4. EXTENSION FEATURES a) Automatic Call Back: Facility shall exist for an extension user on encountering a busy signal on a called extension, to invoke the automatic call back feature by dialing a code before hanging up. When both the calling and called parties are free, the call should be automatically put through on no-answer the call may be disconnected after a specified period. (This facility should be available throughout the network if more than one EPABX are interconnected in a Private Network). b) Call Forwarding: An extension with this class of service shall be able to transfer all incoming calls, temporarily to another pre-selected extension. Such requests shall be registered by dialing a code followed by the extension No. Facility shall also exist for cancellation of a request registered earlier. This facility should be available throughout the network if more than one EPABXs are inter-connected in a Private Network. c) Consultation Hold: An extension engaged on an external call (incoming or outgoing) shall be able to hold the call while making internal call for private consultation. The external subscriber shall not overhear such consultation. There must be facility of music during hold condition. d) Brokers Call: An extension engaged on an external call (incoming or outgoing) shall be able to hold the call while making another call than alternate between the two. The other party shall not over hear such consultation. There must be facility of music during hold condition. This

facility should be available throughout the network if more than one EPABXs are interconnected in a Private Network. e) Automatic Call Transfer: It shall be possible for an extension user to transfer incoming calls to another extension with or without help of the attendant. This facility should be available throughout the network if more than one EPABXs are interconnected in a private network. f) Executive/Secretary: A combination of call forwarding, consultation & hold to provide for executive to selectively/answer calls. This facility should be available throughout the network if more than one EPABXs are interconnected in a private network. g) Executive Over-Ride: There must be facility offering priority to 5 min extensions to over-ride on going conversations. This facility should be available throughout the network if more than one EPABXs are interconnected in a private network. h) Access To Paging: Extensions and attendant shall have dial access to a loudspeaker or any other type of Paging System where such a system exists. i) Conference Call: It shall be possible for an extension user (up to a maximum number of 6 to talk to each other at the same time on a conference circuit. One of the extension user or by the attendant may set up the conference call. This facility should be available throughout the network if more than one EPABXs are interconnected in a private network. j) Call Pick-Up: It shall be possible for an extension user to pick-up incoming calls ringing on another extension without the help of the attendant. This facility should be available throughout the network if more than one EPABXs are interconnected in a private network. k) Call Re-Routing: It shall be possible for a call to be re-routed, without help of the attendant, to other pre-defined extensions when certain conditions apply. This facility should be available throughout the network if more than one EPABXs are interconnected in a private network. l) Auto Call Disconnection: For large EPABXs, the system should facilitate to fix the time of call beyond which it will be automatically disconnected. m) Dynamic STD Lock: The System should support that individual extension can lock outward dialing (STD/ISD/LOCAL) by a personal secret pass code to prevent misuse by others. n) Paging On Key Phone: The caller can activate speaker phone of the called extension to communicate in urgency in own voice when Extension is idle. o) Call Name & Extension number on Display (Internal CLI): Name as well as Extension No. of the caller is displayed on the Key Phone, facilitating to respond accordingly. p) Background Music: The Key Phone user can enjoy the light background music channeled from System When Voice DISA Card incorporated.

q) Auto-Answer / Auto-Off: Key Phone can be programmed for auto-answer after pre-set number of incoming rings. The Key Phone is automatically disconnected when caller disconnects. 5. ATTENDANT'S CONSOLE FEATURES Stand-alone or P.C. based Attendant Console with the following features: a) The operator console should have soft/feather touch keys with easy to view display and busy lamp field for extensions. It will have easy handling facility for all internal & external calls. b) Answering an Incoming Call: Facility should exist for answering an incoming call, whether from an internal extensions or external junction. It should be possible to identify the type of call that is internal, external line etc., from the call indicator. c) Call Queuing: All incoming calls should be presented to the console in order of the arrival. Facility should exist for giving preference to junction calls and from tie lines over calls from internal extensions. d) Serial Call: Facility should exist in Large systems to extend an incoming call as serial call which should come back to attendant on completion of call permitting the attendant to route the call to another extension and so on. e) Call Waiting Display: An indication should be given when there is an unanswered call waiting in the queue. The lamp shall flash if number of calls waiting in the queue are two or more or if a call has been waiting fore more than a predetermine time. f) Call Selection: Facility should exist to the attendant to select which incoming call to be answered first. g) Call Hold Facility: It shall be possible for the attendant to place an incoming junction call on hold pending further processing. h) Setting Up External Calls: Facility shall exist for enabling the attendant to set up the external calls for the extensions, which are allowed to access the public network. The attendant may either dial the number himself or merely extend the junction to the authorized extension user. i) Trunk Offering: The attendant shall be able to offer an incoming call to busy extension. A tone shall however, alert the talking parties when the attendant bargesin on a connection. j) Provision for Remote Supervisor Control. k) Position Busy: When more than one console is in use. It shall be possible for a console to prevent further incoming calls from being assigned to it by busying itself. When a console is so busied all the waiting calls queued for the particular console shall be transferred to other console/extensions. Incoming calls in cases where two consoles exist shall be equally distributed. Facility shall exist during absence of the attendants for incoming external calls to be forwarded to one common or several individual extensions.

l) Night Service: It should be possible for all incoming calls to be transferred to certain pre-fixed extensions, in case this option has been exercised during the night. m) Head Phone Connectivity: The operators can plug-in headphone to handle the call traffic efficiently while keeping her/his hands free for other jobs. 6. SERVICE OBJECTIVES Following service objectives shall be met : a) Under overload conditions, the lost call figures applicable shall be one in 200 for extensions to extensions call and one call in 100 for junction calls, overload being defined as 10% increase in occupancy of speech network and simultaneous 25% increase in the number of calls. b) The selection time under full load is defined as the time interval between the instant at which the required information for selection of the outlet has been received at the inlet and the instant at which outlet is ceased shall not exceed in 99% of the cases under traffic overload 1.5 seconds. c) The assumption to be made whilst dimensioning the links, junctions and attendants console shall be following: i. Total originating & terminating traffic per extension (including junction traffic) 0.2 erlang during peak busy hour. ii. Total junction traffic per extension 0.1 erlang during peak busy hour. iii. Average holding time of calls 0.90 seconds. iv) The switching network shall provide access to the links & junction on fully nonblocking basis. v) The equipment design shall be such that any special case and precaution on the part of maintenance personnel are kept to an absolute min. And no preventive maintenance is required. vi) The System shall have inherent capability to monitor its own performance and to detect, analyze and locate faults. vii)Fault repair at site should normally consist of only replacing the faulty card or plug-in modules. vii)The System should have remote maintenance facility. 7. TESTING a) Acceptance tests: Facilities to be available at the place of inspection fori. Verification of all features / functional performance of the Machine. ii. High Voltage (Flash Test at 1000 V) iii. Measurement of loop resistance. b) Documentation Requirements for Stores Offered for Inspection against R/C for Imported EPABX: Successful tenderers shall be required to meet / furnish the following for inspection of bulk supplies for each & every lot. i. Catalogue/specification sheet of the manufacturer ii. TTC for the product duly indicating the serial number of the tested machine and actual test results values for all major specification parameters as well as for environment tests, where applicable. iii. Manufacturers test certificate, back up guarantee/warranty and after sales services support for the machine serial numbers offered from the authorized official of the foreign manufacturer in the following format:

I/We who are the manufacturers of ------------------------------------(name and description of the goods offered) having factory(ies) as provided for the R/C at ------ ----------------------- (Name & Complete address of the factory(ies) hereby certify that the following machine/model Nos. bearing Sl. Nos. mentioned against each were exported by us to M/s - ---------------------(Name & address of the Indian supplier) Item Model No. Machine Sl nos Invoice No The aforementioned machines were tested in our premises and found to be satisfactory as per the contract specifications. We hereby extend back up guarantee/warranty and after sales services support in case the Indian supplier do not perform their obligations. We also undertake to supply spare parts for 7 years from the date of supply of machine to consignee. The above certificate should be on the letter head of the Manufacturer and should be signed by the legally competent officer of the company or by authorized person and having power of attorney to legally bind the manufacturer along with copy of such authorization. c) Environmental Testing: The EPABX system and all the other equipment offered shall meet the requirement of following environmental tests:(i) Cold Test: At 0 Degree C for 2 hrs. As per IS 9000/Pt 2/Sec 4/1977(reaffirmed 2007). (ii) Dry Test: At 45 Degree C for 16 hrs. As per IS 9000/Pt 3/Sec 5/1977(reaffirmed 2007). (iii) Damp Heat(Steady State) Test: At 40 Degree C & 95% RH for 2 cycles as per IS9000/Pt 5/Sec 1/1977(reaffirmed 2007). After recovery of 1&1/2 hour environmental tests as mentioned above, the functional performance/features of EPABX shall be checked and results should be satisfactory. Environmental test shall be carried out at a Govt.lab.TTC in this regard shall be required at the time of both registration and inspection. 8. MAINTENANCE MANUALS Two sets of each of the following operation and maintenance manuals shall be supplied along with the equipment. i. General write-up of overall System specification & description of all the equipments explaining features, facilities, functions & principals. ii. Operating Manual. iii. Detailed description of entire software, if applicable. iv. Maintenance of instruction manual including maintenance test schedule fault deduction and trouble shooting procedures. v. The derived power supply shall be suitably protected on the input side against over current and accidental reversal of polarity and on the output side against over current and over voltage. Automatic recovery shall be possible NOTE:Under Schedule 3, Additional items for EPABX System - For Voice Mail System 4- port for use with PC, PC will not be the part of supply and to be purchased separately NOTES:

i) The EPABX system should be Digital Microprocessor based stored programme control with latest Software Version. It should have facility to connect Computer Terminal,Telephone,& Paging System through suitable Interface common to all such devices. Tenderers shall indicate full details of the system offered including CPU speed. Tenderers shall indicate model/make of the system as well as important sub assemblies. ii) Tenderers shall furnish compliance statement for technical requirementclause by clause clearly indicating deviations to tender specifications.They shall furnish their comments / justifications for the same. iii) Tenderers shall furnish the details of after sale service and past performance of the system quoted by them as per format enclosed at Form 1 and 2. Schedule 2 Large EPABX Systems Configuration
Specification : Large EPABX systems Configuration shall comply as per the detailed specification under Annexure-A and shall be supplied in one of the configurations as per schdule.

Schedule 3 Float cum Boost Charger for EPABX System

Specification : Float cum boost charger for EPABX system are used as an accessory.It shall be supplied as per the ratings ordered as per schedule.The detailed specification like voltage out put -in float mode,normal mode and boost mode,line and load regulation,ripple at full load,maximum over shoot in percentage,maximum undershoot in percetage, efficiency,availability of short circuit protection shall be spelt out clearly by the tenderer.

Schedule 4 Small EPABX System with In built 4 Port voice mail.

Specification : Small EPABX systems with in built 4 port Voice mail (details like recording duration shall be indicated by tenderer)shall comply as per the detailed specification under Annexure-A and shall be supplied in one of the configurations as per schedule.

Schedule 5 Main Distribution Frame(MDF)

Specification :Main distribution frame is used as accessory to EPABX and shall be suitable for the EPABX quoted and shall be with IPM .Tenderers to indicate the model/item No. of EPABX for which MDF are suitable.

Schedule 6 Small EPBAX system configruation add-on items

Specification :These items are accessories to EPABX system and shall be suitable for the EPABX quoted as per Annexure-A.

Schedule 7 Large EPBAX system Configruation add-on items

Specification :These items are accessories to EPABX system and shall be suitable for the EPABX quoted as per Annexure-A.

Schedule 8 EPABX- Unified(Server based)

1(a) Basic Architecture 1 The IP telephony system should be a converged communication System with ability to run TDM and IP on the same platform using same software load based on server and Gateway architecture(SIP Server based EPABX system ready for unified communication).The system should be capable of supporting Analogue, Digital and IP Telephones. The single IP EPABX system should have a provision of expandability minimum up to 18000 stations (any mix/percentage of Analog/Digital/IP ) and minimum up to 2000 trunks (in totality 20,000 ports) without changing or cascading multiple servers to achieve the future capacity. CLI facility for all users should be provisioned from day 1.The OEM shall be listed in magic quadrant of Gartner. 2 The sytem should be based on server gateway architecture with external appliance server. No card based processor systems should be quoted. 3 The Communication Server/Call Server would be deployed in a duplicated configuration over the distributed IP infrastructure (LAN/WAN). The call server should have in-built duplicated power supply drawing power from two different sources. Both the active and standby processors should not be in the same unit/cabinet sharing the same active backplane so as to prevent total system failure on failure of the motherboard/backplane. 4 In hot-standby operation mode, during changeover from active server to standby server, any active/ ongoing calls across the entire network/locations should not be interrupted or affected. There should be no restriction on number of endpoints being backed up in case of one server failure. 5 The system should be modular, scalable and distributable in nature. 6 The system to have distributed architecture and the centralized control for all the IP PBX entities in the network. It should be possible to have centralized applications like voice mail, UC for the netwrok users 7 The server and gateway should support IP V6 from day 1 so as to be future proof. 8 System should provide remote survivability. In case of LAN/WAN link failure to the remote location gateways, the remote locations endpoints should be survivable with all basic telephony features. 9 The system shall be configured for SIP and IP TRUNK interfaces without any external interfaces or adapters. 10 It should be possible for the IP phone to be connected on the same line which is connected to the computer i.e. Single wire to desk. 11 All the Servers should be a commercially-off-the-shelf server (Make like Dell/ IBM/ HP/ SUN) & with min following specification of each server. Vendor

can quote equivalent or higher performance server. Microprocessor: Intel E5620 quad core processor or better Memory: 12 GB DRAM Hard disk drive: Minimum 146 GB SAS hard drives configured in a RAID 5 array 2 nos USB port in front & 2 nos USB port in back Quad Gigabit (10/100/1000 Base-T) Ethernet Ports Hot-swap fans: Six Runs on Open Source secure Linux Operating System 12 The VOIP should be implemented through Plug and Play interface boards in any of the Universal slots of the system. The replacement of cards in both Call Control and Media gateways should be online (i.e. hot pluggable) with out the need to power off the system. 13 The system software version offered should be the latest release as on the date of supply of EPABX as available globally. 14 The offered solution must provide a standard based mechanism for QoS implementation.8 15 At Layer 2, Ethernet 802.1p/Q standards define the bit markings of Ethernet packet header which are used to prioritize packets at Layer 2. 16 At Layer 3, IP standard DiffServ defines bit markings in the Type-ofService (TOS) fields in the IP header, which will identify a packet to be associated with a specific service. On IP equipment end-to-end, these services can be administered. 17 At Layer 4, it should support UDP port-prioritization. 1(b) SIP Routing and Registration Engine ( this functionality should be inbuilt in the call server) 1 The system should be based on the standards-based principles of IP Multimedia Subsystem (IMS) to allow custom core services to be delivered to each user in the enterprise. 2 The offered solution should be able to have IMS-like functionality based on the 3GPP and SIP-ISC so that there is flexibility in providing services to users wherever they are and in any device thereby enabling richer multivendor integration and providing agility for implementing unified communications in the network 3 Proposed system should have 100% of the SIP entities and SIP endpoints have their signaling encrypted by TLS 4 System should allow direct registration / profile creation of SIP endpoints onto it and perform all functions of Proxy/ Registrar / Redirect etc 5 The system architecture should allow for incremental application additions to the enterprise without modification to existing feature server software 6 Proposed system should handle All administration and management of the enterprisewide private global dial plan by this communications appliance, and managed as a single enterprise with the Single Administration point 2 Subscriber / Trunk Cards (a) Analog Subscriber Cards (i) Should provide 24 or More Ports (ii) Each Port to support CLIP Feature both DTMF and FSK. The presentation of CLIP should be card dependent and should not be dependent on Central Resources. (iii) Should be work on copper cable without degradation of service up to minimum distance of 2 Kms. (b) Digital Subscriber Cards (i) Should provide 24 or More Ports.

(ii) Calling Number and Name should be displayed on the phones that are connected on to this card. (iii) Should work on Copper up to a distance of 2 Kms with out any degradation to the performance. (c) CO Trunk Cards (i) The CO trunk card should provide at least 8 ports per card. (d) E1/PRI Trunks (i) The offered system shall support software configurable E1/PRI Cards. In other words it should be possible to configure the same card as E1 or PRI or vice versa. Otherwise vendor should provide 2 cards each for achieving this functionality. (ii) Should Support DP, DTMF, MFCR2, QISG, DPNSS signaling streams or equivalent 3 Security 1 The system must support log services for both Internal and External commands and configuration history for at least a 21 Days time. 2 The protection of signaling connections over IP by means of authentication, Integrity and encryption should be carried out using TLS. 3 The password and Access Control must Include the following: 4 (aa) Passwords to prevent the possibility of an aggressor to easily read or deduce system or account access password. (ab) Password aging with Configurable time periods. (ac) Usage of AES (Advanced Encryption System)-128 Bit algorithm for password encryption. 5 System should support MLPP feature. 6 System should be able to encrypt the Control signaling also associated with the IP Calls with a minimum of AES 128 bit. 7 All management traffic between the remote console/session and Call control server should be encrypted (SSH for Direct Command Line Sessions, Interface, https (SSL) for Web Sessions, SFTP for File Transfer Etc.). 8 The administrator logging on to the call control server needs to authenticate by suitable mechanism such as User Login Information and Passwords/ Radius Server. 4 Signaling Standards. (a) The offered IP Exchange be ready to support following signaling standards 1 E1 with QSIG (Q2931P protocol Compliance) 2 Trunk digital-MFR2 (Indian)/SS7/V5.2 3 Local Analog-DTMF 4 CO lines for STD local junctions shall work on R2MFC / Decadic signaling. 5 E1 CCS PRI 6 E1 CAS (R2MFC, Modified Indian R2MFC 7 SIP 8 H.323 Signaling 9 Voice encoding standards:10 (a) G.723, G.711 (b) G.729 A. 11 The system must support Network Time Protocol as per RFC 1305 to synchronies to the system date and time of network devices. 12 T.38 for FAX Connections over IP Networks. 13 To support voice activity Detection as per IEEE standards of G.729 AB. 14 DTMF and Mixed Dialling modes for telephones. The system should provide outgoing DTMF transmission even from Digital Telephones. 15 The offered system being IP at Core should support Echo cancellation 5 Main site and remote site Gateway FEATURES. 1 The remote unit should have the capability of having more than 100 DSP resources.

2 The link between the remote units & main unit should be truly non-blocking and provide complete feature transparency. The remote unit functioning on IP should be self survivable. 3 The connectivity between Server & Gateway should be be duplicated through duplicated Data Switch so that if any one link fails; redundant link should take controls immediately without disruption of services (Hot-Standby). 4 The system should ready to provide closed numbering scheme wherein no access code is required to be dialled for calling extension numbers of another complex. 5 The power supply module for both media gateways and call control server module should have the capability to take on AC power supply. 6 The Gateway should support routing & switching functionalities like OSPF, RIP, PPP, PPPoE, Frame Relay, VRRP. 7 The gateway should support IPV6 from day one to be future proof. 8 The Media Gateways should have the capability to integrate with all types of legacy interfaces such as Analog CO Trunk, Analog DID Trunk, E1/PRI Interfaces, IP Subscriber interface, IP Trunk Interface 9 Once the IP WAN link comes in service the connectivity should switch to IP and calls should go through IP Only. 10 The Gateway should support embedded web manager and RADIUS authentication 11 The Gateway should support SCP, TFTP and FTP clients 12 The Gateway should support SNMPv1, v3, Telnet and SSHv2 13 The Gateway should also support local announcements and music on hold support. All tone detection and call classification resources should be local to the gateway. 14 The Gateway should support survivability for continuous voice services like local survivability when main processor fails, Emergency Transfer Relay, Modem dial backup, Dynamic Call Admission Control, Inter-Gateway Alternate Routing 15 In case of WAN link failure, when the connectivity with main server is lost, the remote locations endpoints should be survived with basic telephony features. 6 Management (i) The system must include a dedicated server platform that will be based on the latest technologies and should be able to manage the entire network as a single system. (ii) The management platform should offer graphical clients and web based interface (iii) The management platform must offer web access allowing the authorized users to manage the system must multiple PCS using Internet Browser. (iv) The management platform must perform the following tasks:(ab) Configuration and Programming. The management system must be able to configure and programming of services, users, class of services, various categories and all system parameters and features. The process should be easy with out the administrator haing to remember in command line for carrying out administration. (ac) Faults and Alarm Management. The offered Management platform must have provision for storing all alarm and event messages in a separate file date wise and should have the capacity to analyse the same. It should also be possible to route these faullts and alarm messages to any of the operator console. (ad) Processor Occupancy Report. The offered management Platform must indicate stats about the processor occupancy report in terms of total number of calls that entered the

exchange and how many were attended and how many were dropped etc. (ae) Interface to Directory Services. The offered system must have the provision to display directory services on all Digital Telephones and IP Telephones, WLAN Handsets. The LDAP Protocol should be supported so that the users can click the name and dial the desired number. (af) Call metering and accounting. The log of local calls (local to local), trunk calls and transit calls through this exchange should be possible on the management platform. Provision should be available to customize the log information that is being generated from the system. A simple view of the log should clearly indicate whether that particular log is for incoming or outgoing or transit call. Call metering and accounting should be from the IP PBX to the Call metering and accounting terminal should be purely on IP only and not on RS232 C ports. (ag) Performance of Operators. The offered management platform should indicate the stats regarding the Number of calls assigned to the operator and number of calls cleared and number of calls dropped etc. These statistics should be possible to be generated from Docket less Exchange as well. (ah) Reports. The management platform must be able to generate reports in terms of accounting, error reports and alarm reports. It should be possible to export information such as Call metering on to an excel format. (ak) The management platforms must provide different levels for accessing the system based on the role being played by the user who is accessing the system. The administrator should have the highest authority. (al) The management platform must have a provision of giving history of all activities carried out through the same for at least 10 days including the time and date of the event that has occurred. (am) The management platform should be able to interact with the Call control server for all backup related services. It should be possible to keep backup or archive of the system on any PC or external Hard Drive for system software and User Database. (an) The management system should be SNMP compliant and ready for interfacing to Umbrella Management system such as HP Open view. (v) History Log. The history log should enable users to view the results of running and completed tasks. (vi) There should be `help facility for the administrator for inputting commands CLI

DRAFT COPY

Page 21 of 35 Interface (vii) It should relieve the user from remembering lengthy procedure and formats for data changes and shall use simple English commands only for the same. (viii) System management should automatically check through series of tests the normal operation of the system. 7 System Features. (i) The system should support at least 13 digit numbering scheme. (ii) The system should support closed numbering scheme wherein no access code is required to be dialed for calling extension numbers of another complex networked via IP (H.323 &SIP) and QSIG. (iii) Scheduling. The scheduling capability should enable users to specify a task to run at a specific date and time. A Task could be a collection of one or more operations that users can specify to run at a predetermined time. (iv) CLI on Digital, IP as well as Analog Phones with display: The CLI coming from local and trunks should be displayed on :(a) Digital Telephones. (b) IP Telephones. (v) CLI coming in from ISDN PRI trunks should be displayed on Analog Telephones, Digital Telephones and IP Telephones. (vi) External Holding Tone. The offered system should be ready to accept music on hold from an external PC or CD player. (vii) Distinctive Ringing. The offered system to provide distinctive ringing for internal calls, external calls, auto call back calls and certain emergency services. (viii) The proposed system should support automatic route selection (ARS) and least Cost routing (LCR) features to route the calls based on priorities related to user profile, tariff, and network availability, along the most cost-effective path. This service will be transparent for users and irrespective of the physical carrier connection. (ix) Auto-attendant facility on all trunks simultaneously with flexibility of having different sets of announcements to separate incoming trunk groups. (x) When all attended consoles are engaged, the external caller shall be informed of this situation by voice message. The call should be routed to the least loaded operator. (xi) Should be able to provide alternate answering point for calls that might otherwise go unanswered. (xii) Executive Override. (xiii) Line Lock-out. This feature shall allow for automatic release of calling station line from the common equipment after a predetermined time in case of failure to dial or failure to go on hook. (xiv) ISDN PRI with QSIG. The EPABX should provide ISDN-PRI trunk with open-ended

QSIG (ETSI) to support private networking. OEM should be a member of IPNS/ECMA forum. QSIG should not put any restriction on the number of E1s/PRIs. The QSIG should provide all basic and Supplementary features. It is preferable to have same card which is software configurable for E1 / PRI. In case the vendor is unable to provide this feature then he should give a commitment to exchange the E1 cards with PRI cards and vice versa without any additional charges, whatsoever. It is preferable to have 2 port E1/ PRI cards. In case the vendor has both, 1 port and 2 ports E1/PRI cards then only 2 port cards will be offered. Here vendors to specify the following: (a) Hardware and software required to implement QSIG. (b) List of features supported by the EPABX in heterogeneous environment. (xv) DTMF & Busy Tone Resources: The offered system should be equipped with at least 25 numbers of DTMF receivers. Busy tone detectors for each and every trunk circuit should be available. (xvi) The offered system should support Unified Communications. (xvii) The offered system should provide Unified Messaging.

DRAFT COPY
Page 22 of 35 (xviii) The offered system should support IVRS. (xix) The offered system should support paging. (xx) The offered system should support IP based wireless phones. (xxi) All future upgrades of system software as and when released shall be provided by vendor subsequently without any additional cost to the user. The user will however, procure essential hardware required. (xxii) Account Code. It should be possible to enter account code before the call. It should be possible to allocate a class of service that forces a user to enter an account code when a call is made. (xxiii) Minimum No Digits Dialed. Minimum 13 digits dialing should be possible. (xxiv) Alphanumeric Dialing. Allow users to place a call by entering an alphanumeric name instead of dialing a long string of numbers. Calling Number and Name display must also be available for Analog Extensions. This feature should be as per the Bell core Custom Local Area Signaling Service (CLASS) CND standard, which uses FSK for the display to be enabled. Compatible Analog Phone with CLID display must be quoted. (xxv) Dynamic Route Allocation/Alternate Routing. Facility to automatically route call on the shortest path / re-route calls which encounter busy trunks on the initial route. Automatic digital translation is carried out by the system. Provides the possibility of reaching external destinations via different routes.

(xxvi) Busy Tone Detection. Busy tone detection on all trunk line (Analog / Digital) must be available in the system. (xxvii) Centralized Attendant Service. Enable private network attendants to be consolidated on one of the switches in the network. (xxviii) Configuration Data Changes. The system should allow selected configuration data to be upgraded from the system terminal. For system integrity certain commands should be protected by way of password and unable to be changed from the customer administration terminal unless a high level password is entered. The commands that should be protected are those that could affect traffic if entered incorrectly or could be used to perform telephone fraud (i.e. Direct Inward Subscriber Access Feature). These commands will be reserved for selected maintenance staff. (xxix) Distinctive Ringing. The system should provide audibly different station ringing patterns to distinguish between internal and external calls (xxx) Flexible Number Plan. The system should have no direct correlation between permanent positions in the switch and the extension directory numbers. The dialed extension directory number is translated into the line number appearance by the processor. A user must be able to be assigned an extension number and keep the same number regardless of their location within the building complex. This greatly simplifies the updating of directories and meant that when a person shifts they do not have to advertise a new number, therefore saving money on stationary and business cards, etc. (xxxi) Fully Restricted Extensions. Extensions must be able to be barred from all forms of outgoing access, except calls to Emergency Service, like police, fire etc through call of service programming. This will restrict the extension to receiving incoming calls only. (xxxii) Integrated Electronic Directory. Allows internal system users Viz. Digital and IP Telephone users with display equipped terminals to access the system directory through a menu driven option for retrieving the information by name, appointment or telephone number, use the alphanumeric buttons to key in and retrieve the required information from the system directory. The directory will contain an alphanumeric listing of the names, appointments and extension numbers assigned to all voice terminals administered in the system. (xxxiii) Multiple Operator Positions. Multiple Operator positions should be provided, and exchange lines and functions may be grouped to be handled by one or more operator positions. The system should have a provision to support at least 30 operator

DRAFT COPY
Page 23 of 35 consoles. (xxxiv) System Traffic Reports. Traffic statistics should be provided on incoming and outgoing trunks groups, attendant consoles, station hunt groups and individual stations. The information reported must include the number of calls and call duration. (xxxv) Power Failure Restart (Automatic). System should be provided with battery back up. However, in the event of loss of system power, at restoration the system could perform an automatic start up without human intervention. (xxxvi) Power Failure Transfer. In the event of total loss of power or processor malfunction, analog/PSTN lines can be automatically through switched to selected predefined extensions. (xxxvii) Tenant Partitioning. Provide telecommunications service to multiple independent groups of users through a single PABX. Most commonly, this feature is used to provide telecommunications service from a single provider to multiple tenants of an office complex. The feature can also be used to provide group services, such as departmental attendants or multiple music sources, on single customer system. (xxviii) Terminal Translation Initialization. The TTI feature should enable a user to associate a terminal administered without hardware translation to a valid port address by dialing a special digit sequence (Feature access code, TTI security code and extension) from a terminal connected to the port. It also should allow a user to disassociate a terminal from its port location by dialing a similar disassociate digit sequence. This feature should be able to share an extension to several users hence prevent the requirement to move a telephone set from one location to another location by using the same telephone number. Subscriber only need to key in the Feature Access code, TTI security code and his extension only, and then the subscriber can make a call or receive a call from that telephone set. (xxix) Card Lock Out. Fault on one or more analog/digital line ports should not lock out the entire card. Even if one port is working there should not be card lock out. (xxx) Boss Secretary feature. The incoming call to the officer shall ring on secretarys phone with option of ring on both telephones. It should be possible to activate the Boss/Secretary telephone for enabling the telephone for above features.

It should be possible for the Boss/Secretary to contact each other using one touch key on digital telephone and by dialing one or two digit code on analog telephone. There should be no requirement of using plan telephone for utilizing this feature. (xxxi) Password Display Suppression. When a password is entered in a display equipped terminal the display should suppress the digits so that no one present can deduce the password. (xxxxii) Mixed Numbering. It should be possible to have both Closed and Open Numbering scheme. (xxxiii) Class of Service (COS). Should be able to define whether or not voice terminal users may access the following features and functions: Automatic Callback, Call Forwarding All Calls, Call Forward Busy / Dont Answer, Data Privacy, Extended Forwarding All, Extended Call Forward Busy / Dont Answer, Priority Calling, Restrict Call Forwarding Off-Net, Personal Station Access, Trunk to Trunk Transfer Restriction Override, Off-Hook Alert, Console Permission and Client Room. (xxxiv) Blast Dial Out: User should be able to dial a single number and have PBX call to 8 other pre-administered endpoints, conferencing them all together. The system should be configured with the following: Unlimited 3 party conference calls within subscribers of main exchange minimum simultaneous 10 x 8 party auto dial-out meet-me conference calls minimum simultaneous 20 x 5 party meet-me conference calls (xxxv) The following basic telephony features to be provided by the offered system:(aa) Abbreviated Dialing

DRAFT COPY
Page 24 of 35 (ac) Automatic Callback on Busy (ad) Automatic callback on No answer (ae) Direct Inward Station Access (af) Call forwarding Unconditional (ag) Call forwarding on No answer (ah) Call forwarding on Busy (aj) Malicious call trace (ak) Group Call Pick up (al) Extended Group Call Pickup (am) Call Park (an) Call retrieve (ao) Calling line identification restriction (ap) Call waiting (aq) class of service (ar ) Hot Line (as) Delayed Hotline (at) Do not Disturb (au) Do Not Disturb override. (av) Call Hold (aw) Call Transfer (ax) Internal Music On Hold

(ay) External Music on Hold Support (az) Last Number Redial (ba) Save Number Redial (bb) Instrument locking for preventing outgoing calls (bc) One Number service.-Through this feature it should be possible to have the same number for internal extension and Mobile Number. Through this feature both internal extension and Mobile number will ring simultaneously and once the call is picked up from either of the devices the ringing on the other device stops. This requires integration of PRI Lines with DOT/MTNL. This feature may also be termed as Parallel ringing. The offered system should be configured for 5 such user licenses. (bd) Blind Transfer of calls (be) Call conference min. 3 Party from analog, digital and IP Phones (bf) Call conference min. 6 Party from analog, Digital and IP Phones with password protection (bg) Call Toggle (bh) Support for Single conference of min. 30 Party using a server based conferencing solution (bi) Call Consultation (bj) Display of name and number on analog, digital and IP Telephones. (bk) Sped Dial Individual (bl) Speed dial Central (bm) Hunt Group Cyclic (bn) Hunt group Linear 8 System Administration & Maintenance Facilities. System administration and maintenance terminal should be provided for the purchased capacity. This should be PC based system running user friendly, GUI/ Windows based administration & maintenance software. (i) System management should automatically check through series of tests the normal operation of the system. (ii) System shall have the provision of instant fault information. (iii) System shall have the provision of automatically identifying and isolating faulty trunks. This should be done on daily basis automatically or invoked by System administrator and results output on Maintenance terminal. (iv) The system shall maintain a history log of last 500 commands/ 7 days along with the log-in name and commands given.

DRAFT COPY
Page 25 of 35 (v) It should relieve the user from remembering lengthy procedure and formats for data changes and shall use simple English commands only for the same. (vi) There should be `help facility for the administrator for inputting commands. (vii) The administration should be secured by way of password protection. It should be possible to have different layers of password. (viii) The system management terminal shall be capable of adding/ modifying hardware/software at main location and remote

(ix) Location from main location only. (x) System Administration terminal should carryout system health check. (xi) Scheduling. The scheduling capability should enable users to specify a task to run at a specific date and time. A Task could be a collection of one or more operations that users can specify to run at a predetermined time. (xii) History Log. The history log should enable Ucers to view the results of running and completed tasks. (xiv) Call Accounting Data Export. The Call Accounting Data Export feature should enable users to export information on station maintenance terminal. (xv) Import/Export Capability. This should include easy graphical exporting and importing of login, coverage paths, hunt groups, data modules, stations, trunk groups, directional commands, and Virtual directional numbers. (xvii) Performance/status/information. The software, through real time monitoring should be able to provide the status of extension/group of extensions and trunks/trunk groups with respect to the EPABX performance at any time on request basis through screen disp (xviii) Maintenance Console. The console should have Alarm indications. The system should also automatically report the alarm to the system administrator / designated attendant console/extensions. The alarms should indicate the following conditions :(aa) Major Alarm: The system has logged a Major Alarm. Major alarm would necessitate emergency transfer procedure. (ab) Minor Alarm: The system has logged a Minor Alarm. (ac) Reset-Alert: reset of system at level 2 or 3 has been performed. (xxiii) Circuit Pack LEDs in the System. Each circuit pack should have LEDs on the front panel visible at the front, to distinguish various status : (aa) Alarm: When the system detects a fault in the circuit pack. (ab) Testing: When the system runs tests on the circuit pack as part of background maintenance or demand testing. (ac) Busy: When the circuit pack is in use by the system. (xiv) Fault Detection/Alarm. The software should have built-in self diagnostics/power on confidence test, and should constantly monitor the exchange performance and report/generate suitable alarms during any failures to indicate/localize the faults besides k (xv) Diagnostics. Detailed software diagnostics/test runs should be provided to facilitate system trouble shooting to localize at least the faulty PCB/group of circuit packs. Bidder should submit the details of diagnostics/ tests along with the Technical bid (xvi) Automated Fault reporting system. Should be able to indicate line status of all connections along with nature of fault. 9 IP Softphone 1 It is envisaged to provide the IP users with a true unified communication client with Single Intuitive Interface to Access communications from one client including

voice, video, voice messages, audio/video conferencing, Telephony Presence and communication history It should provide the following minimum facilities. The softphone should work in both H.323 and SIP modes.:2 The users should have access to all the telephony features available on IP Phones like Multiple call appearances and one-button access to frequently used features, such

DRAFT COPY
Page 26 of 35

Schedule Add on items for EPABX- Unified(Server based)

as Answer, Conference, Transfer, Hold, Redial etc. 3 The user having Integrated Webcams should be able to make video calls as easily as making a phone call. Features should include audio/video features like call, transfer, forward, conference, hold, mute, call coverage. The softclient should support High definition video calling from day 1 with HD web cameras. 4 The IP softphone users should be able to view the IM and telephony presence of other softphone usersand do instant messaging with each other. 5 The softphone should support offline IM messages. i.e. if a user is offline he should receive the IM messages sent during the time he/she was offline. 6 Users should be able to initiate minimum 6 party ad-hoc audio conference call. 7 The users should be able to access to voice mail by clicking on Icon 8 The client should provide a capability to click to call from the numbers highlighted in the web browser 9 Users should be able to use this client as standalone telephony client with Headset & Mic 10 Help Desk Functionality To address the various needs/queries of the employees related to IT, HR, Logistics etc in a centralized manner it is envisaged to create centralized help desk.The Proposed telephony system should be provided with a contact center kind of a functionalities. Following call center functionality should be provided along with the system for 100 agents from day 1. This help desk functionality should be inbuilt in the system and should not require any external server. Automatic Call Distribution (ACD) features. (i) Agent Login IDs (ii) Music in Queue (iii) Auto-Available Split/Skill (AAS) (iv) Multiple Call Handling On Request (v) Multiple Call Handling Forced (vi) Service Observing (vii) Automatic Call Distribution (ACD) (viii) Most Idle Agent (MIA) Across Splits/Skills (ix) Agents in After Call Work (ACW) Considered Idle (x) Redirection of calls On No Answer

(xi) Basic Measurements (xii) Holidays based call routing Reporting. (i) Total incoming calls received in group (ii) Average speed of answer (iii) Abandoned call (iv) Average abandoned time (v) Average talk time (vi) Average staff (vii) % service level of group Note:Indentor shall provide min. 7.5 KVA UPS for min. 2 Hrs back up.EPABX shall operate on 230V+ or - 10% ,50 Hz .

Schedule 9 Add on items for EPABX- Unified(Server based)

Add-on items quoted shall be suitable for EPABX-Unified (server based).Detailed specification of all the items quoted shall be indicated by the tenderer. 9

DRAFT COPY