Tapping recent inbound calls in Call History to call back results in forbidden message

Status
Not open for further replies.

drenmatt

Free User
Joined
Sep 16, 2020
Messages
4
Reaction score
0
Hey guys, I am fairly new to the 3cx pbx set up, but I was able to get it up and running fairly well by reading 3CX documentation. That said, I have a strange issue going on. All of my firewall rules passed in the pbx, I have the same FQDN set up for inside and outside and all works well. That said, I get a forbidden message when I tap on a missed inbound call under the recents view to call the person back. This happens on my Android 3CX client and on my Mac 3CX client. Is there any way to solve this? I can tap on the keypad icon and manually type the exact same number and the call goes through just fine. I find this a little odd. Maybe I am missing a setting somewhere to call call history callbacks or something?
 
Are numbers in history complete numbers ? no missing first digit ?

Can you call externals numbers dialing directly without call history?
 
Hi there. Yes, the history contains complete phone numbers, they all are 11 digits, for example it might show 16145551212 in the history of missed inbound calls and when I tap on it, it begins to dial that number back, but then suddenly fails with the "Forbidden" message. However, if I dial the same number manually from the dialpad screen, it works just fine.
 
In this case you need to replicate this exact scenario you describe, but have Verbose logs enabled from Activity Log and compare the log of calling it back via tapping VS dialling it manually.

We might expect to see a different number being sent in the first case vs the second case
 
OK, I just did it again. Here's what is going on. Let's say I miss a call from 16145551212, when I tap on that missed call in the "recent call history" tab, the app tries to dial it and shows 16145551212 at the top of the screen, then gives me the "forbidden" message. When I then look in the call history, it shows it dialed 6145551212 instead of 16145551212. So somehow, it is removing the 1. Ideas?
 
Also FYI, if I add a 1 to the prepend outbound call string on my main outbound call route on the 3CX server, then I can simply click on the missed call and it will dial them properly. But, that also means I can't call internationally without removing that rule or adding other rules.
 
In your PBX outbound rules, do you have a rule which has strip 1 digit?
1600670096934.png

In the PBX Settings, under E164 do you have the rule to remove any digits?
1600670262817.png
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,832
Messages
589,285
Members
164,662
Latest member
DejanMDS