I was told not to ask BobRTC-related questions on the Discord, so hopefully someone can help me here.
When calling certain numbers (that hang up immediately), rapid redial won't attempt to try them back multiple times, it acts as a single call each time you press it. No "this number is not in service" or "this number is not accepting calls right now" messages of any kind either, just an immediate disconnect.
What is likely occurring in these instances?
[[73],[1,21,73]]
@KGB#118835 Just to make sure I fully understand what is happening, are you experiencing this on certain phone numbers that still exhibit normal behavior (being able to dial them and talk with someone etc.) when called regularly; or, does this immediate disconnect and halting of the feature only occur on phone numbers that hang up quickly after regularly calling ? Hopefully I made my question clear enough, but let me know if not and I will rephrase it the best I can.
Although I will have to check with another person to confirm this, from my understanding, rapid redial will not continue it's chain of calls if the talk-time of the first call in the sequence is under a certain threshold.
Thank you
I am having a similar issue if not the same example: 1 (872) 267-9329
if I call from from Bob it will connect (single call) not ring then disconnect. if I call using Hangouts / voice it will connect every time. hope this helps
started working now!! Thanks for whatever you did!!
@Loki101#118890 Yea, our tolled dialing has been messed up for the past day or so. Just came to our attention.
@Norm_Harrison#118868 I may have spoken too soon. I went back and tried to replicate the issue so I could provide specific examples, and found that I was having much more difficulty placing outbound calls than I had initially thought, although my setup had not changed. I just ran CCleaner to clear all caches which logged me out completely, but now I seem to be getting stuck on the authorization step (even though it went through flawlessly before). I’ll try a few more things later today and if I’m able to recreate the problem I’ll report back in greater detail.
@KGB#119135 BobRTC was under construction for the last few hours. Not sure if it’s running right now. Check again tomorrow 
Okay, after further testing I’m back with some specifics.
Calling (302) 684-6186 from BobRTC: Works perfectly every time.
Calling (805) 457-4186 from BobRTC: Immediate disconnect, doesn't even ring. Rapid redial has the same effect, and does not attempt to redial.
Calling (805) 457-4186 from alternate source: "Thank you for calling Social Security"
Calling (607) 603-1395 from BoRTC: Immediate disconnect
Calling (607) 603-1395 from alternate source: Fast busy signal
Calling (479) 350-5127 from BobRTC: Immediate disconnect
Calling (479) 350-5127 from alternate source: "Your call cannot be completed as dialed. Please check the number and try again."
Each of these numbers is being dialed from a separate tab within the same browser window. At any point in time after unsuccessfully attempting to place a call, I can click over to the tab for (302) 684-6186, and it works perfectly. Click the tab for, say, (607) 603-1395, immediate disconnect. Click BACK over to the tab for (302) 684-6186, connects perfectly.
Edit: Refreshed the tab for (805) 457-4186 and it started working again! However, refreshing the tab for (479) 350-5127 has no effect.
@Norm_Harrison#118868 Just tagging you here since my previous post didn’t seem to bump the topic back up to the top.