I've had this sort of cascading series of minor issues in upgrading this one particular client to v20 (update 2, build 715). It's self hosted in the cloud, using Flowroute as the SIP provider. After successfully upgrading to v20, I made the mistake of adding a + symbol to the beginning of the "Main Trunk Number" as well as each of the DID's in the trunk settings in 3CX, because 3CX says to do that in the little banner right below that says you must have a + symbol at the beginning (e164 format).
However, after doing so, the customer couldn't receive any calls and the event logs showed a bunch of error 30051 "unidentified incoming call. Review INVITE and adjust source identification". This was vaguely familiar to me from a few years ago when we had some issue that required setting/changing the inbound parameters "to user part section" or something. So, I figured no big deal, I'll go change that setting back to the default so that can have the numbers in proper e164 format and avoid future issues/confusion. However, I couldn't find that setting. It seems it was retained during the upgrade but has been deprecated and is no longer available in the GUI. https://www.3cx.com/community/threa...ng-with-flowroute-3cx-v20.126354/#post-597800
So, I figured "no big deal" ... at this point, I should be able to just delete and re-add the trunk. However, we use IP-based authentication with Flowroute, for better security (as recommended by Flowroute). Unfortunately, when I attempt to add a new trunk, and select Flowroute as the carrier, the SIP credential fields are now REQUIRED in 3CX. Does anyone know why 3CX is requiring SIP credentials to be entered for Flowroute and not allowing me to use more secure IP-based authentication?
Further, it seems that if I choose "Generic SIP Trunk", the dropdown appears for "type of authentication" and allows you to set it to "Do not require - IP Based", yet the SIP Credentials are still REQUIRED fields.
I just deployed a brand new 3CX system, created from scratch, last month, using similar configuration (Flowroute, IP based auth) and did not have this problem. I was able to create the trunk without entering any SIP credentials. However, if I try to add a new trunk on THAT same system, I have the same issue now. I believe that system was deployed prior to update 2 becoming available, so I'm guessing this is a new issue that was introduced in a recent build from the past month.
I'm wondering if there's anything I can edit in the Flowroute trunk template ... but in looking through that, it's not obvious to me what that would be. Does anyone have any thoughts/suggestions? Is there any reason to think this is something 3CX might fix, or is this requirement to use SIP authentication just something else that is being forced upon us whether we like it or not?
Thanks!
Marc
However, after doing so, the customer couldn't receive any calls and the event logs showed a bunch of error 30051 "unidentified incoming call. Review INVITE and adjust source identification". This was vaguely familiar to me from a few years ago when we had some issue that required setting/changing the inbound parameters "to user part section" or something. So, I figured no big deal, I'll go change that setting back to the default so that can have the numbers in proper e164 format and avoid future issues/confusion. However, I couldn't find that setting. It seems it was retained during the upgrade but has been deprecated and is no longer available in the GUI. https://www.3cx.com/community/threa...ng-with-flowroute-3cx-v20.126354/#post-597800
So, I figured "no big deal" ... at this point, I should be able to just delete and re-add the trunk. However, we use IP-based authentication with Flowroute, for better security (as recommended by Flowroute). Unfortunately, when I attempt to add a new trunk, and select Flowroute as the carrier, the SIP credential fields are now REQUIRED in 3CX. Does anyone know why 3CX is requiring SIP credentials to be entered for Flowroute and not allowing me to use more secure IP-based authentication?
Further, it seems that if I choose "Generic SIP Trunk", the dropdown appears for "type of authentication" and allows you to set it to "Do not require - IP Based", yet the SIP Credentials are still REQUIRED fields.
I just deployed a brand new 3CX system, created from scratch, last month, using similar configuration (Flowroute, IP based auth) and did not have this problem. I was able to create the trunk without entering any SIP credentials. However, if I try to add a new trunk on THAT same system, I have the same issue now. I believe that system was deployed prior to update 2 becoming available, so I'm guessing this is a new issue that was introduced in a recent build from the past month.
I'm wondering if there's anything I can edit in the Flowroute trunk template ... but in looking through that, it's not obvious to me what that would be. Does anyone have any thoughts/suggestions? Is there any reason to think this is something 3CX might fix, or is this requirement to use SIP authentication just something else that is being forced upon us whether we like it or not?
Thanks!
Marc
