Project Software

Banibrata

Dutta

*****, ******* ******, ***

***

Gaithersburg, MD 20877 Ph : 650-***-**** (Cell), 240-***-**** (Home)

abpool@r.postjobfree.com

BANIBRATA DUTTA

SUMMARY:

Nearly 5 years of experience in the design, development

and testing of Telecommunication software with a focus on Communication

Protocol Software (and Firmware) involving High Availability and Distributed

Processing, on both Real-Time and Time-shared systems. Analyzed

requirements, designed solutions, programmed and debugged existing software for

ARMILLAIRE Technologies, Inc s, A-2000 Switch for Internet PRI

Offload cum International Gateway with Modem Fault Detection

(with Load-Balancing) and A-5000, the Next-Generation VoIP

enabled Class 5 switch with Integrated Voice and Data services (VoATM

core). Designed and implemented TeleSys iSCP number translation (internet

SCP). Experience on Trillium, ADC NewNet (Access Manager), HSS and TeleSys

SS7stacks (ANSI, ITU-T, Telmex/Mexico and China variants), and SS7-MTP2

cards from Voice-Board Corporation, ADAX and PTI. Have

in-depth knowledge of ISUP and Call-Control (including AIN 0.2

and IN-CS2) and, working knowledge of interworking

modules. Experience with INETSpectra Tester and Abacus

Call-Load Generator. Have developed SCTPprotocolstack.

Knowledge of SIGTRAN protocol M3UA, for signaling transport,

using the highly portable Telecom software development Object-oriented

framework, called ACE (Adaptive Communication Environment). Have an

understanding of the Linux HA philosophy. Have worked on CDOT-MAX-XL

switch s IOP, implementing MML commands, and also on ISDN D-channel X.25

gateway, MAX-XL/Packet-Handler interface module. Very strong programming skills

with C, C++, Perl and Korn

Shell, on the Unix platform (Solaris 2.6 and Linux), and also

QNX and VxWorks (POSIX and Native API s).Used

utilities/tools like Imatix s Libero (FSM tool), Imatix sSMT (user

space Symmetric Multi Threading tool), RCS (Revision Control System) and

K-Develop 1.2 under Linux. Comfortable with Rational Purify and SUN-Forte

/ SUN-Workshop on Solaris 2.6. Comfortable using RationalClearCase

and RationalClearQuest for development. Also comfortable with

CVS.

SKILLS PROFILE:

Hardware:

Armillaire ISM (VoATM Media-Gateway), SUN SPARC

(Ultra5, Netra), HP Workstations, Intel based PC s, CDOT-IOP (Unix I/O

Processor), CDOT-MAX-XL (CDOT RTOS based), ADAX APC-7 SS7 card, PTI Channel-7

SS7 card, VOICEBOARD SS7 cPCI card, INET Tester (MTP3/MTP2

Conformance/Verification testing and ISUP/TCAP traffic generator), SUN

Compact-PCI platform CP-440, Yurie System s PSAX switching hardware supporting

DS1, DS3, E1, HD-E1, OC3, Ch-OC3 line cards and Lucent 2300 series PSAX,

Shunra Technologies STORM WAN Emulator, Eastern Research s DAX (multi-system

MUX/DEMUX), Abacus Load Generator.

Operating System:

SUN Solaris 8 & 2.6, Linux, HP-UX 10.x, VxWorks, QNX, Win-NT,

Win2000-Pro (Windows platform mostly for host based development).

Special Software/Tools:

Rational Purify, SUN Forte/Workshop (on SUN

Solaris), Imatix Libero, Imatix SMT, Unix RCS, K-Develop (on Linux), Dia, DDD,

Lyx, MS-Project, MS-Word, Adobe Frame Maker, MS-Project, MS-Access, MS-Excel,

Rational ClearCase and ClearQuest, VxWorks Tornado.

Languages:

C, C++, Perl and Korn-shell scripting

language.

Protocols:

SS7 (particularly MTP2,

MTP3, ISUP and Call-Control : ANSI, ITU-T and TelMex/Mexico variants), ISDN,

MF-R1, MF-R2, Call-Features (CLASS and AIN based), SCTP, TCP, RUDP, M3UA.

