,•

ANNEXURE-1 TO THE TENDER ENQUIRY NO. DPS/AMPU/CAP/802

Detailed Technical Specifications of the required EPABX

•:• The offered system should be IP-PBX, enabled with Unified Communication and Collaboration
Application. IP-PBX should employ Stored Program Control (SPC) using Pulse Code Modulation
(PCM) and Time Division Multiplexing (TDM) conforming to latest ITU-T (earlier CCITT) standards
(Preferred makes - Unify (Formerly Siemens Enterprise Communication) I Avaya I CISCO I
Alcatel- Lucent)

•:• The offered system should be of OEM Product and OEM should be a registered member in the SIP
forum community. A documen t proof should be provided by the vender or the OEM

•:• System should be a 100% non-blocking Switching architecture.

•:• System should be highly reliable and ensure uptime of 99.99%

•:• The system should be expandable up to 500 extentions

•:• The system should be able to network up to 30 systems with at least 1000 users in network
mode.

•:• The system should run on Open standard Linux based operating system

•:• The system should support Logical partitioning as per TRAI regulation

•:• The system shou Id be integrated platform with a modular design and distributed processing
structure.

•:• The system should be based on the latest processor, high-level operating system, uniform
system software, open interface and distributed processing.

•:• The Mother Board Processer of IP-PBX should use a 32-bit microprocessor (Pentium). The system
software should be installed on any of the latest devices like Secure Digital Card (SDHC), Flash
RAM, Hard Disc and MO Drive with a minimum of 8 GB memory but not on EPROM.

•:• The system should be with redundant power supply unit (n+1) for the main control unit. The
f ailure of the main power supply unit should not affect any operations of the IP-PBX. The
system should be able to automatically switchover to the standby PSU without dropping any
ongoing calls.

•:• The system should facilitate 5 party Ad-hoc Conferencing feature with 6 simultaneous groups of
conferences possible with any combinations of extensions and trunks.

•:• The system should support universal port architecture for seamless growth and ease of
management. Signaling card and control card should not occupy any universal slot

•:• All the peripheral cards (Extension card, Trunk Card, ISDN PRI Card, etc) are Hot Swappable, i.e.
It should be possible to replace any peripheral card even when the system is in the working
state.

Page 1 of7

,
•!• There should be LED indication on each card, which can help determine the real time status of
the card

•!• The system should support the following interfaces :

• Analogue Extension with CLIP functionality.
• Digital Extension with CLIP functionality.
• IP Extension with CLIP functionality.
• Analogue Trunk with CLIP functionality.
• ISDN BRI Trunk with CLIP functionality.
• ISDN PRI Trunk with CLIP functionality.
• SIP Trunk
• E&M Trunk (Tie Line Trunk)

•!• The system should support the following trunk features :

• Caller ID on all Analogue Trunks
• Emergency transfer of P&T lines in case of power failure or non-operation of IP-PBX
• to selected extensions.
• DID facility
• CO to tie restriction
• Trunk camp on
• MFC signaling
•!• The system s hould utilize single codec per line

•!• The system should support different class of service during the day and during the night

•!• The system s hould support direct connection to any external music source ( for music on hold)

•!• The system should integrate with an announcement/ industrial paging system with a built-in
interface without any external additional hardware

•!• The system s hould provide 100% feature transparency for all voice , data , video, voice mail
automated attendant, call accounting, automated call distribution etc

•!• The system s hould restart automatically without any human intervention when the external ac
power supply is resumed after complete power failure (Even after the batteries are discharged)

•!• Numbering Scheme: The system support Flexible Numbering Scheme wherein every extensions
will be assigned different extension numbers, (ranging from minimum of two digits to a maximum
of 4 digits). Also, it should be possible to change all the facility codes, group directory numbers
for subscriber hunt groups and trunk/page groups, abbreviated dialing codes, etc. as per the
requirements.

•!• Capacity of the communication system should be able to split across a minimum of five
subsystems. This makes it possible to share one communication system for several
companies at the same time.Features in the tenant system include:
• Intercept
• PABX number
• Caller list
• Override
• DISA
• Speaker call
• Call detail recording
• Hotline destinations
• Text messages, advisory messages

Page 2 of7
 • Internal calls
• Internal Directory
• Night service
• Park slot
• Traffic Restriction Groups
• Voicemail
• Toll restriction
•:• VoIP gateway components should be integral part of offered system for connecting IP extensions,
SIP trunking & ITSP' s registration facility without adding any new hardware which will consider
any of the universal slots.

