After updating to v4 follow Me is not working on the main pbx tenant
Any advise
Please share a call trace from Asterisk CLI
We cannot give you a response with no details at all!
It looks like it’s missing a lot of logs from this call trace
Please grep C-00000128 from the asterisk log file and post the full call trace
Are you able to dial the numbers in your followme list directly from the main tenant?
Follow me appears to be trying to ring 9083779022 and 9083779022 correctly but you are getting Everyone is busy/congested at this time practically immediately.
Trunk issue? The calls are using your Outbound Route: VOIP.MS
[2024-07-18 11:07:39] VERBOSE[353378][C-0000015a] app_dial.c: Called Local/9083779022@cos-all/n
[2024-07-18 11:07:39] VERBOSE[353378][C-0000015a] app_dial.c: Called Local/8456595581@cos-all/n
[2024-07-18 11:07:39] VERBOSE[353378][C-0000015a] app_dial.c: Local/9083779022@cos-all-000000bb;1 is ringing
[2024-07-18 11:07:39] VERBOSE[353408][C-0000015a] app_dial.c: Called PJSIP/18456595581@EC2pbx-trunk
[2024-07-18 11:07:39] VERBOSE[353378][C-0000015a] app_dial.c: Local/8456595581@cos-all-000000bc;1 is ringing
[2024-07-18 11:07:39] VERBOSE[353378][C-0000015a] app_dial.c: Local/8456595581@cos-all-000000bc;1 connected line has changed. Saving it until answer for PJSIP/unifiedvox-00000287
[2024-07-18 11:07:39] VERBOSE[353378][C-0000015a] app_dial.c: Local/9083779022@cos-all-000000bb;1 connected line has changed. Saving it until answer for PJSIP/unifiedvox-00000287
[2024-07-18 11:07:39] VERBOSE[353407][C-0000015a] app_dial.c: Called PJSIP/19083779022@EC2pbx-trunk
[2024-07-18 11:07:39] VERBOSE[353407][C-0000015a] app_dial.c: Everyone is busy/congested at this time (1:0/0/1)
[2024-07-18 11:07:39] VERBOSE[353378][C-0000015a] app_dial.c: Local/8456595581@cos-all-000000bc;1 is busy
[2024-07-18 11:07:39] VERBOSE[353407][C-0000015a] app_dial.c: Everyone is busy/congested at this time (1:0/0/1)
Thanks for the help.
Outgoing calls for the primary tenant are not working. I think this account is only receiving calls. It’s missing a DID for outgoing calls. I can’t think of what is setting the DID, not the caller-ID, for the extension. Please advise.
Dont forget it is the main PBX tenant so we cant just set default configs on the trunk or outbound routes
Also, something has changed in v4 that is causing it to missing the DID since in v3 it was working fine
DID is only involved in incoming calls, the CDR should not show anyting in DID for the outbound calls.
Is the outbound route that your main tenant using properly set? Is it sending the callerid your trunk provider is expecting? Is that trunk that the outbound route using properly connected?
Nothing was changed on our end except for switching from v3 to v4, and now outbound calls are not working for the main tenant.
We switched by exporting and importing a backup
Using sngrep -c you should be able to see more information about why your trunk provider blocked the call. You should be able to see an error code and sometimes also an error message
Like @sama mentions, using sngrep to troubleshoot a live call will help you best now to show what you are getting back from your trunk provider.
Nothing was changed on our end except for switching from v3 to v4, and now outbound calls are not working for the main tenant.
We switched by exporting and importing a backup
You did migrate to a new server so some things could change, for example did the IP of the server change? Maybe that trunk provider is rejecting calls from the new ip if you are using IP authentication.
As of this moment with the logs you have provided it seems like a trunk issue, providing more info/logs of your trunk status and what you see on a call using sngrep will certainly help to troulbleshoot better.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.