Outgoing calls working over one trunk and rejected over another in the same PBX

[Aron]

In my NFR instant (V20, on perm, Linux) I’ve connected 2 trunks from a provider not yet supported by 3CX. (on going procedure).

I’ve given both trunks the exact same configuration (very standard).

Both trunks register and incoming calls are working.

But, only one of the trunks allow outgoing calls while the other trunk rejects outgoing calls with cause value 401.

In the pcap file of the sucessful call, the “From” message includes the trunk’s user name:

From: “044xxxxxxx” <sip:[email protected]>

In the pcap file of the unsucessful call, the “From” message shows the CLI instead:

From: “042xxxxxx” <sip:[email protected]>

I then tested with the trunk's user name in the CLI field of the outgoing rule that route over the rejecting trunk.

And the call goes through.

The “From” message for that call:

From: “042xxxxxxx” <sip:[email protected]>

What am I doing wrong ?

 

[leejor]

Maybe I'm reading this incorrectly, but...
you say...

But, only one of the trunks allow outgoing calls while the other trunk rejects outgoing calls with cause value 401.

In the pcap file of the sucessful call, the “From” message includes the trunk’s user name:

OK, so that trunk works.

Then you say...

I then tested with the trunk's user name in the CLI field of the outgoing rule that route over the rejecting trunk.

And the call goes through.

So, it sounds as if you've used exactly the same settings as in the first (working) trunk, and now the second one works, to which you seem surprised.

I'm confused as to the issue, if the changes you made now have the trunk working.

Did you ever speak to your provider about this?

Calls can be rejected for a number of reasons that aren't immediately apparent , including an incorrect (format) caller ID.

Even with trunks to the same provider (sub-account?) , there could be different specs required. I would suggest talking to your provider to clear this up.

You may also wish to divulge the provider in the event someone else has has an experience with them.

 

[Aron]

With the trunk that was working in the first place, I never set anything in the CLI field of the outgoing rule.
The second trunk only allow outgoing calls if the trunks's name is set in the CLI field of the outgoing rule.

 

[leejor]

A provider can be picky about what you are sending, and the only way to confirm the correct information, is to ask them why this is happening. It could be a setting that can be (or needs to be) changed, at their end.

Being a non-supported provider, I don't think you will get much sympathy on the forum, The standard responce is to use a supported provider.