Feasibility study for use of SIP protocol for Service Creation Server for the

ARMILLAIRE A-5000 switch. Familiar with GR-303, RBS and TR-08 standards.

PROJECT DETAILS:

January,

2002 till date

Firmware

Development for ISM (Integrated Switching Module), part of

ARMILLAIRE

A-5000, Class-5 Switch.

Employer: ARMILLAIRE Technologies Inc., MD, USA.

Role: Team Lead (Senior Member Technical Staff)

ARMILLAIRE

Technologies, Inc. develops

next-generation telecommunications solutions that combine software, hardware

and professional services to provide a flexible, scalable communications

platform for the unified networks of tomorrow. More specifically, the products are telecommunicationswitches (both Class-4 and Class-5) equipped to

provide voice and data services over a converged and/or converging network, i.e. supporting both circuit

switched and packet switched networks. Also the products focus on high performance and reliability. Higher

performance and capacities are achieved thru high port densities on the line-cards using ATM based switching, where as a mix of software and hardware

takes care of the high availability or reliability aspects. ARMIALLAIRE also

has products that help the transition

of legacy networks to next-generation networks, one such example being A-1000

and A-2000 which allow ISP s

currently connected to the legacy network (PSTN), to benefit from technologies

s.a. Internet PRI Offload, Modem

Fault Detection, International Gateway and High Availability to achieve higher cost/performance ration,

flexibility to grow at will and the ability to handle growing data-traffic

demands over the PSTN, without leading to degradation of voice-services, the

very thing that the PSTN was originally designed for. My role in this project

is to develop new features and enhance existing ones as mentioned below.

My responsibilities in the project are:

Understanding the requirements for this product based

on SRD s (focuson Call-Features, multi-ISM, and MF-R2

stack development).

Write Component

Design Documents (Detailed Design) for :

Call-Features,

Multi-ISM

Inter-shelf routing and resource-management, and

MF-R2

Telmex/Mexico specific enhancements.

Doing coding.

Writing Unit

Test Documents.

Leading a team

of four developers excluding myself, managing schedule, mentoring, work

allocation and tracking progress.

All development in this project was done

using C on VxWorks on host

for development with remote-debugging on target platform (RM-7000 RISC based).

Hardware:

ARMILLAIRE Integrated

Switching Module (firmware for both Line-Cards and CPU cards), basically an

VoIP and VoATM enabled ATM core based Media-Gateway.

Operating System: VxWorks (Tornado

Prototyper on Windows2000 for host

based

development) and VxWorks OS on target platform.

Languages:

C.

October,

2001 December, 2002

SIP

AIN Inter-working for VoIP services in ARMILLAIRE A-5000,

Class-5

Switch.

Employer: ARMILLAIRE Technologies Inc., MD, USA.

Role: Developer (as Senior Member Technical Staff)

As already

mentioned that A5000 is a Class-5 switch with an ATM core based switching. The

second phase of it s development was targeted at making it VoIP enabled, i.e.

providing Voice Services to customers using SIP and RTP over IP. This involved

both enhancements and addition to the switching hardware as well as major

enhancement of the switching and service control software. My focus was on defining

requirements in terms of Calling-Services, SIP-IN interaction for call-control

and SIP-SS7 interworking. NOTE: Due to re-organization within the company, my

activities on this project got prematurely curtailed.

My responsibilities in the project are:

Understanding the requirements for this product

and giving inputs for the enhancement SRD.

Interacting

with members in IETF SIP-IN

Interworking WG forum while

contributing towards standardization efforts.

Designing IN based services to augment SIP services by using IN CS2 call-model logic, based on some pre-standardization

work.

Studying and

understanding the existing IN CS2 implementation in A5000 switching software.

Suggesting

hardware enhancement requirements to hardware team.

Some initial coding

(until the re-organization).

All development in this project was done

using C++ and Borland VisiBroker on

Solaris 8.

Hardware:

SUN Netra and SUN SPARC

Ultra-5, PTI SS7 Card, INET Tester, ARMILLAIRE ISM Switching Hardware.

Operating System: Solaris 8.

Languages:

C++, K-shell scripts.

March,

2001 to September,2001

ARMILLAIRE

A-2000, Multi-utility Switch with ISDN Pri-Offload,

