0% found this document useful (0 votes)
31 views7 pages

Specs - 2024 05 27 11 51 26

The document outlines the technical specifications and requirements for the supply, installation, and commissioning of an IP EPABX with Media Gateway system. It details the necessary features, server specifications, terminal and trunk support, voicemail and conferencing capabilities, as well as compliance with local content regulations and security measures. The proposal must include a modular design, support for various communication protocols, and a mobile app with specific functionalities.

Uploaded by

Varun Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
31 views7 pages

Specs - 2024 05 27 11 51 26

The document outlines the technical specifications and requirements for the supply, installation, and commissioning of an IP EPABX with Media Gateway system. It details the necessary features, server specifications, terminal and trunk support, voicemail and conferencing capabilities, as well as compliance with local content regulations and security measures. The proposal must include a modular design, support for various communication protocols, and a mobile app with specific functionalities.

Uploaded by

Varun Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Supply, Installation and Commissioning of “IP EPABX with Media Gateway”

System

IP-EPABX Technical Specification


1. Technical Specification for Server Based IP EPABX

The EPABX system should be of IP EPABX with Media Gateway category based on Server media gateway
Architecture. It should support distributed architecture where in it should be possible to distribute
servers as well as media gateways at different locations. The IP EPABX system must be based SIP
standard so that all standard SIP terminals available in the market can work with system any time
without any problem. Offered IP Phones along with the IP EPABX must be based on open SIP standard.

2. TECHNICAL SPECIFICATIONS FOR IP EPABX SERVER

a) The offered system should have a valid TEC GR & ER approval. TEC-GR approval for all Type-I, II & III approval
should be mentioned in the TEC Certificate. The tenderer must submit valid TEC certificate as per
TEC/GR/SW/PBX005/01/SEP-16 or latest for the particular model of system Quoted and the same must be
issued in the name of Manufacturer.
b) Make in India: The tenderer should provide self-certification specifying that the item offered meets the
minimum local content (Class 1 Local Supplier) and shall give details of the locations(s) at which the local value
addition is made.
c) The system should be based on open standard server-gateway architecture running on Linux OS supporting
Analog, Digital, IP, SIP and Mobile App Extensions. EPABX System on card-based CPU will not be acceptable.
d) Offered solution must be based on IMS architecture with CSCF, HSS, MRF & SGW. Solution must be installed
on both physical as well as virtual server.
e) IMS must provide a uniform and seamless communication network where in Mobile users of private 4G/5G
network can communicate with wired FXS/Digital/IP phone users seamlessly.
f) IMS must be 3GPP standard along with provision to integrate with EPC Core to connect eNodeB & gNodeB for
4G/5G Network
g) All applications such as Call Control, UCS, NMS, Database, Billing, Load Balancer in single server. No separate
server for any application.
h) Server in HA mode can work on single port, no other port will be required for data base synchronization.
i) REDUNDANCY: The call control servers should be redundant and the solution should be based on (Active-
Active) Architecture. 2 servers (Main & Hot standby) will be installed. In case of failure of main server, Other
server will take over the entire load of that users without disrupting of any of the call.
j) All gateway and IP Phones of any particular server location should be registered on their respective server
k) The server should be of OEM only. The proposed server should be capable of supporting at least 780 SIP
extensions and solution will be deployed with 780 licenses from day 1. Only gateway with requisite cards is to
be procured for additional users
l) The server should have the following minimum specifications: Intel Quad core, 8 GB RAM, hot swappable
power supplies, 2 x 1G LAN ports. The vendor may provide better specifications available at the time of
bidding.
m) The system should support SIP trunks to interoperate with other PABX's & also to work with SIP Trunk from
service providers.
n) Voice CODEC support G.711, G.729, G.729a, G.722, OPUS. or any less utilization bandwidth across WAN and
LAN
o) Video CODEC: H.264, VP8 or equal
p) The system should support at least 30 remote sites on the same platform through gateways
q) VIRUS Protection: The system should provide complete inbuilt encryption capabilities or features without any
external firewall, with the ability to encrypt all traffic (media and call control signalling) between IP phones,
soft phones, call controllers and all other associated endpoints via a strong encryption features like MD-5,
802.1x, AES 128, TLS & SRTP.
r) System should be able to provide centralized voicemail with the option of Distributed centralized voicemail in
case of connectivity failure.
s) The system should support PRI/ E1/Analog/Digital/Radio/GSM/IP/SIP Trunks& the system should be available
with 780 perpetual licenses from day 1.
t) The communication server should offer BHCC (Busy Hour Call Completion) of at least 2,00,000 per server to
ensure superior traffic handling capacities.
u) The offered system should be modular in design. The architecture of IP EPABX should be capable of seamless
migration to its maximum capacity by simply adding licenses on the set of control server without
compromising on any functions/ features of this system or any degradation of service.
v) The proposed communication system should have a highly secured, encrypted IP supporting hybrid Trunks
e.g. Analog CO, Digital Trunks, PRI/SIP Trunks.
w) Offered Gateway must have universal in architecture where all type of card should support from day 1like FXS,
FXO, GSM, E1/PRI, DIGITAL, RIC, E&M and the same must be shown during POC and acceptance of the system
without any additional gateway for any type of interface.
x) System should support Diffuser for QoS (Quality of service) for the voice packets traveling over data networks
y) The equipment quoted by bidder must be SIP compliant.
z) The offered must be approved with TEC ER from MTCTE & Approval from NABL for below temperature as per
IS Accordance:
aa) Conformity to Dry Heat for 16 hours at maximum specified temperature degree C in accordance with
IS:9000/part-3/section-5/1977 latest.
bb) Conformity to Cold Test for 4 hours at minimum specified temperature degree C in accordance with
IS:9000/part-2/section-4/1977 latest.
cc) Conformity to Damp Heat (Cyclic)Test for 2 Cycles of 24 h each at a temperature of 40 degree C & 95% RH in
accordance with IS:9000/part-5/section-1/ 1991 latest.
dd) Provisions of Make in India Policy 2017 issued by Govt. of India, as amended from time to time, shall be
followed for consideration of tenders.
ee) Bidder must have an ISO certificate.
ff) Perpetual license for lifetime to be provided by OEM .
gg) The manufacturer must have DSIR recognized R&D office in India.

