Does anyone know if the bug with SQL and inbound routes has now been sorted?
I ask because I’m STILL having issues with superfecta schemes not being followed for certain caller ID patterns for which I have specific inbound routes setup.
I have a caller ID route where DID is set and CID is any and superfecta scheme is default
I have another where DID is set CID is _01302XXXXXX (local area code) and has its own superfecta scheme
But despite the fact that superfecta scheme IS referenced in the log ‘darlnumbers’, the call ends up with a CID as if it was set by the default superfecta scheme?