SUMMARY

• Exposure to teh entire range of telecom activities ranging from Requirement analysis, Proposal writing, preparing Statement of Compliance, Design, Development, Customer support, Installation and Sustenance.
• Strong software skills: Java, C and C++ language with noledge of Linux internals.
• Telecom and networking background along with noledge of Contact Center technologies, LTE, IMS, SS7, ISDN, VoIP and SIP.
• Vast experience in Cisco UCCE,UCS,ICM, Call manager, CVP and Social Miner components.

PROFESSIONAL EXPERIENCE

Confidential

Technical Lead

Responsibilities:

• Playing teh role of a Technical Lead for Cisco’s Contact Center Business Unit
• Writing proposals and working in coordination with presales and marketing team based on customer’s requirements.
• Work along with teh Advance Services team for requirements gathering and installing of Cisco’s Contact center products.
• Responsible for design and development of enhancements for Cisco’s Intelligent Contact Management (ICM) product. Enhancements include Social Miner, Congestion Control, solution call tracing, Router requery and Mid call tracing for ss7 calls.
• Sustenance of Network Interface controller component, Outbound and Router within UCCE/ICM product.

Confidential

Technical lead

Responsibilities:

• Assigned a Technical lead role to lead Application platform team of four members dat deals with various applications on teh platform level.
• Responsible for requirement gathering, providing design solutions and maintenance of teh various applications dat basically deal with remote installation and maintenance activities of all teh hard wares in teh prepaid billing system.
• Acting as a single point of contact for all technical issues related to Application platform team.
• Responsibilities also include training and initiating various noledge transfer activities to new joiners and trainees.

Confidential

Technical lead

Responsibilities:

• Part of teh System Management team for Narrow Band Access Products of Ericsson’s AXE and MSC switch.
• Led a project on teh development for migration of ATM to VoIP backbone for teh Ericsson’s AXE switch.
• Involved as teh technical coordinator for teh MSC R13 project, playing a vital role in defining solutions and acting as a single point of contact for all technical issues.
• Responsible for providing design solutions by writing proposal documents and implementation activities related to one of teh subsystems of teh Ericsson’s AXE and MSC switch.
• Managing system implementation tasks related to Ericsson’s AXE and MSC switch.
• Responsible for designing and implementing future developments in teh system

Confidential

Telecom Engineer

Responsibilities:

• Primarily responsible for operation, maintenance and administration of Ericsson’s AXE switch.
• Responsibilities involve mainly B - number analysis, routing issues, coordinating with other ILTs, fault management and generation of traffic reports.
• Responsibilities also include installation and maintenance of Digital Loop Carriers (media gateways), a product of UtStarCom, along with carrying out teh necessary tests.
• Managing teh whole network of Digital Loop Carriers through iNetman NMS (Network Management System).
• Responsible for provisioning of circuits through clarity and iNetman client.
• Responsible for managing teh Atrica network through Aspen NMS

Confidential

Software Engineer

Responsibilities:

• Played a vital role in development of network protocols for CORAL IRIS system on Linux platform
• Installation and maintenance of Coral Tadiran systems, a product of ECI Telecom.
• Configuration of ISDN network and also providing suitable interface to Spacenet, a network of ISRO.

Technical Lead

Responsibilities:

• Responsible for teh sustenance of Intelligent Contact Manager (ICM) product. Activities include providing 24x7 support to teh product, design and development of enhancements.
• Primary area of expertise is in Network Interface controller component involving protocols such as VOIP, H.323 and SS7.

Technical Lead

Responsibilities:

• Remote Maintenance Unit is a critical application in teh Comverse Prepaid billing system dat is responsible for instaling, upgrading, taking backups and restoring OS based images of any hardware device in teh architecture.
• Teh objective of dis project was to adapt dis application to support all teh Linux based devices in teh architecture as well.

Technical Lead

Responsibilities:

• Development of test utilities to support NFS porting with DU and Linux systems
• dis activity involved developing test utilities for testing teh porting of NFS (Network File system) with Digital Unix and Linux based systems.
• Teh test ?utilities had to open teh files in different mounted locations and also write data into files at different mounted locations.

Technical Lead, Design and Coding

Responsibilities:

• Design of new version of STK (Software Tools Kit) for RMU (Remote Maintenance Unit)
• STK consists of an application called Remote Installation Package(RIP). dis application is responsible for installing and removing different packages on remote systems at teh customer location from a central location. Teh objective of dis project is to adapt dis particular application to Linux based systems.

Technical Lead

Responsibilities:

• Migration from Perl scripting to Python for SET command in LBA (Load Balanced Application)
• Teh SET command for LBA sets all teh required parameters for teh LBA to operate upon. dis operation of SET command was earlier written in PERL.
• Teh objective of dis project was to rewrite teh whole script in PYTHON.

Technical Lead

Responsibilities:

• Migration of TDM to IUA in Ericsson MSC R13.0 for layered architecture
• Teh objective of dis project is to implement Sigtran framework into Ericsson’s MSc and Mobile MGw. dis is also a migration project from teh typical TDM switches to softswitches.
• Teh sigtran protocol used was ISDN user adaptation (IUA) for transfer of signaling messages. Teh study involves teh procedure for defining and implementing teh solution as per IUA RFC.

Technical coordinator

Responsibilities:

• Teh previous configuration of teh Ericsson’s MSC architecture is based on teh non layered architecture, not accepted by many customers.
• Teh objective of dis study is to connect PABX to MSC server via Mobile media gateway. Here teh mobile media gateway is remotely connected to teh MSC server where teh network cloud is ATM.
• Teh activity also defines teh strategy for migration from non layered architecture to layered architecture. Teh study was divided into three sections: O&M section, traffic handling and D-Channel signaling.

Technical coordinator

Responsibilities:

• dis study project deals with teh implementation of calendar application using teh VOCAL concepts. When teh called party is not available, details from his calendar present in teh Microsoft exchange is fetched and displayed to teh calling party. IPC-UDP concepts are used along with SIP. Teh concept used in teh setup is VoIP. SIP soft phones are used for dis purpose.

Design and implementation

Responsibilities:

• Teh objective of dis project was to design forlopp hadling. dis concept deals with unexpected exits in teh AXE 810 switch.
• On implementing dis particular feature unexpected exits can be handled without causing major impacts to teh system.

Implementation

Responsibilities:

• Teh objective of dis project was to allocate teh time slot to each subscriber in a sequential manner after a restart takes place.
• By doing dis, teh overflow of teh stack is avoided and theirfore large restarts of teh AXE switch can be avoided.

Implementation

Responsibilities:

• Teh objective of dis study is to adapt teh Ericsson’s AXE switch to support to different variants of teh PRA.
• Since teh AXE was supporting only teh ETSI standard, some modifications in teh protocol was required to support dis ANSI standard.