•:• lnskin VoIP Gateway should support any system based proprietary protocols as well as open
standard protocols like SIP.

•:• The system should have at least 8 built in DSP resources without adding any additional modules.

•:• The offer system should be provisioned to support' at least 128 DSP resources without occupying
any system slot.

•:• SIP trunking should be an inherent feature of IP-PBX and the same configure 4 ITSPs on a single
interface card

•!• The system should have an inbuilt Voicemail solution providing the following features:
• Minimum 06 Port Voice Mail system
• The voice mail system have a minimum of 320 voice mail boxes
• The voice mail system have a storage capacity of minimum 32 hours.
• The voice mail system have a facility to provide at least 100 auto attendant mailboxes.
• The voice mail system support Voice Quality G. 711
• The voice mail system have at least 4 different Greetings for: night/day, manual
selection, etc
• The voice mail system provide a Message wait indication (MWI) for Group mailboxes.
• Date and time stamp in all messages.

•!• The system should be equipped to provide an interactive voice response system (IVRS) without
any additional hardware.

•:• The offered system should have following features without adding any external hardware

• Extension to extension calling

• Extension to extension call barring

• Operator calling

• Operator call barring

• Direct Outward Dialing with at least 6 levels of dialing class

• Call transfer by means of RECALL key in tone phones and direct extension number dialing
in case of pulse phones

• Incoming call routing should be possible to a predefined extensions hunting group or

group ringing

• The group ringing and hunting groups should be able to accommodate up to 32 extensions

Page3of7
 • It should be possible to define the hunting groups as either linear or cyclic hunting

• Night mode activation via authorized extensions only

• Different class of service for extensions in the night mode

• Automatic call-back to busy and ringing extension

• It should be possible, via a code, to ring up to 32 extensions simultaneously. These

extensions could be analog phones, Digital phones or a combination of both.

• All extensions should have a facility to register at least one reminder call from their
extension
• All extensions with outgoing dialing facility should be able to register at least 10 memory
numbers from their extensions

• Extensions with access to system abbreviated numbers should not have any toll restriction
for accessing these numbers

• All extensions should have a facility to lock their instruments so as to prevent outgoing
calls. It should be possible to have a locking code of up to 5 digits. It should also be
possible to view or change this locking code from a system administrator Digital phone
• It should be possible to park up to 6 calls in the system
• The extensions, both analog and Digital phones, should be able to initiate a 5 arty
conference with up to 4 external parties

•:• System should support up to 6 simultaneous 5 party conferences.

• Possible to assign extensions to a call pickup group with up to 32 extensions in a
group. Calls ringing outside a group should be answered by a different access code.
• Possible to assign an internal hotline between extensions. It should be possible to
program these hotlines as immediate or as delayed hotlines
• Possible to have different ringtones for internal, external and callback calls. It should be
possible to change these ringtones, at site, as per requirement
• Possible to change the dial tone, ringing tone, call waiting tone, conference tone,
override tone, etc. as per the requirement.
• Possible to access each trunk individually by means of individual trunk access codes.
• Possible to group the trunk lines into at least 4 routes. It should be possible to assign
more than one code to each route.
• Possible to seize the lines of a route in either linear or cyclic mode.
• There is a provision of route overflow for outgoing calls, such that if all the lines of
one route are busy, then the system should automatically select the alternate route
which has been programmed.
• Possible to connect the extension ports of another PABX onto the trunk circuit of your IP
PBX.
• Possible to send 'FLASH TO TRUNK' from both analog extensions and Digital phones.
• The system support both open and closed numbering scheme.
• System support Silent Calling.

•:• The system should provide Unified communication features for at least 50 Users without any
additional hardware or External Server. The system should be further able to expand its
facilities to all the users.

Page 4 of7

,
 •!• The system should provide the following features without adding any external hardware
• Presence includes status based announcements
• Instant Messaging, Multi-user chat
• Favorites includes Call Status
• Visual Voicemail Control
• Voicemail to E-mail Service
• Directory Access
• Call scheduling

The system sho uld support Enhanced UC features

•!• Presence-integrated Telephony: Should be able to change the presence status from Any device.

•!• Visible Voicemail (including Voice mail to Email)

•!• Notification of Voicemail or fax mail on user prefered device.

•!• Instant messaging

•!• Favorites List

•!• Drag and Drop conferencing

•!• Mobility : Call me service, One Number service, Set

•!• One Number Service (ONS)

•!• Directory Access (personal/Internal/External)

•!• Click to Dial

