trunk with different DIDs

Status
Not open for further replies.

csavulescu

Free User
Joined
Dec 16, 2019
Messages
10
Reaction score
0
Hi everyone,

I have setup a trunk in 3cx and have added multiple telephone numbers and extensions, however I cannot seem to understand how to associate outbound telephone numbers to the extensions.

I have something similar to this

Extension 00 Chris tel: xxxx003 - works for both outbound and inbound calls with the correct tel no
Extension 01 Gina tel: xxxx004 - works fine for receiving calls on her extension by calling tel no xxxx004, but when making calls it uses the same tel no as extension 00 xxxx003

I imagine this is because it follows the "Route calls to" in the SIP trunk?

What I want to achieve is extension 00 to make and receive calls via it's tel no xxxx003 and extension 01 to make and receive calls via it's own tel no xxxx004.

Can anyone help?
 
You configure the 'Outbound Caller ID' with the correct DID for the extension.

In the sip trunk,, outbound parameters check 'Remote Party ID - Calling Party : Display Name' and 'Remote Party ID - Calling Party : User Part' is set to 'OutboundCallerid' Outbound caller taken from extension settings in management console.
 
Hi,

Have you seen the "Outbound Caller ID" setting under your extension settings?
13547
 
Hi,

Have you seen the "Outbound Caller ID" setting under your extension settings?
View attachment 13547
Yes, but sadly, if you add the PSTN there, outbound calling will stop working.

My workaround for the moment is setting up new trunks in both twilio and 3cx for the other extensions.
 
I think it's a good idea to enable Verbose Logging (under Activity Log) and see why it fails before you go ahead looking for workarounds that might not actually be needed.

Perhaps the format that you enter the number in the extension VS the trunk VS what the provider expects does not match somewhere. The logs will give us a better idea of what happens, and once we know then we can take appropriate action.

I imagine this is because it follows the "Route calls to" in the SIP trunk?
Also in answer to the above, it only affects inbound - so no this not the reason in your case. Spend some time with the logs. Make a test call and then for ease, you can filter using "Search By Call" to catch the latest call and make your filtering show the last call.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,934
Messages
589,822
Members
164,814
Latest member
Ruben756