While the database issues mentioned previously are continuing, with reports that the Silver Spring staff have been extremely busy today trying to work around unspecified problems performing trips, DC ParaTransit Info is wondering what could cause an IVR reminder call this evening (made to customers the night before to remind them of their upcoming trips) to abort at the beginning of the message, stating:
A GPS Error has occurred
We’ve asked MetroAccess for more information, but we’re curious if this is related to the database issues, and more importantly – if this is indicative of a problem with IVR (and presumably, Trapeze) not being able to access/reference GPS data, what effect is this having on provisioning of trips?