•!• Fax Mail without any external Hardware (should be able to send/receive fax without fax
machine.)

•!• Screen Pop ups

•!• Live call recording

•!• · Personal Auto Attendant

•!• Call journal

•!• Social network integration via XMPP to exchange Presence and Chat information .

•!• Presence enabled Attendant console

•!• UI Integration with Web Collaboration (Desk sharing & Video)

•!• The system support Multi Media Contact Center solution without adding any external Server. It
should be an integral part of offered system

•!• The Multimedia contact center support the following features:-

Page 5 of7

,
 • Skill based Routing
• VIP Call Queue Support
• Fax, Email and Chat Integration
• Various types of reporting

•!• The system should be able to network with any other IP-PBX systems. This networking should
happen either over IP via SIP protocol or over PRlvia Qsig protocol. No proprietary protocols or
solutions will be accepted as part of this project.

•!• The system should support voice networking of multi vender IP-PBX via QSIG software for feature
transparency throughout the network. The system should work with any type of public exchange
or similar network to which it will be connected without requiring any modification in networks

•!• The system should support Video conferencing features with the following standards :
• ISDN-BRI customer access supporting H.320
audio/video/data call
• Transmission rates of 64Kbps/8Kbps
• Full support of ITU-T H.320 Standard (Audio/Video/Data) Audio - G.711, G.729, G.722 and
T.120 Data Standard
• Multimedia Collaboration between customer and users based on ITU-T T .120 data
conferencing

•!• The system should have an inbuilt LAN port. It should be possible to access the system from any
node of the LAN for maintenance purpose.

•!• The system should support centralized system administration using SNMP (Simple Network
Management Protocol)

•!• The system should have the flexibility to add/delete/modify the service features or any other
functionalities without any extensive modification required.

•!• The administrator should be able set different languages system-wide or on a extension-specific basis
for the displays generated by the IP communication system on phones equipped with a display The
following languages are available:
German, English, French, Spanish, Italian Dutch, Portuguese, Finnish, Czech, Danish, Swedish,
Norwegian, Turkish, Polish, Hungarian, Russian, Greek, Slovakian, Croatian, Estonian, Latvian,
Lithuanian, Chinese and Catalan.

Page 6 of7
 ANNEXURE-1 TO THE TENDER ENQUIRY NO.: DPS/AMPU/CAP/802
SPECIFICATIONS FOR OLD EPABX SYSTEM & NOTES

 SPECIFICATIONS OF EXISTING EPABX SYSTEM:

Make : SIEMENS
Model : HIPATH 3550 V.5
Year of Purchase : June, 2008
NOTES TO BIDDERS:
1. The old EPABX System is of SIEMENS Make. Physical Condition of 1 No. of
Siemens Make old EPABX system can be seen at AMD, Southern Region,
Bangalore-560 072. In this Connection you can contact Smt. Sujatha Mudaliar,
Incharge, Engg. Services, AMD, Southern Region, Bangalore on 080-2321 5626 or
alternatively through email on sujatamudaliar.amd@gov.in.
2. Tenderers are requested to give their quote with buyback as well as without
buyback and we reserve our right to place order either at the actual price without
exchange of obsolete item or at the discounted price with exchange of obsolete
item.
3. It should be the responsibility of the Supplier concerned to take back the
obsolete item on “As is where is basis” after delivery of the new EPABX system
ordered.
4. In Case of Exchange of obsolete items, any request for payment of any statutory
levies or taxes towards the sale of the old EPABX system should be borne by the
Supplier Concerned.
5. Bidders should submit an undertaking alongwith their online bid,
“confirming their willingness to take up Annual Maintenance Contract on
yearly basis and maintain the system for a minimum period of 10 years”
after completion of warranty period at AMD, Southern Region, Bangalore.
6. Make/Model offered for the item should be clearly mentioned in your online Bid.
7. In the event of an order, Training Should be imparted to 4 Persons at Purchaser's
site.
8. As the GST column is blocked by DPS with effect from 02.11.2018, bidders
are strictly requested not to quote GST anywhere in the Online bid and also
in annexure if any enclosed to the Price bid, failing which their offer will be
summarily rejected as per Header Point No. 5 & 6 above. GST as applicable
on Basic cost shall be admitted by the Purchaser. (As per Header point no.1
above). Bidders are strictly requested to follow the above guidelines while
submitting their offer to avoid rejection of their offers. In addition to the
above, Bidders are requested to go through all the Points mentioned in the
Header above, while submitting their offers.

Page 7 of 7