hh) If required, the bidder/s may be asked to demonstrate IP EPABX setup along with sample
equipment during STEC to verify the technical specification of the system. In case of failure the
bidder will be declared disqualified. All equipment will be tested as mentioned in specs along with all
card & phone support.

3. Desired Features & facilities of IP EPABX

a) Inbuilt system dashboard


b) Security 802.1x/ MD-5/ AES/ SRTP/ TLS1.2 to prevent DOS attack
c) IVRS
d) Emergency call to the predefined numbers using short code
e) Emergency alert to predefined number with predefined messages on SMS/ WhatsApp mapped
to the code.
f) Connectivity with ITSP service providers
g) CDR with programmable archiving period and retrieval
h) One number service
i) LDAP functionality
j) Alphanumeric numbering plan
k) Multi-level Auto-attendant
l) Boss-Secretary feature using IP phone
m) Class of Service unlimited.
n) Day/Night Mode
o) Mobile/Desktop client supported with Video calling
p) Voice paging on IP phones
q) 3 Party Video Conference using SIP Video Phones
r) Busy lamp field
s) Call Forward All/ Busy/ No Answer / External
t) Listen-In/ Barge-In/ Whisper
u) Restrictive dialling
v) VIP number restrictive access
w) MWI (Message Wait Indication)
x) Own Extension PASSWORD Change
y) Call Pick up Extension/ Group
z) Call Forking aa)Conference 3 Party / Multiparty bb)CLI with Name cc)Auto provisioning/ zero
configuration dd)Realtime graphical display of inbound calls ee)Operator console with
AB/AT/AS/VIP facility ff)Distinctive Ringing based on CLI / Internal/ External)Custom Ring back
tone

4. TERMINAL SUPPORT

System should support the following type of terminals


a) Analog Phones
b) Digital Phones
c) Radio sets
d) IP Hard phones
e) IP/SIP Softphones
f) Video Hard/Softphone
g) 3rd party SIP phones RFC3261 Compliant

5. TRUNK SUPPORT
System should support following types of trunks:
a) Analog Trunks
b) PRI
c) SIP trunk
d) GSM
e) SIP trunk
f) E&M

6. VOICEMAIL FEATURES

a) All messages left in the VMS shall be immediately stored in a hard disk or other storage medium subject to
review by the Employer. The hard disk or the storage medium shall be backed up with a mass storage device
automatically and periodically. The interval between back up shall be user programmable.
b) Incoming calls to the VMS shall be served on a first-come-first-serve basis. The PABX switch network shall
provide automatic call distribution functions to evenly distribute the calls to input ports of the VMS. c)IVR
functionality should be available

7. CONFERENCING FEATURES

a) The system should have built-in greater than 48 party Ad-Hoc or Meet-Me audio conferencing bank from day
1.
b) Multiple conferences with variable number of users should be possible within each of the conferencing
banks.
c) System should be able to generate detailed reports about the conference.
d) System should support scheduling of conference call.
e) Conference should be available in various modes like Meet me, scheduled conference etc.
8.1 Digital Phone Type -1

DIGITALPHONE
1 The Digital phone should work only on two wires.
2 Min. 4-inch graphical display
Minimum4 Nos. of soft keys with Navigation buttons with OK button,
3 UP/DOWN, RIGHT/LEFT
4 Minimum 16 Nos. or more of Programmable Keys with LED indication
Digital phone should work minimum 1KM from the gateway on 0.5mm
5 Copper single pair cable.
6 Handset;
7 Push button or soft key for each Direct Line Telephone ;
8 12-push button keypad for dialing ;
9 Adjustable volume control for speaker and ringer ;
10 Hands-free operation through built-in speaker and microphone;
11 Powered by the Central communication processor;
12 Visual display of details for incoming and outgoing calls;
13 Display of call duration ;
14 System lock display ;
15 Lamp for message waiting ;
16 Lamp for ringing signal

