--> At CallCenterOps.com we’re dedicated to providing information about operations management to those involved in real-time customer service via call centers.
Learn how to advertise on this site.
CCOps Home  |  Forum Home  |  Jobs Board  |  Library  |  Operations  |  Resources  |  In The News  |  Site Map

Go Back   CallCenterOps Forum > Technology Discussion
FAQ Social Groups Calendar Search Today's Posts Mark Forums Read

Technology Discussion The CallCenterOps Technology Forum focuses on the technologies that make call centers work. (No advertising is accepted - posts will be removed.)

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 04-11-2005, 12:09 PM
Member
 
Join Date: Apr 2005
Posts: 0
Anyone familliar with NCT or Network Call Redirect?

This may be the wrong forum to post this in, but here goes...

We are trying to implement MCI's NCT (Network Call Transfer) feature on our trunk group. The switch on both coasts is an Avaya G3r Version 8. The way that it works is this...

A customer calls into the 866 number, and hits the vector. We are using BSR between 2 different service centers, and the switch looks for a better EWT for the customer. At that point the call is sent to the center with the best EWT. The switch sends MCI the request for NCT, and MCI takes the call up in the cloud, and transfers it to the other center. When the transfer is complete, the originating trunks are dropped. Those trunks being the incoming call from the customer, and the BSR call to the other service center. Currently when a call is sent via BSR, there are 3 trunks tied up, and with NCT there will only be one.

Here is how it's setup in the switch...

The T1's have to be converted to NFAS because the incoming, and outgoing trunks have to utilize the same D channel. The trunk group needs the following changes...

2 way direction
Supplementary Service Protocol set to g
Disconnect Supervision In and Out both set to yes
Network Call Redirection set to ANSI-Transfer

Next the Best service Routing needs to have the following...

The 9 is removed from the Interflow VDN number.
The Net Redirect is set to yes.

That's pretty much all the translation changes. Now here's the problem...

I have a switch in Norfolk, VA. and a switch in San Diego, CA. Both switches are identical release, and have identical programming. NCT works from Norfolk to SD, but not the other way around. The call will transfer from SD, but the original trunks will not drop like they do from Norfolk.

The following text is from an ISDN Protocol Analyzer. The first shows the Norfolk call record, and the second shows the SD call record. The text in red is the request from the PBX to MCI to invoke NCT. The first FACILITY request being the PBX requesting, and the second is MCI acknowledging the request.

As you can see in the SD call record, there is no FACILITY request from the PBX, ,and subsequently there is no acknowledgment from MCI.

So the million dollar question would be WHY?? What switch translation would control that request that is sent to MCI?

NORFOLK

01:26:11.183 SD1 I FROM 28198 SETUP From:757963xxxx To:866248xxxx
01:26:11.218 RD1 I TO 28198 CALL_PROCEEDING
01:26:11.228 RD1 I TO 28198 PROGRESS
01:26:11.230 RD1 I TO 28198 ALERTING
01:26:11.233 RD1 I TO 28198 CONNECT
01:26:11.369 SD1 I FROM 28198 CONNECT_ACK

01:27:28.567 RD1 I FROM 19604 SETUP To:1619817xxxx
01:27:28.615 SD1 I TO 19604 STATUS InvalidInfoElementsContents
01:27:28.719 SD1 I TO 19604 STATUS RequestedFacilitynotSubscribed
01:27:28.871 SD1 I TO 19604 CALL_PROCEEDING
01:27:29.877 SD1 I TO 19604 PROGRESS
01:27:29.901 SD1 I TO 19604 CONNECT
01:27:29.936 RD1 I FROM 19604 CONNECT_ACK
01:27:29.943 RD1 I FROM 19604 FACILITY
01:27:30.295 SD1 I TO 19604 FACILITY
01:27:30.540 SD1 I FROM 28198 DISCONNECT NormalCallClearing
01:27:30.543 SD1 I TO 19604 DISCONNECT NormalCallClearing
01:27:30.576 RD1 I TO 28198 RELEASE
01:27:30.582 RD1 I FROM 19604 RELEASE
01:27:30.628 SD1 I FROM 28198 RELEASE_COMPLETE
01:27:30.638 SD1 I TO 19604 RELEASE_COMPLETE


SAN DIEGO


01:00:38.272 SD2 I FROM 1720 SETUP From:757963xxxx To:866248xxxx
01:00:38.314 RD2 I TO 1720 CALL_PROCEEDING
01:00:38.324 RD2 I TO 1720 PROGRESS
01:00:38.328 RD2 I TO 1720 ALERTING
01:00:38.330 RD2 I TO 1720 CONNECT
01:00:38.391 SD2 I FROM 1720 CONNECT_ACK
01:01:16.584 SD2 I FROM 1717 DISCONNECT NormalCallClearing
01:01:16.610 RD2 I TO 1717 RELEASE
01:01:16.654 SD2 I FROM 1717 RELEASE_COMPLETE
01:01:23.974 RD2 I FROM 25934 SETUP To:1757963xxxx
01:01:24.026 SD2 I TO 25934 STATUS InvalidInfoElementsContents
01:01:24.054 SD2 I TO 25934 STATUS RequestedFacilitynotSubscribed
01:01:24.242 SD2 I TO 25934 CALL_PROCEEDING
01:01:25.759 SD2 I TO 25934 PROGRESS
01:01:26.104 SD2 I TO 25934 CONNECT
01:01:26.144 RD2 I FROM 25934 CONNECT_ACK
01:02:21.972 RD1 I FROM 0 CONNECT_ACK
01:02:22.022 SD1 I TO 0 CONNECT
01:02:50.996 SD2 I FROM 1719 DISCONNECT NormalCallClearing
01:02:51.036 RD2 I TO 1719 RELEASE
01:02:51.084 SD2 I FROM 1719 RELEASE_COMPLETE

Any help would be greatly appreciated.

Thank you in advance.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -4. The time now is 01:41 AM.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2