Experienced Professionals

Capgemini Indiana, United States of America
Apply Now

×

Select how often (in days) to receive an alert:

  • Apply Now

  • Start applying with LinkedIn Start applying with LinkedIn

  • Please wait...

Collab

Job Description

 

•            Technical expertise Required CUCM - Call routing/Media resources /Protocols (SIP, H323, MGCP) - worked on all 3 and have strong knowledge of different types of Codecs.

•            Integration with CUC, UCCX, CVP, Gateways and reading debugs & Traces of UC Products.

•            PRI T1/E1, FXO FXS /CME /CUE.

•            Real-Time troubleshooting on Voice Gateways & CUBE.

•            Hands-on experience with reading logs of UC Products, Voice Gateway and CUBE as well.

•            Hands-on experience on taking Packet Captures on different devices & reading those logs as well.

•            Hunt groups /Call pickups/Voicemails and configuration/Types of CISCO routers and differences.

•            Auto attendant and B-ACD.

•            Basics of Jabber & MRA.

•            24/7 Support (ready to work in shift’s).

•            Candidate should be having strong experience in handling P1/P2 issues over bridge/WebEx sessions.

•            Candidate should be able to coordinate with multiple stakeholder’s during outage calls.

•            Candidate should be strong in communication.

•            Candidate should be aware of basic ITIL process.

•            Candidate will be involved in incident management – involves in in-depth troubleshooting skills & providing RCA’s.

Ref. code:  496151

Posted on:  7 Jul 2026

Experience Level:  Experienced Professionals

Contract Type:  Permanent

Location: 

Bangalore, IN

Brand:  Capgemini Engineering

Professional Community:  Manufacturing & Operations Engineering

  • Apply Now

  • Start applying with LinkedIn Start applying with LinkedIn

  • Please wait...

All rights reserved by Capgemini. Copyright © 2025

×

Show More Details

  • "route" is used for session stickiness
  • "careerSiteCompanyId" is used to send the request to the correct data centre
  • "JSESSIONID" is placed on the visitor's device during the session so the server can identify the visitor

Show More Details

Confirm My Choices