8.2 Digital Phone Type-II

DIGITALPHONE
1 The Digital phone should work only on two wires.
2 Min2 X16 Character
Feature keys like Mute, Conf etc with volume UP & Down
3
4 Minimum24 Nos. or more of Programmable Keys with LED indication
Digital phone should work minimum 1KM from the gateway on 0.5mm
5 Copper single pair cable.
6 Handset;
7 Push button or soft key for each Direct Line Telephone;
8 12-push button keypad for dialing;
9 Adjustable volume control for speaker and ringer;
10 Hands-free operation through built-in speaker and microphone;
11 Powered by the Central communication Processor ;
12 Visual display of details for incoming and outgoing calls;
13 Display of call duration;
14 System clock display;
15 Lamp for message waiting;
16 Lamp for ringing signal
9. Push Button Phones

Push Button Phones.


1 16 Digit two line LCD Alphanumeric Display
2 FSK / DTMF Compatible CLI
3 99 Incoming call memory
4 10 Outgoing call memory
5 Phone Book 50 Nos
6 8 one touch and 10 two touch memory
7

8. Functional Requirement of the Server Based IP EPABX

8.1. IP/LAN network, LAN switches, UPS Power back up etc. shall be provided by the buyer within
Building or campus.
8.2. The Central Location i.e. where the Servers in Hot standby/duplicated should have minimum 20
simultaneous voice paths available to communicate with all other remote locations & shall be
expandable up to 30 simultaneous voice path in future on same hardware.
8.3. In the normal operation in future, the entire system (up to 700 lines) will works like a single System
with feature transparency.
8.4. In case of scattered complex where the multiple Media Gateways are connected with the Server,
failure of link between Server Location to any remote locations, the remote locations shall work as
an isolated EPABX with all standard feature & functionality.
8.5 The Server based IP EPABX system should have a provision of expandability minimum up to 700
lines/extensions (Analog & SIP) on same Server without clustering & cascading of multiple Server.

9. Media Gateway Specification for Server Based IP EPABX


9.1. Should be same OEM make rack mountable solution with required number of universal slots
architecture for equipped & each gateway should have minimum 256 ports capacity with minimum
8 or 16 universal slot. Gateway should be supplied with 224 Analog Ports, 112 Digital ports, 8
Analog trunks, 2 Port RIC, 4 PORT GSM & 1PRI.

9.2. Should be equipped with self-survivability with all standard telephony feature & functionality so
that in event of failure of IP/LAN/WAN Link with the server, it should function as stand-alone
Exchange.

9.3. Should have modular architecture with the ability to stack/cascade multiple gateways in a single/
different location. One or more such stacks/cascades should be able to place at same locations to
achieve ultimate capacity.

9.4. Should have redundant IP Ethernet (10/100/1000 Base-T) ports& dual AC & DC power supply
module on each gateway stack.

9.5. To ensure security of IP voice packets, end-to-end Media Encryption must be supported. The
Encryption employed should be strong and standards based.

9.6 Media gateway should work independently in case of out from server due to link failure.
10. Mobile App
Mobile App must provide below mentioned features.

a) Facility to dial as audio/video call


b) Call history Search (Call Log: incoming, outgoing and missed calls)
c) Busy Lamp Field (Buddy List)
d) Call swipe-seamlessly moving ongoing calls between devices
e) Camp-on
f) Simultaneous ringing on multiple internal & external extensions.
g) Call Transfer (blind, Consultation)
h) Group Call Pickup
i) Last Incoming Number Redial
j) Call pickup user
k) Call Park / unpark
l) Voicemail
m) Text message
n) Audio conference
o) Bargin (Break in)
p) Call forward all, busy.no answer
q) Follow Me
r) DND
s) Recording
t) FAX
u) Dialling rights (intercom, local, std)
v) Directory
Material shall be provided strictly as per the specifications for the BOQ

Supply, Installation and Commissioning of IP-EPABX System


Sr.No. Particulars Quantity Units
1 2 Server in Active-Active with 780 universal SIP licenses 1 Nos.
2 Analog Extensions 224 Nos.
3 Digital Ports 112 Nos.
4 Analog Trunk 8 Nos.
5 PRI 1 Nos.
6 GSM 4 Nos.
7 RIC 2 Ports
8 Digital Phone Type 24 Nos.
9 Digital Phone Type 84 Nos.
10 SIP Trunk 16 Nos.
11 UC Mobile App Support 1 Nos.
12 Online UPS for minimum 2 hours back up with batteries. 1 Nos.
13 Telecommunication Cable 50 Pair 600 Meter
14 Telecommunication Cable 30 Pair 500 Meter
15 MDF 100 Pair 5 Nos.
16 Push Button Phones 20 Nos.
17 Warranty 1 Year
18 Installation and commissioning 1 Job

You might also like