Toggle sidebar Toggle sidebar

Solved Unsupported trunk between v18 and v20

Status
Not open for further replies.

abdulla_ahmed

Customer
Joined
May 17, 2023
Messages
8
Reaction score
0
We have configured unsupported SIP trunk and it was working all good for around 5 months, after we upgraded the system to V20 we noticed two provider can't call the number only same provider customers can call the line.
We reverted back to V18 the line working good with all three providers. But once we upgrade to V20 the two providers can't reach the number.

We noticed during capturing network traffic 'unsupported URI Scheme' but don't understand what's different between V18 configurations and V20 as the provider was imported with same settings
 
Unfortunately, we won't be able to advise on unsupported providers.
You could pick one of the supported ones, or try to get the current one to be supported.
 
It's working on v18 currently as we downgraded
What's the changes in v20 for uri scheme as same template imported from v18 which its working perfectly
 
abdulla_ahmed said:
we noticed two provider can't call the number only same provider customers can call the line.
Click to expand...
To be clear... does this mean that callers, from two other providers, are unable to all your number?

Are these mobile providers, VoIP providers?

What destination do they reach when calling?

Are you able to use the 3CX Activity Log to see if the calls are reaching 3CX, and if so, what does the log show as to how the call is handled?

Did you engage your provider for assistance, when this was happening?
 
leejor said:
To be clear... does this mean that callers, from two other providers, are unable to all your number?

Are these mobile providers, VoIP providers?

What destination do they reach when calling?

Are you able to use the 3CX Activity Log to see if the calls are reaching 3CX, and if so, what does the log show as to how the call is handled?

Did you engage your provider for assistance, when this was happening?
Click to expand...
Our country have three providers for mobile and landline
I'm using one of the three for the landline, after upgrading to v20 only calls from same my provider can call our landline number. the other two provider when they try to call it's showing phone number closed
I have captured the traffic on the network interface and notice this

SIP 716 Status: 416 Unsupported URI Scheme

Now we reverted to v18 which it's working as normal. I also verified the templated imported in v20 for the provider it's the same and have same inbound parameters as v18
 
Are you able to compare a working call, to a failing one, in the Activity Log, to see the difference, in the Invite?.

Have you spoken to your provider to see if they can offer any suggestions at to what the call difference might be? As calls originating from their subscribers are working, then it suggests that they are sending something different, when the call originates from an external source. They may have some control over that.
 
leejor said:
Are you able to compare a working call, to a failing one, in the Activity Log, to see the difference, in the Invite?.

Have you spoken to your provider to see if they can offer any suggestions at to what the call difference might be? As calls originating from their subscribers are working, then it suggests that they are sending something different, when the call originates from an external source. They may have some control over that.
Click to expand...
The provider wouldn't support us
I haven't compare because in v20 the page for configuring the inbound parameters which was in v18 was removed
 
You might want to use something like Wireshark to compare calls from other providers to those from the same provider. Even when using version 18, there should be some difference, as the Invite from your provider shouldn't be changing simply because you are using version 20.

You might also want to mention the name of the provider. Perhaps someone else will have to, or has already dealt with this issue.
 
Last edited:
leejor said:
You might want to use something like Wireshark to compare calls from other providers to those from the same provider. Even when using version 18, there should be some difference, as the Invite from your provider shouldn't be changing simply because you are using version 20.

You might also want to mention the name of the provider. Perhaps someone else will have to, or has already dealt with this issue.
Click to expand...
Thanks a lot for the support

But again even if I compare the messages how I would configure the inbound parameters in v20 as no way to that
 
If you find the difference, then that is going to be the "clue" as to what needs changing. Post the information here in the forum and someone may have a solution, or a recommendation as to what to try..
 
abdulla_ahmed said:
Lets wait for 3cx to find solution
Click to expand...
As advised before, if the trunk is not supported, we won't be able to help and troubleshoot the issue, and these are our support procedures.
 
OlegR_3CX said:
As advised before, if the trunk is not supported, we won't be able to help and troubleshoot the issue, and these are our support procedures.
Click to expand...
Not sure why you keep repeating this. The issue is clear for us. It's something wrong between v18 and v20 in the inbound parametersn. Since the inbound parameters are removed in v20 we are not able to reconfigure the trunk with the Voip setup.

Also note in our country we don't have provider which you support. So the only option to stick with what we have
 
abdulla_ahmed said:
Not sure why you keep repeating this. The issue is clear for us. It's something wrong between v18 and v20 in the inbound parametersn. Since the inbound parameters are removed in v20 we are not able to reconfigure the trunk with the Voip setup.

Also note in our country we don't have provider which you support. So the only option to stick with what we have
Click to expand...
Very good in this case and as already suggested you may export the trunk settings, make your changes, delete the current trunk and import the changed one back.
 
@abdulla_ahmed
Have you tried checking your trunk with the NEW Update 1?
 
Hi there.
Thank you for the update and glad it's all working now.
This thread will now be closed.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,990
Messages
590,161
Members
164,926
Latest member
tohoken1
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom