Unsupported How to use 2nd line on Yealink TA410

[marian.b]

Hello,

I've got a 3CX system running for some time now. It's pretty stable.
3CX is used with Yealink TA410 that can connect to 4 lines. At the moment, i have 3 lines connected and waiting for the 4th line.
The current configuration on TA410 has two trunks (2 lines in trunk 1 + 1 line in trunk 2). On this device all is set to have a proper connection to my 3CX server. Looking into the logs, i have noticed that the 3CX is usually running almost entirely on the first 2 lines.

3CX is able to receive calls from all 3 lines but usually goes out only on TRUNK1 (consisting of those 2 lines).
In the OUTBOUND RULES section, i have a rule that is pointing to the TA410 gateway. But this goes out only on first 2 lines (TRUNK 1). If i add to that trunk that 3rd line and set up the rule of what line should be chosen, TA410 will also make use of it.

Now i need to change things a bit. I want to have 2 TRUNKS, each of them with 2 lines. And i want to be able to select from 3CX system what trunk to be used for outgoing calls.
By default, outgoing calls go out on TRUNK1 (looking what line is available).
The old analog system that i had been using for several years had 4 extensions (100, 101, 200, 201) and when i was picking up the receiver i had to first dial the extension (201, for example) then the phone number. This was nice & easy.

I am trying to make this setup of being able to chose another outgoing route (rather than the default one) because in some countries calls from my 1st provider are restricted.
How can i set the 3CX to go on the default route all time but having, at the same time, the possibility to chose the second trunk from TA410?

Any advices?

Thank you!
Best regards,
M.

 

[leejor]

To add additional extensions to a set would require creating a custom template, or manually provisioning the set, then preventing it from downloading any template updates.

https://www.3cx.com/docs/custom-ip-phone-templates/

However..., as the Unsupported label, against your post, suggests, the set would then be considered by 3CX to be just that, and would have to be re-provisioned if you intended to submit a trouble ticket to 3CX..

If you did provision more then one line key per set, the outbound rules could be modified so that each extension number, on the set, would use a specific route (PSTN gateway?), or add a specific caller ID (SIP trunk).

The alternative might be to have the user dial a specific prefix, to access each trunk.

 

[marian.b]

Oh my, i feel like a gardener trying to be a pilot .
I only have one gateway with 4 lines. 3CX is connected there, randomly taking in/out one of the lines.

Can you describe a bit the alternative of using prefixes?
I think it looks easier to modify the outbound rules in order to access specific lines on the T410. I checked the TA410 manual but as i am not experienced in this area, i don't know what would be the correct flow of outgoing calls.

Thanks!

 

[leejor]

If you are using a PSTN gateway, and it is setup as a single trunk group, then, unless it is the type that makes use of a prefix, to select the line, on the gateway (some Grandsteam gateways do this), then this is not possible.

To select a specific outgoing line, you would have to create four trunk groups, one per PSTN line, on both the gateway and in 3CX. Each wuld still use he same IP of the gateway, but a different port. You could then choose which trunk each call/extension would use, based on the outbound rules.

As it stands, with one trunk group, the gateway will choose which PSTN line to use for outgoing calls.

Incoming calls could still be routed to different destinations, using DID rules, even with the single trunk group.

 

[marian.b]

Incoming calls are already routed using DID rules. All good there.
At the moment, i tested with a single group that has 3 lines and it goes round robin on them.
Then is only one trunk that si created in between my gateway and 3CX server. I'll try to use the same address but another port for extra trunks.

I will come back with the result on Monday.

Thank you!