Question about trunk configuration sip/pjsip

Good Morning
I have the following scenario:
A telephone operator in my country (Brazil), delivers SIP trunks through modems / routers, each of these modems / routers has a network configuration, which is usually an IP for PABX and the Gateway, which in this case is the modem itself / router, an endpoint is provided to configure the SIP trunk.
Example:
PABX IP: 10.20.1.2
Gateway: 10.20.1.1
Endpoint: 10.50.1.1

To configure this scenario it is simple: I create a route in linux for the endpoint passing through the gateway

My question is:
How to configure 2 of these scenarios, the endpoint being the same but the physical means (modems / routers) are different.
Example:

Trunk1 with modem / router 1:
PABX IP: 10.20.1.2
Gateway: 10.20.1.1
Endpoint: 10.50.1.1

Trunk2 with modem / router 2:
IP PBX: 10.30.1.2
Gateway: 10.30.1.1
Endpoint: 10.50.1.1

is it possible to configure this scenario using sip or pjsip without having the need for another asterisk as a gateway?

Asterisk does not impose any limit on the number of trunks and whatsoever, but you need to plan your network(s). I’d prefer the new pjsip stack as there are more options to finetune the connection.

As I read the question, the problem is that the same IP address is used by two different peers. TCP/IP just wasn’t designed to work like that.

It would have helped if the OP had highlighted the feature of configuration that was the problem.

The description of the problem is not specific enough and I don’t know what is exactly meant by “Endpoint.” That said I have a couple of trunks on a box at a customer site where the IPs are the same and the accounts are distinguished only by the account data, i.e. a single routing device is sufficient.

The downside is that all SIP headers must be exactly as the service provider says, while with a single trunk misconfigurations are largely ignored. As said, there’s not enough info here to look at the details.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.