- Joined
- Oct 6, 2016
- Messages
- 8
- Reaction score
- 0
I trying to use the info from this article http://www.3cx.com/docs/multiple-outbound-caller-ids/. What I like to do is:
-I have trunk1 with a DID range xxxxxxx1-xxxxxx10, on which users are calling out with their own DID's i.e. xxxxxx07, which is set in their Ext as CallerID. This works fine.
-Then I have trunk2 with 1 DID, some users of trunk1 also need to able to call out on this trunk, now showing this 1 DID.
This situation is similar to the scenarios in the article but I doesn't work for me.
I'm able to select trunk 1 or 2 with a leading digit in the called number and a filtering Outbound rule, that works so far.
btw. can I select a trunk using the line buttons (yealink) somehow instead of a number prefix?
The article is based on 3CX v14 I'm on v15, some parts are confusing me:
In the Prerequisites it says;
In a forum post somewhere I've read that the Outbound CallerID formatting is only used in cases when an unanswered call is forwarded to i.e. mobile (Ext forward rule), is that so? Or is this formatting also valid for outgoing calls like explained in the 3 scenario's of the article?
I tried all combination but it seems the formatting is not active somehow, all I see on the display of the called number is the extension nr.
My outbound rule has this Ext in it's rule, so it using this trunk alright. The trunk CallerID is empty.
(I noticed that when an trunk CID and also an Ext CID is filled in, that the Ext CID is send out not the Trunk CID. When the Ext CID is empty then the Trunk CID is used).
-I have trunk1 with a DID range xxxxxxx1-xxxxxx10, on which users are calling out with their own DID's i.e. xxxxxx07, which is set in their Ext as CallerID. This works fine.
-Then I have trunk2 with 1 DID, some users of trunk1 also need to able to call out on this trunk, now showing this 1 DID.
This situation is similar to the scenarios in the article but I doesn't work for me.
I'm able to select trunk 1 or 2 with a leading digit in the called number and a filtering Outbound rule, that works so far.
btw. can I select a trunk using the line buttons (yealink) somehow instead of a number prefix?
The article is based on 3CX v14 I'm on v15, some parts are confusing me:
In the Prerequisites it says;
I suppose this a provider requirement? But why is that OrginatorVallerID option shown? Do I need to set this option in Trunk>Outbound parameters somewhere?The trunks MUST support “Originator Caller ID” (Clip No Screening)
In a forum post somewhere I've read that the Outbound CallerID formatting is only used in cases when an unanswered call is forwarded to i.e. mobile (Ext forward rule), is that so? Or is this formatting also valid for outgoing calls like explained in the 3 scenario's of the article?
I tried all combination but it seems the formatting is not active somehow, all I see on the display of the called number is the extension nr.
My outbound rule has this Ext in it's rule, so it using this trunk alright. The trunk CallerID is empty.
(I noticed that when an trunk CID and also an Ext CID is filled in, that the Ext CID is send out not the Trunk CID. When the Ext CID is empty then the Trunk CID is used).