Hello,
In U5A1 there was an issue with having the WA-number on more than one trunk. The release notes say this is fixed for Alpha 2.
I am however experiencing the following behavior, which I think is not how it should be.
I have two trunks, one from cm.com and one from WhatsApp.
Both have the number +3112345.
In WA, the number routing is configured directly on the trunk to a group (804 in my case, 24/7)
I had deleted the did from cm.com trunk, but I decided to add it back in alpha 2.
So, after adding it back in the trunk/did, I went to inbound rules to re-create the inbound rule.
In the number dropdown hoewever, I got the numer +3112345 displayed twice since it was of course setup for two trunks.
Not sure which was which, I just picked one and configured it to 804 (group) for in office hours and 807 (ivr) for out of office hours.
After adding the inbound rule, it showed up un the list as ‘cm.com trunk’.
So, I called the number from my mobile and it went to queue 804 but it should have gone to 807 since it’s out of office.
I checked the event log and it said the call came in on trunk ‘WhatsApp’. That not of course, since the number is registered at cm.com and really comes in through them.
But fair enough, I went back to inbound rules and created another inbound rule with the second incarnation of the number +3112345 selected in the dropdown.
After adding that, it shows up in the inbound rules list as WhatsApp trunk. I configured that one for 804 and 807 (in/out office hours) as well.
I then called the number again and the call went to 807. Event log still says the call comes in through the WA-trunk.
Then, I sent WA messages but it doesn’t come through.
That’s probably because it’s out of office now and it now routes to ivr 807.
So, two problems:
The number is shown twice in the dropdown, you cannot see which trunk it belongs to. But this is merely inconvenient, not a show stopper.
Second: 3CX always thinks inbound calls to the number come through the WA-trunk instead of the cm.com trunk. It then also follows the WA-routing for calls, where in A1 you could have WA messages routed to 804 24/7 and calls to 804/807.
It shows this in the log: 08/10/2022 11:40:18 PM - [CM101011]: There's incoming call on the line '' marked as outbound-only!Lc:10005(@Whatsapp[<sip
:0/UDP>])
I hope I explained it clearly enough
If not, let me know!
Addition:
I deleted the did from the cm.com trunk again, so it should use the default set up there again, this was also suggested in the other forum thread. But this doesn’t work in U5A2 anymore. 3CX believes the call comes in via the WhatsApp-trunk and uses the call routing set up on the trunk there.
Add2:
WA messaging is fine when the message is sent to the group (804).
In U5A1 there was an issue with having the WA-number on more than one trunk. The release notes say this is fixed for Alpha 2.
I am however experiencing the following behavior, which I think is not how it should be.
I have two trunks, one from cm.com and one from WhatsApp.
Both have the number +3112345.
In WA, the number routing is configured directly on the trunk to a group (804 in my case, 24/7)
I had deleted the did from cm.com trunk, but I decided to add it back in alpha 2.
So, after adding it back in the trunk/did, I went to inbound rules to re-create the inbound rule.
In the number dropdown hoewever, I got the numer +3112345 displayed twice since it was of course setup for two trunks.
Not sure which was which, I just picked one and configured it to 804 (group) for in office hours and 807 (ivr) for out of office hours.
After adding the inbound rule, it showed up un the list as ‘cm.com trunk’.
So, I called the number from my mobile and it went to queue 804 but it should have gone to 807 since it’s out of office.
I checked the event log and it said the call came in on trunk ‘WhatsApp’. That not of course, since the number is registered at cm.com and really comes in through them.
But fair enough, I went back to inbound rules and created another inbound rule with the second incarnation of the number +3112345 selected in the dropdown.
After adding that, it shows up in the inbound rules list as WhatsApp trunk. I configured that one for 804 and 807 (in/out office hours) as well.
I then called the number again and the call went to 807. Event log still says the call comes in through the WA-trunk.
Then, I sent WA messages but it doesn’t come through.
That’s probably because it’s out of office now and it now routes to ivr 807.
So, two problems:
The number is shown twice in the dropdown, you cannot see which trunk it belongs to. But this is merely inconvenient, not a show stopper.
Second: 3CX always thinks inbound calls to the number come through the WA-trunk instead of the cm.com trunk. It then also follows the WA-routing for calls, where in A1 you could have WA messages routed to 804 24/7 and calls to 804/807.
It shows this in the log: 08/10/2022 11:40:18 PM - [CM101011]: There's incoming call on the line '' marked as outbound-only!Lc:10005(@Whatsapp[<sip
:0/UDP>])I hope I explained it clearly enough
If not, let me know!
Addition:
I deleted the did from the cm.com trunk again, so it should use the default set up there again, this was also suggested in the other forum thread. But this doesn’t work in U5A2 anymore. 3CX believes the call comes in via the WhatsApp-trunk and uses the call routing set up on the trunk there.
Add2:
WA messaging is fine when the message is sent to the group (804).
Last edited:
