Wholesale: Products & Services

Archived System CR SCR011413-1 Detail

Proposed solution: Request to CenturyLink is to exclude failed transactions when performing the check for trackID.

Status History

Project Meetings

6/19/13 System Monthly Meeting Mark Coyne – CenturyLink relayed this is an AT&T CR. The Final technical specifications associated with MTG Release 1.5 were sent on May 16, 2013. The release will be effective June 30, 2013 and we will look at this in the July CMP meeting.

4/17/13 System Monthly Meeting Mark Coyne – CenturyLink said the CR was posted separately to the calendar with the planned solution and the AT&T responses to the outstanding questions from CenturyLink. Mark said the system release notice will go out on April 18 for a targeted release of June 30, 2013.

3/20/13 System Monthly Meeting Mark Coyne – CenturyLink said this CR has been Accepted and that CenturyLink has provided a high level solution to AT&T and that they are in the process of reviewing the response. Once a response from AT&T is received, CenturyLink will begin to develop a level of effort.

2/20/13 System Monthly Meeting Mark Coyne – CenturyLink said these three CRs were presented by AT&T last month and are under evaluation.

1/21/13 Clarification Meeting Attendees: Susan Lorence – CenturyLink, Mark Van de Water – AT&T, Doris Luttrell – CenturyLink, Lori Burchett – CenturyLink, Cecilia Tank – CenturyLink, Kyle Kirves – CenturyLink, John Hansen – CenturyLink, Mark Coyne – CenturyLink, Carrie Bousfield – CenturyLink, Vinesh Vijayan Leela – CenturyLink

Susan Lorence – CenturyLink stated the purpose of the call and asked Mark Van de Water to provide a brief description of SCR011413-1 -TrackID transactions associated with MTG.

Mark Van de Water – AT&T defined the issue that had come to light during testing of the MTG platform and the problems around the TrackID field. He asked that the TrackID not be captured.

Carrie Bousfield – CenturyLink asked if the issue was only for Create and if they were planning to use the TrackID for MLT transactions as well.

Mark Van de Water – AT&T stated that he felt it was only for Create and that he was unsure and confirmed that it was for POTS only. He asked it CEMR supported MLT for POTS or only for T1

Carrie Bousfield – CenturyLink stated that she believed that was correct.

Mark Van de Water – AT&T asked if there would be a TrackID for a straight MLT transaction.

Susan Lorence – CenturyLink stated that an issue that had been brought up on the monthly CMP call was from Bonnie Johnson – Minnesota Department of Commerce had asked if MEDIACC had the TrackID functionality and that it did not.

Mark Van de Water – AT&T stated that he felt it was new to Legacy Qwest and that Legacy CenturyLink had the field but that it was ignored. He stated that at this time, the request was only for Create functions.

Carrie Bousfield – CenturyLink stated that she was asking so that CenturyLink could address all functionality at the same time.

Mark Van de Water – AT&T asked Vinesh is MTG allowed MLT testing.

Vinesh Vijayan Leela – CenturyLink responded with yes and confirmed that a TrackID was associated with the transaction.

Mark Van de Water – AT&T asked if the same scenario would apply to the MLT transaction. Vinesh Vijayan Leela – CenturyLink agreed.

Mark Van de Water – AT&T stated that the MLT transaction was not as detailed as the Create scenario and therefore was not as critical and that this Change Request should be considered for Create only.

1/16/13 Systems Monthly Meeting Mark Van de Water - AT&T said that AT&T is currently testing MTG and found a situation that caused them to generate this CR. Mark presented the CR and asked if there were any questions.

Bonnie Johnson – Minnesota Dept of Commerce asked if this should be considered an error vs. new functionality.

Mark Van de Water - AT&T said that CenturyLink is the only company that has the TrackID restriction. He said neither Legacy CenturyLink nor does Verizon have it; there is a TrackID but not the same edits. Mark said that once the AT&T user corrects the error, they must submit an entirely new ticket with a new TrackID.

Bonnie Johnson – Minnesota Dept of Commerce said her question was for CenturyLink and asked if this functionality was in MEDIACC.

Carrie Bousfield – CenturyLink said she did not believe TrackID was used in MEDIACC but would check.

Tracy Strombotne – CenturyLink said we would research the question and provide a response back.

Susan Lorence – CenturyLink said there will be a clarification call for the three CRs on January 18 and we would try to have the question answered for that call.

CenturyLink Response

CR solution and questions sent to AT&T from CenturyLink on March 14, 2013

Solution for Duplicate Track Id For Ticket Create scenario: a) AT&T sending duplicate ticket create request to MTG, by re-using the same TrackID which has sent in initial create request – *Issue found in MTG end with 1st create request. MTG will relax ‘Duplicate TrackId found’ scenario and allow the duplicate ticket create with same trackID to MTG downstream system. b) AT&T send duplicate create request to MTG, a trackID already exist and TicketId is created successfully in MTG – *Issue found in AT&T side, B2bi or other interfacing system did not received response from MTG

MTG will relax ‘Duplicate TrackId found’ and MTG will send async response with exception like ‘This TrackId already been used for Ticket ID’ to AT&T. AT&T can use the same TrackId and TicketID and send subsequent transaction (Update, Retrieve, Modify, Cancel, Close out) request to MTG based on the current ticket status in MTG.

Sample response for b) from MTG to AT&T will be CTG-5100 TrackID already been used for TroubleReportId: CTL12345

For MLT (Mechanized Loop Testing) scenario: a) MTG system failed to process MLT in 1st request sent by AT&T to MTG then – On subsequent request from AT&T, MTG will relax ‘Duplicate TrackID exist’ scenario and allow subsequent MLT transaction from AT&T by re-using the same TrackID.

b) If MTG processed MLT transaction and sent valid ( for eg: a ticket already in Progress ) exception back to AT&T then – AT&T will have to use new TrackID and communicate with MTG for subsequent MLT transaction for same TN. MTG can only send the same error message like “TrackID already in use”.

c) AT&T failure – MTG sent good response to AT&T and they didn’t receive the response from MTG, then AT&T will receive ‘TrackID already in use’ and AT&T has to send a new request with new TrackID for the same TN. If there is an valid error response from MTG, ( for eg: a ticket already in Progress ) to AT&T, then AT&T should not re-use the same TrackID to send the MLT request. AT&T should wait for the ticket to be closed, and create a new TrackID to test MLT for the same TN.

NOTE: RESPONSES REC’D FROM AT&T ON APRIL 4 ARE IN RED/BOLD

AT&T needs to confirm the items below – a) Will AT&T be able to send unique TrackID ( prefix with ATT ) so MTG can understand that the trackID is submitted by AT&T. AT&T RESPONSE – B2Bi gateway team has agreed to prepend ATT to the track id sent from the back end systems in the outbound transactions to QWEST and would strip off this prefix in the inbound transactions from QWEST before passing the response back to the back end systems. No change to the back end systems. b) AT&T should not re-use TrackID for different TNs/ Circuits. AT&T RESPONSE – Agreed. c) AT&T cannot re-use TrackID after a month from the time it is been generated. AT&T RESPONSE – Agreed since the trouble is expected to be resolved in a week or two and the ticket would be closed. d) AT&T should not send same trackId multiple times (example: 3 weeks after the first attempt. We have seen this scenario in Test environment.) AT&T RESPONSE - Agreed since the trouble is expected to be resolved in a week or two and the ticket would be closed. Agreed since the trouble is expected to be resolved in a week or two and the ticket would be closed. AT&T is allowed to send the same TrackID to QWEST for ticket create within two weeks of the first attempt if AT&T did not receive the response for the first attempt.