International

Gateway and some Class-4 features.

Employer: ARMILLAIRE

Technologies Inc., MD, USA.

Role: Developer (as Senior Member Technical Staff)

A-2000, like A-5000 is an ARMILLAIRE

product deployed in network carrying live customer traffic. A-2000 is the

next generation of A-1000. A-2000 builds on the features of A-1000,

strengthening it with high-availability and thus greater reliability, much more

flexibility, much more capacity, and some new features, s.a. InternationalGateway (ITU-T/ITU-T) and (ITU-T/ANSI). Also it has support for TelMexprotocolvariant of the SS7 stack. Finally, A-2000 is highly

scalable because it s switching hardware can be deployed in a highly

distributed mode. Last, but not the least, A-2000 supports Voice/Data-over-ATM

in a back-to-back configuration, leading to extremely high concentration

and support for high call volumes and data traffic. A-1000, is somewhat like a Tandemswitch that provides Internet PRIOffload, by diverting

the data-traffic (s.a. dial-up modem traffic from internet subscribers to the

ISP) away from the traditional circuit-switched network, as close as possible

to the source of the call, to the data-network. This is done by intercepting call-origination

messages and routing them thru A-1000 switch to ISP s access-servers that sit

behind ISP modem-pools connected to the switch via ISDN PRI s. A-1000 has

patented technology to detect faulty modems are remove them from list of

candidates that can accept incoming data calls. This list is dynamically

maintained and managed. The A-2000 supports all advanced features s.a. billing,

CDR generation, logging, message tracing etc. apart from normal call-processing

features necessary in a tandem type of switch. My work revolved around the

maintenance, testing and coding enhancements for the Call-Processing, ISUP

(SS7) protocol layers of the A-2000 software. Additionally, I was also

looking after the Fault-Detection and recovery logic in the switch.

My responsibilities in the project were:

Understanding the requirements for this product based

on SRD s.

Understanding

the current implementation of the high-availability protocol stack and the

product in general.

Document

test-procedures for compliance of current implementation to the requirements

specified.

Do testing of

the product for compliance.

Suggest

improvements, enhancements in the products.

Design the

enhancements, improvements and fixes to the problems identified in testing.

Coding, and

unit-testing the required changes in software.

Some development in this project was done

using C++ and VisiBroker (CORBA ORB) on

Solaris 8. Got some basic knowledge and understanding of CORBA.

Hardware:

SUN Netra and SUN SPARC

Ultra-5, PTI SS7 Card, INET Tester, ARMILLAIRE ISM Switching Hardware.

Operating System: Solaris 8.

Languages:

C, K-shell scripts.

December,

2000 to February,2001

TeleSys

i-SCP (internet SCP).

Employer: TeleSys Software,

Inc. Burlingame, CA, USA.

Role: Team Lead.

TeleSys

Software, Inc. is a leading provider of Next-Generation Signaling Platforms, Products

and Solutions. It has products ranging from Traditional Signaling platforms, to

highly scalable and highly available Next-Generation Signaling platforms, to

IP/SS7 convergence signaling solutions. It has a proven product base, deployed

in major carrier s networks s.a., AT&T WirelessServices (USA), Rogers

Cantel (Canada), Nortel Networks, Network

Telco, In-Touch, NewCore, InfoInteractive etc. It has a

part of it s development workshop in NOIDA, India, where it is known as AdTel

Software (P) Ltd.

TeleSys i-SCP is an internet

enabled and IP based Service Development Platform. It is a three tiered SCP

(Service Control Point) fabric, that is highly scalable (allowing any

number of computational entities to be added), highly reliable (allowing load-sharing

and N+M active-standby entities to be configured) platform that allows

development of a host of Number-Translation type of applications. The

basic i-SCP, has the #ESN, CCIF (Continuous Customer Information Feed)and some basic Location Based ServicesTraffic Report,

Weather Report, Location Based-800-number etc. For Voice-playback or

announcements, the system interfaces with a Convergent IVRU which may terminate

voice-trunks towards network entities s.a. MSC.

My responsibilities in the project were:

Capturing the requirements for this product, and

preparation of a project development plan.

Creating the Architecture document and Detailed Design

document.

Migrate an original AWS product of similar nature, and

