Behind the Curtain at TCG

More on Asterisk and IntuitiveVoice Evolution

Want to change the conference line access number in Asterisk/Intuitive Voice Evolution? It's not all that easy if you don't want the conference line to be something not in the 14000-15000 range.

We like to have a nice long conference line access code, like 4859282. It decreases the probability that someone will guess it and use our conference line (not that that's all that likely anymore, what with freeconferencecall.com and all that, but still it would annoy me).  So how do we do that?

We have to mess with the database again. Going back to my blog posting in March 2008, we learn the steps to get into the database. Do the following:

1. SSH into the box (got the root password from Intuitive Voice).
2. Become root, if you're not already.
3. /etc/init.d/mysqld stop (we need to get into the database without a password)
4. mysqld_safe --skip-grant-tables & (this will restart the database but make it so passwords are not required. Yay security!)
5. mysql asterisk_config (going into the correct database)
6. Find rows of ast_config where var_val contains the conference line number Evolution created for you. I use this SQL: select * from ast_config where var_val like "%14000%"; (or whatever the conference line I want to change is.
7. Using the "id" tag as the unique identifier (it is unique), change all the var_val lines that reference that conference line. SQL for us:
   
   • update ast_config set var_val="4859282,10,Goto(20)" where id=140624;
   • update ast_config set var_val="4859282,9,Macro(pause)" where id=140623;
   • update ast_config set var_val="4859282,7,Macro(callrecord,${CUT(CHANNEL,,1):4})" where id=140621;
   • update ast_config set var_val="4859282,8,Set(__MONITOR_FILENAME=/var/www/html/monitor/${UNIQUEID})" where id=140622;
   • update ast_config set var_val="4859282,6,Macro(reporting)" where id=140620;
   • update ast_config set var_val="4859282,5,Set(__STATUS=ANSWERED)" where id=140619;
   • update ast_config set var_val="4859282,4,Set(__DESTINATION=)" where id=140618 ;
   • update ast_config set var_val="4859282,Conf5,0" where id=140613;
   • update ast_config set var_val="4859282,1,2" where id=140614;
   • update ast_config set var_val="4859282,1,Set(__DIALED=${EXTEN})" where id=140615;
   • update ast_config set var_val="4859282,2,Set(__TYPE=INTERNAL)" where id=140616;
   • update ast_config set var_val="4859282,3,Set(__SOURCE=${CUT(CHANNEL,,1):4})" where id=140617;
8. /etc/init.d/mysqld stop (stop the unprotected mysql instance)
9. /etc/init.d/mysqld start (start the good one)
10. Go into the web interface and restart the PBX (not necessary to reboot)
11. Give it a shot.

NGMA lunch canceled

The NGMA training lunch at which Dominic Sale, the OMB GMLOB Portfolio Manager, was scheduled to speak has been canceled. Apparently things are so hectic at OMB that it's proven impossible to schedule any appropriate time.

The next NGMA lunch will be on June 24th, when Elizabeth Russell will present “Become a More Effective Speaker: How to Tell Your Story with Confidence & Get Results”. See you there!

NGP Meeting - June 9th - be there!

The agenda for the NGP's June 9th meeting has been announced. Register at , and join us at 1.30pm at the Department of Education at 550 12th Street SW, Washington, DC, or via webcast at http://tcg.acrobat.com/thengp.

• GAO Study of Grants.gov - Jennifer Ashford and Jacqueline Nowicki, GAO
  
• Grants.gov Update - Mike Pellegrino and Vince Sprouls, Grants.gov
  
• Grants.gov Pilot with FedBizOpps with Interior and Energy - Richard Clark, GSA
  
• NGMA Conference Highlights - Katie Hermosilla, Booz Allen Hamilton
  
• Charitable Giving Info Now Online at the Texas Attorney General - Bill Levis, Urban Institute; Denise Francis, State of Texas Governor's Office; Linda Lampkin, Economic Research Institute
  

As a reminder: The following NGP meeting will be October 20 or 27th, so be sure to keep those dates aside.

MAX Federal Community on FederalNewsRadio

FederalNewsRadio has a story and a couple of interviews about the MAX Federal Community this week. (Note: TCG supports this system on behalf of OMB.) The Community is powering a lot of inter-agency collaboration across government. FederalNewsRadio interviewed Sandi McCabe at the Department of Education and our colleague Shahid Shah of Netspective Communications about how the system works and the benefits it provides.

NGMA lunch to be rescheduled

If you were planning on attending the NGMA training luncheon tomorrow, featuring Dominic Sale of OMB talking about "The Use of Technology in Managing Grants: Guidance and Direction - Recovery.gov and GMLOB", then you can stop right now because it's being rescheduled. The new date is TBA; we'll post it here when we know. And keep an eye on the Grants Management Events Calendar for all the dates of upcoming meetings, lunches, and training that you'll want to attend.

NITRC discusses keys to success

Yesterday the NITRC program participated in a panel discussion among the top five 2009 Excellence.Gov Awards. Government Computer News wrote up a nice little story about it, here.

Grants.gov report from GAO cites concerns

Last week the GAO released a report (GAO-09-590R) on the status of Grants.gov, in response to enquiries from Congressmen Voinovich, Towns, Lynch, and Davis. The report echoes many of the concerns expressed by OMB several weeks ago but GAO goes a few steps forward with regard to concerns about confusing grant deadlines, with these recommendations (as stated by FCW):

• To the extent permissible by law, applications received at any point on the stated grant opportunity closing date should be considered timely.
• Agencies must notify an applicant when an application submission has been received and if the application has been deemed late. An applicant that submits electronically (including by e-mail or fax) should receive automatic confirmation with a date and time stamp.
• Applicants whose applications have been deemed late should be given an opportunity to provide supporting documentation to demonstrate that they attempted to submit an application on time (such as e-mail confirmations, electronic time stamps, U.S. Postal Service or commercial postmarks, etc.)

Later this week, I hope to post some thoughts about where Grants.gov should go in the future, as sticking with the current system and situation is untenable.

Federal grants management systems landscape

Last week I gave the presentation below at the Compusearch PRISM Educational Conference. On the panel with me were Katie Hermosilla (Booz Allen Hamilton) and Chae Shim and Tracy Mosson (Compusearch). Katie talked about the policy side of the grants management world and I summarized the systems side, at a very high level. It was a very interesting discussion, with some great questions from the audience, so I thought others may be interested.

Federal Grants Management Systems Landscape, April 30, 2009

View more presentations from dgcassidy.

Grants.gov gets applause for recent build

Monday was the deadline for a large grant opportunity, and Grants.gov performed very well! Whatever measures the team has taken seems to have really helped. As one submitter from a university wrote on the Grants.gov system-to-system mailing list:

"Like most folks, we went into yesterday's Challenge grant deadline with a lot of trepidation. We don't know what all the techical team at Grants.gov changed in the last build. But what a difference that build made! ... We appreciate all the hard work by the Grants.gov team that made this possible."

This was met with applause from others, too. Kudos to the Grants.gov team!

GDIT gets Grants.gov sole source contract extension

Grants.gov has determined (through a very rigorous process) that only General Dynamics IT, their current contractor, can help them through this frantic period of activity and meet the goals of the Recovery Act, and has awarded them a contract extension, as this announcement shows. One of the announcement attachments is a "Justification for Other Than Full and Open Competition", which is a standard analysis that procurement offices produce to justify why "Only one responsible source and no other supplies or services will satisfy agency requirements." The announcement reads, in part:

"The technological augmentation of Grants.gov shall be limited to strengthening Grants.gov community applicant and Agency log-on, registration and application processing. The technology augmentation solution (solution) must be developed and implemented to ensure integration into the existing Grants.gov infrastructure.

"The Contractor shall supply the expertise, labor, equipment, and services necessary to implement the augmentation and continued day-to-day operations, maintenance, and support of Grants.gov. This includes file servers, storage devices, load balancing and network equipment, additional cage space, racks and hosting services (power, connectivity, monitoring)."

It also states:

"The current System Integrator, GDIT designed and operates the Grants.gov system and is the only entity with the in-depth knowledge of the current system. GDIT is also currently the only company that is familiar with the deficiencies of the current design and is best able to engineer and solution taking into account all relevant information concerning the system.

"It could take another contractor as much as 60-90 days to learn the basic architecture, design, and coding of the system and then additional time to design and implement a technical solution, which presents a high level of risk in being able to successfully meet OMB instructions to immediately improve the system and a substantial duplication of costs."

I don't think anyone who knows anything about Grants.gov could reasonably argue with this statement.

There is also a statement about some market research that was conducted:

"Market research was conducted to determine if any alternative options were available to develop and implement a cost-effective solution in the required time frame of the OMB memorandum to support Recovery Act processing. Grants.gov Program Management Office (PMO) and Health and Human Services (HHS) staff investigated the possibility of using a small business service provider that could be contracted with in order to determine the feasibility of having another source perform this work. It was determined that although other solution providers could eventually learn the system and do the requested work many of these firms did not have the in-house expertise and requisite skills to do all of the work and thus would have to subcontract for other services and that the time frames to obtain the resources, go through the steep learning curve and then design the solution would exceed the time available to improve the system, providing a high level of risk in successfully implementing a timely and cost-effective solution. This time frame also did not accommodate the amount of time it would take to solicit and contract for the services, which would also increase the potential time for a solution implementation. Also considered was contracting with a larger company to obtain these services, but the acquisition and learning curve times, along with the associated costs, would still be a factor and thus make this option a high level of risk in successfully implementing a timely and cost-effective solution. All of these options will also result in a substantial duplication of costs. Based on the above, GDIT is the only source available to perform the work without substantial duplication of costs to the government and without unacceptable delays in fulfilling the agency's requirement."

I think this was inevitable, given the state of things. What is surprising, though, is that the Grants.gov PMO has investigated alternatives. Certainly there was a "cloud computing" RFI last year but I don't recall seeing anything along the lines described above.

Regardless, I hope the measures that GDIT is being contracted to take will get Grants.gov through this frantic period and position the platform for future significant improvements that address "the deficiencies of the current design," as they're termed in the announcement.