Solved I am getting 12294 - calls not going out on a lot of calls recently

Status
Not open for further replies.

TownTech

Bronze Partner
Joined
Feb 14, 2023
Messages
112
Reaction score
14
I am getting 12294 - calls not going out on a lot of calls recently
Call or Registration to +1xxxxxxxxxx@(Ln.10001@Voxtelesys) has failed. sip:1.12.123.11:5060;lr replied: Decline (603)
Anyone know what's wrong? No changes on our end.
 
Hi @TownTech ,
603 Decline means the callee or the callee's carrier is rejecting the call. First thing you will want to do is register your numbers with https://freecallerregistry.com/fcr/, this will whitelist your numbers with the mobile operators (and some cable carriers) spam filters.
 
  • Like
Reactions: Nathan@Voxtelesys
Anyone else sure about the above call registry website? Seems a little suspicious
 
It could be that your number is simply flagged as SPAM, somewhere. If you are in the habit of making calls that might be considered as such, then there may not be a lot you can do. Many providers offer their customers a relatively easy way to flag a call and block it. It may not even mean that they have any idea of who is calling, just that they don't recognize the number and may have had more that one call from that number.
I know a lot of people that will not answer the phone if they don't recognize the number.
 
  • Like
Reactions: Kevin@voxtelesys
Anyone else sure about the above call registry website? Seems a little suspicious
It is indeed a legitimate link, your calls going out over Voxtelesys are signed with Stir/Shaken certificates, but even with an A attestation mobile and some cable providers rely on their SPAM vendors to filter calls. We do not know the exact metrics on how a number is filtered or flagged, but we can assume it has to do with call history, consumer feedback, answer ratio, and call volume increase.

You register with https://freecallerregistry.com/fcr/ which will take care of Verizon, Tmobile, and ATT. Or if you want links to each provider directly:
ATT: https://hiyahelp.zendesk.com/hc/en-us/p/request_hub
Verizon: https://www.voicespamfeedback.com/vsf/
T-Mobile: https://callreporting.t-mobile.com/ (or use https://portal.firstorion.com/app/landing#/signup)
 
Also do you have a ticket open, when can check the call records and do a check on the terminating numbers to verify the callee carrier.
 
  • Like
Reactions: Kevin@voxtelesys
Also do you have a ticket open, when can check the call records and do a check on the terminating numbers to verify the callee carrier.
Thank you. I get nervous when websites ask for details like that, but I guess it is necessary for this issue.
We registered on the website with the customers email address, business number & info.
I will submit a ticket also through Voxtelsys portal. Thanks
 
Thank you. I get nervous when websites ask for details like that, but I guess it is necessary for this issue.
We registered on the website with the customers email address, business number & info.
I will submit a ticket also through Voxtelsys portal. Thanks
Unfortunately with all the spam calls these days those vendors require that information to properly vet the number, they will even test inbound call the number to verify the business in certain scenarios. HIYA and First Orion both have portals the customers can create free accounts with to upload and manage the numbers in a better format than submitting with the free call registry link.

Feel free to DM me the ticket number
 
I believe there may be something larger going on as we are having the exact same issue with Flowroute. I've went the route of registering with the registries but 7 days later, I'm not seeing any change. A TMobile number that I was able to call out to just last night, I am unable to call this morning.
 
I believe there may be something larger going on as we are having the exact same issue with Flowroute. I've went the route of registering with the registries but 7 days later, I'm not seeing any change. A TMobile number that I was able to call out to just last night, I am unable to call this morning.
I cannot comment on Flow route but the example shared here was blocked by a term carrier or device. Registering with the links is the first step. You will need to open a ticket with flowroute.
 
I cannot comment on Flow route but the example shared here was blocked by a term carrier or device. Registering with the links is the first step. You will need to open a ticket with flowroute.
Thanks for the reply, and I've spoken to them about this issue. They suggested the registries as I said, which I completed about a week ago. I spoke with them again this morning and they didn't have much else to say other than possibly change the caller ID. Any suggestions on steps after that?
 
Thanks for the reply, and I've spoken to them about this issue. They suggested the registries as I said, which I completed about a week ago. I spoke with them again this morning and they didn't have much else to say other than possibly change the caller ID. Any suggestions on steps after that?
It is hard to say. Registries only matter if you see a 6xx code this means it was blocked in some fashion. If you are having call fail and the code is not a 6xx then it is a whole different scenario.
 
It is hard to say. Registries only matter if you see a 6xx code this means it was blocked in some fashion. If you are having call fail and the code is not a 6xx then it is a whole different scenario.
Definitely seeing some 603 errors and some 404, 403, 500s as well. Thanks for the input.
 
404 = Not found, typically a non working number. If it is a working number then its a route issue
403 = carrier refused call, these typically would have more details with them outlining the refusal
5xx could be a variety of errors, I would recommend checking out the wiki for SIP codes: https://en.wikipedia.org/wiki/List_of_SIP_response_codes
 
  • Like
Reactions: Nathan@Voxtelesys
I've temporarily worked around this by using a different provider for a select group of extensions for outbound calls. I registered that number with the registries and so far this seems to be working until the overall issue is resolved.
 
404 = Not found, typically a non working number. If it is a working number then its a route issue
403 = carrier refused call, these typically would have more details with them outlining the refusal
5xx could be a variety of errors, I would recommend checking out the wiki for SIP codes: https://en.wikipedia.org/wiki/List_of_SIP_response_codes

If the provider is responding with a 5xx code, keep in mind that 5xx means that the PROVIDER has an "internal issue". Your next port of call would be asking the provider for specific details about why it failed. I might add that "5xx" is still on the vague side, a more specific code might give more insight.
 
I still have a bunch of Decline (603) errors. My customer did filed out the registry forms weeks ago and still having issues.
 
Do you have a ticket open with our team? If you share some examples we can check them called carrier and see if there is a common carrier. If all the calls go to Tmobile, then you could register directly with Tmobile and setup a free first Orion account vs the free call registry link.
 
Do you have a ticket open with our team? If you share some examples we can check them called carrier and see if there is a common carrier. If all the calls go to Tmobile, then you could register directly with Tmobile and setup a free first Orion account vs the free call registry link.
Yes. It looks like it's all up to the phone carriers now. Of course, my customer will think it us. But my customer is doing the work of notifying the carriers to get on a whitelist
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,281
Messages
591,677
Members
165,402
Latest member
noufir