scale it, to use two of TeleSys s other products, viz. MACH7 Controller

Platform, and MACH7 HA-IP/SS7 Gateway (i-STP). This included the identification

of IS-41 API requirements (IS-41 B+ and C, OriginationRequest INVOKE, RETURN

RESULT and ERROR components).

Detailed design for the ORACLE server migration to

model it s replication to fit MACH7-Controller s HA model.

Redesign and implementation of the SCP Administration

Module.

Maintaining Schedules and project tracking.

All development in this project was done

using C and C++ on Solaris 2.6, using

Oracle 7.3.2, Solstice Disk

Mirroring package, Sun Security package and Prolific JAM 7.0.2 user-interface development platform.

Hardware:

SUN Netra and SUN SPARC

Ultra-5, Convergent VRU (intel 486 based, with Convergent Voice Card).

Operating System: Solaris 2.6, SCO

Unix.

Languages:

C, C++, K-shell scripts.

Special

Software: Sun Forte/Workshop

development suite, INET Tester (for SCP tester and TCAP load generator).

October, 2000 to November, 2000

MACH7 SS7 stack port on

VoiceBoard compact-PCI SS7 card.Employer: TeleSys Software, Inc.

Burlingame, CA, USA.

Role: Developer.

The TeleSys, MACH7 SS7 stack, has

been available on ADAX and PTI SS7 cards. The goal of this

project was to port the MACH7 SS7 stack on the VoiceBoard compact-PCI SS7

card. Additionally, there was another major goal to be achieved by this

project, i.e. to make the SS7 stack completely portable at the card-interface,

i.e. make the stack plug-and-play with any card from any vendor, without

requiring the stack binary to be re-built.

My responsibilities included:

Understanding

the VoiceBoard compact-PCI SS7 card and it s various features, including

the concept of T1/E1 spans, various line-coding, framing, synchronization

formats, timing mechanisms, compact PCI features, s.a. Hot-Swap,

use of H.110 back-plane, s.t. the best use of all these features could

be made by the rest of the SS7 stack, which was eventually done. The VoiceBoard

based SS7 stack, being the most flexible and powerful MACH7 stack, s.t. it

allows any time-slot of any T1-span on any card to be mapped to any logical DS0

SS7 link, support for as much hot-swap as the card provides (but the Stack

is now completely capable of utilizing Hot-Swap, unlike with any other SS7

card).

Designing

the portable stack interface, allowing any card to be plugged in beneath the

SS7 stack which would permit very quick new-card introduction, and no changes

on the SS7 stack side.

Implementation

of the design.

Testing of

the card and the stack against the INET MTP2 Conformance and Validation

Tester, and testing MTP3, SCCP, TCAP and ISUP for complete functionality.

Documentation

of the portable API and it s architecture. Also documented the recommended

road-map for future card portation work.

All development in this project was done

in C on SUN Solaris 2.6, and

some attempts were also made to port this to VxWorks, which were

eventually aborted due to lack of time and interest of the marketing division.

Hardware: SUN Compact PCI platform CP-440, SUN SPARC Ultra-5, VoiceBoard

compact PCI (quad-port T1) SS7

card.

Operating System: Solaris 2.6, VxWorks.

Languages:

C

Special

Software: Sun

Forte/Workshop, INET tester.

June, 2000 to September, 2000

TeleSys Wireless Office

Service Controller Gateway.

Employer:TeleSys

Software, Inc.

Role: Developer

Wireless Office Service, is a novel

technology pioneered by AT&T Wireless Services for mid-to-large

sized businesses, where all employees with mobile (cellular) phones, have the

ability to originate or terminate calls on their mobile handsets, without

charge to their air-time, as long as they are in the office building (or as per

the standards, within the campus ). The Wireless Office Controller is like a

small MSC, which interacts with the office PBX thru a DSL

line and V.35 lines, which in turn connects to a mini Base-Station

Transceiver (for the air-interface, IS-136). The mini-MSC, actually called

the Wireless Office Service Controller (or WOSC) as per the standards, utilizes

the services of a WOSC-Gateway, which in essence is an SS7-over-IP

gateway, that permits the WOSC s to use SS7 signaling without requiring them to

