Solved Outgoing calls - two SIP Trunks

[Tomas Raska]

Hello,
we have two sip trunks - Deutsche Telekom NGN Profile.
And every extensions have setup "Outbound caller ID" number from first or second SIP trunk (depend on locations)

Problem is, that we can make outgoing call only over SIP trunk, where exist this outbound caller id number.
When we delete "Outbound caller ID", then we can make outgoing call over booth sip trunks. But then we do not have outgoing identification (identification is main number)

Is it possible to setup 3cx, that we cann make outgoing calls over booth sip trunks and when we call over local sip trunk then correct identification is sent (outbound caller id) and when we call over remote sip trunk then is send identification main number?

 

[AWS2P]

Do you have DID's on those trunks? or only main number for each trunk?

 

[Tomas Raska]

Yes, lot of DID, for both SIP trunk we have block of 1000 numbers

 

[AWS2P]

you always want to have DIDs sended to callee from both trunks?
If so , you need to be sure your sip provider has no restrictions about this

you need to set each DID number in extensions outbound caller ID field, and let blank " default caller id" field in trunk sip settings if you set main number here.

you need also incoming rules if you want each DID to be forwarded to extension when they are called

 

[JohnS_3CX]

Hi Tomas,

If you see here, you will notice that Clip No Screening support is available as a separate service for the NGN trunks. https://www.3cx.com/partners/sip-trunks/deutschland/

This means that the provider does not allow you to make calls from numbers that don't belong to you. So if extension 100 has an outbound ID that belongs to trunk A, but you attempt to make a call via Trunk B, the provider will most likely stop you. You can ask the provider to enable this option for you and you should be able to work as needed.

 

[Tomas Raska]

I found my Problems:

in this threads is solutions (one Parameter in SIP Trunk Deutsche Telekom is wrong):

https://www.3cx.de/forum/threads/te...le-update-fehler-bei-clip-no-screening.59745/

Now I can make outgoing calls over booth SIP Trunks when Outbound Caller ID is setup.

And second Problem, Deutsche Telekom even though it was CLIP no screening ordered, they did not activate it. Now I see too correct phone numbers.

 

[AWS2P]

Glad you fix it , well done

 

[JohnS_3CX]

Hi Tomas,

Glad this was resolved. As for the wrong value, the default template is tested and confirmed to work with a single trunk, but for special case scenarios this depends on each provider (they will tell you what they want and from which field depending on what you plan on deploying).