Solved Telekom Trunk - Lancom - 3CX

[E. John]

Following Situation:

3CX Enterprise 24SC Hosted by 3CX
Customer has a Telekom Sip-Trunk, which is connected to their Internet line (so i cant register it in The cloud)
Telekom Siptrunk is registriert on a Lancom VOIP Router, which is registert as a master Bridge on the 3CX

Calls are getting routed from the Lancom to the PBX and ring the right extension, but on the display it shows the Localhost IP.

As you see in the screenshot,the caller Number is in the "from field", but its not display behind the Line; it only shows a + (also in the "making route from Line")

Does somebody know how we can fix this?

If you need to information just say it, im willing to share more to get this done^^

With best regards E. John

*the customer cant port their numbers to a different provider, so we want to use a workaround to let them keep their numbers.

 

[NickD_3CX]

While I can't be sure, I think you need to play around with these settings to get your 3CX read the Caller ID from the right SIP field....

 

[E. John]

The Support Team told me the same :`D Problem is that we registerd the Lancom as a bridge, bc the 3CX cant register itself on the Lancom (lancom Problem) and bc of this we dont have any inbound parameters.

We will try to register it as a generic Trunk with Inboud Authentification, but we dont know if it will work...

While I can't be sure, I think you need to play around with these settings to get your 3CX read the Caller ID from the right SIP field....
View attachment 21798

 

[NickD_3CX]

Although not supported, then maybe consider creating an "IP-Based SIP Trunk" between the LANCom router and your 3CX, then you would be more flexible.

Other than that, I am out of ideas, maybe someone else has some other idea.

 

[E. John]

Although not supported, then maybe consider creating an "IP-Based SIP Trunk" between the LANCom router and your 3CX, then you would be more flexible.

Other than that, I am out of ideas, maybe someone else has some other idea.

Your idea lead to the solution. With some Support from Lancom and a few fails we got it working...

Thank you for your help Nick