terminate SS7 links. The communication between WOSC s and the WOSC-gateways is

a proprietary (AWS s) yet secure (due to use of SSL communication and

certificate exchange) protocol. The WOSC is a specification, implemented by

several vendors including Hughes, Ericcsson, Nortel, DGMS etc. TeleSys

designed and developed first and only, highly scalable and highly available,

software only solution for the WOSC-Gateway (i.e. the SS7-over-IP gateway). The

WOSC-Gateway utilizes the MTP3 (and some amount of SCCP, for GTT

alone), in a distributed and high-availability mode to service the WOSC s. It

has the ability to support upto 250 simultaneous WOSC s without message loss,

and fail over across boxes incase of problem in one of the participating

gateway processor boxes. In the more recent implementation the WOSC-Gateway has

the ability to use M3UA/SCTP for talking to WOSC s (i.e. if they are

modified to conform to the open standards based M3UA/SCTP interface).

My responsibilities included:

Modification

of the SIA (equivalent to M3UA as per SIGTRAN standards), WAN (for transparent

IPC across hosts), XNTP (for clock synchronization with a processing cluster of

Workstations), HAD (for monitoring health of the gateway system in terms of

process sanity, process life, processing load thresholds etc.) for support of

multiple hosts.

Maintenance

including several bug-fixes in the above mentioned processes.

Algorithmic

modification for support of greater number of WOSC s.

Provide

support to the AWS Lab personnel during the FOA (AWS First Office

Availability) phase and during the GA (AWS General Availability) phase.

Writing

several batch-processing shell-scripts for migration of provisioned data from

old WOSC-Gateway system to TeleSys s WOSC Gateway system.

Documenting

and explaining, several previously unexplained and undocumented processes.

Fixed

several Web-based GUI related bugs.

All development in this project

was done using C on Solaris 2.6.

Hardware: Sun SPARC Ultra-5, Sun

Netra.

Operating

System: Solaris 2.6

Languages: C, Korn-shell scripting, Perl-scripting,

CGI/HTML.

Special

Software: Sun

Forte/Workshop, Netscape Enterprise Server (now iPlanet), SSL library, Imatix

Libero FSM generator.

March, 2000 to May, 2000

SCTP (Signaling Control

Transport Protocol)

Employer: AdTel Software

(P) Ltd., NOIDA, India.Role: Developer

This goal of this project was to

implement a robust (highly available as per AdTel/TeleSys HA framework), and

high performance SCTP implementation. The, then current version of SCTP

internet draft (version 7) was picked and implemented. SCTP is now an RFC.

SCTP was formalized by the ITEFSIGTRAN (Signaling Transport

Working Group) for Reliable Transport of Signaling information over IP

networks. SCTP takes away the ills of TCP, like head-of-line blocking,

lack of fine-grain control over connection and disconnection timers,

lack of support for multi-homed hosts, no choice of alternate links

on link failure, no implicit message boundary demarcation mechanism

etc. SCTP cures all these ills by introducing the concept of multiple

streams within an SCTP association (much like the TCP client-server

connection, the only difference being SCTP treats both endpoints as peer s and

not client/server), which removes head-of-line blocking, gives finer control on

times which allow each individual association to be managed separately. SCTP

also provides support for multi-homed hosts, and allows application

data/messages to be sent over alternate paths when a path failure occurs. SCTP

supports heart-beating of end-points to be able to terminate

associations more gracefully, and come to know of remote site

disconnect more quickly. Additionally SCTP has some strong anti-DoS (Denial of

Service) attack mechanisms, like immune to blind-masquerade attacks.

Our implementation was an Object-Oriented implementation, which was also

highly portable as it was built using ACE (Adaptive Communication

Environment). Also, our implementation extends the standard SCTP, by itself

being a high-availability implementation. It supports two instances of SCTP

running on separate hosts, which keep each other synchronized about the various

associations (TCB s) and other internal state information.

My responsibilities during this project,

included design and development of the CRC-32 module, the Association-Management

module, the HA module. This was designed and developed by a team of

three developers including myself. All development in this project was done using, C and C++ on Solaris 2.6 and RedHat Linux 6.1.

Hardware: Sun SPARC Ultra-5 and Intel based PC s.

Operating

System:

Contact this candidate