Wrong Caller ID
-
@krzykat said in Wrong Caller ID:
@JasGot What are you referencing? The DIP at Skyetel or ?
For the Caller ID Editor.
Without the "1" They accept it, tell you it has processed, then do nothing with it......
With the "1", they accept it, tell you it has processed, then they actually submit it to the Caller ID database in the sky (or wherever it is)
-
@JasGot said in Wrong Caller ID:
@krzykat said in Wrong Caller ID:
@JasGot What are you referencing? The DIP at Skyetel or ?
For the Caller ID Editor.
Without the "1" They accept it, tell you it has processed, then do nothing with it......
With the "1", they accept it, tell you it has processed, then they actually submit it to the Caller ID database in the sky (or wherever it is)
This might be a bug. I’ll have it checked out.
-
@Skyetel said in Wrong Caller ID:
@JasGot said in Wrong Caller ID:
@krzykat said in Wrong Caller ID:
@JasGot What are you referencing? The DIP at Skyetel or ?
For the Caller ID Editor.
Without the "1" They accept it, tell you it has processed, then do nothing with it......
With the "1", they accept it, tell you it has processed, then they actually submit it to the Caller ID database in the sky (or wherever it is)
This might be a bug. I’ll have it checked out.
Or, and better, do validation on the submission and require 11 digits! (Always better to validate user input....)
-
@JasGot said in Wrong Caller ID:
@Skyetel said in Wrong Caller ID:
@JasGot said in Wrong Caller ID:
@krzykat said in Wrong Caller ID:
@JasGot What are you referencing? The DIP at Skyetel or ?
For the Caller ID Editor.
Without the "1" They accept it, tell you it has processed, then do nothing with it......
With the "1", they accept it, tell you it has processed, then they actually submit it to the Caller ID database in the sky (or wherever it is)
This might be a bug. I’ll have it checked out.
Or, and better, do validation on the submission and require 11 digits! (Always better to validate user input....)
We cant validate a submission like we can elsewhere because the CID updated is not a real time process. That’s why (as Jared noted) it can take a couple of days for it to update. These updates sit in a queue and get updated when the CID gods are in a good mood.
We tweaked our UI to allow 10 digit entries based on feedback here and I suspect that when we did that, the thing that converts the entry into E.164 got mixed up. The CID stuff is crazy arcane...
CID entries can also get rejected If the LIDB thinks their data is more accurate than ours. We don’t get any feedback about that (the log will just show it as rejected, often without a reason, and we have to open a ticket to dispute the rejection.)
And of course, as Jared mentioned, if the party you are calling caches their records for a long time (or never updates them - something that’s super common) then there’s nothing we can do.
So yea, that tool hides a lot and generates a lot of support tickets for us. We try to make what is an absurdly complicated process easy, but by doing so we’re opening the door to bugs like this. Welcome to telecom! lol
-
@Skyetel said in Wrong Caller ID:
We tweaked our UI to allow 10 digit entries based on feedback here
#whistlesnonchalantly
-
@Skyetel said in Wrong Caller ID:
We cant validate a submission like we can elsewhere because the CID updated is not a real time process.
I was talking about the submission form at Skyetel. If you know it's best to get an 11 digit field value for the number, then validate it at the submission form. It would be silly to validate when you submit it to the CID gods when you already know what you should be getting, (even before submitting up stream).
-
@JasGot Ah, yea, that’s what I’m going to check out tomorrow
-
@JasGot said in Wrong Caller ID:
@krzykat said in Wrong Caller ID:
@JasGot What are you referencing? The DIP at Skyetel or ?
For the Caller ID Editor.
Without the "1" They accept it, tell you it has processed, then do nothing with it......
With the "1", they accept it, tell you it has processed, then they actually submit it to the Caller ID database in the sky (or wherever it is)
Looks like this isn't a bug, but without more details we can't troubleshoot further.
Would you please open a support ticket so we can ask for PII?
-
@Skyetel said in Wrong Caller ID:
Would you please open a support ticket so we can ask for PII?
Done:
#82411 -
@JasGot said in Wrong Caller ID:
@Skyetel said in Wrong Caller ID:
Would you please open a support ticket so we can ask for PII?
Done:
#82411Great, thanks. We've already replied
-
I wanted to make sure I followed up and let you all know that we confirmed that there was no bug. There was a propagation delay that impacted @JasGot which caused it to appear that the 10 digit vs 11 digit input mattered.
