Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to select from one trusted IP to different untrusted upstream SIP-Trunks #21

Open
khorsmann opened this issue May 22, 2019 · 3 comments
Assignees

Comments

@khorsmann
Copy link
Contributor

khorsmann commented May 22, 2019

Question:

I have an internal, central siprouter. That siprouter sends to the (in the example config) 10.1.1.4 the calls.
How can i select a other Upstream Trunk? It seems to me that is always an "pair" of Source-Target in the tables.

@Micro-Mike described the Trunking Szenario in Issue #9

For trunking mode:

In database file address the external (untrusted) and internal (trusted) IPs of the SBC are configured. Beside the external and internal IP the Mapping (ID 2001 and 1001) include the destination IPs of the Trunk. Trusted ID 2001 includes the destination SER, Asterisk, etc. in your core-network. Untrusted ID 1001 includes the external IP of your partner SBC, partner SER, etc.

Trusted:
1:1:10.1.1.4:32:0:NULL:Trusted, Core IP
2001:2001:trunk-[10.1.1.4]-[172.168.5.152].sbc:32:0:NULL:Internal-Trunk-Trusted

Untrusted:
101:101:192.168.1.4:32:0:NULL:Untrusted, Access IP
1001:1001:trunk-[192.168.1.4]-[193.22.119.66].sbc:32:0:NULL:External-Trunking-Untrusted

In dispatcher file the internal (trusted) connection ID (2001) is used to specify the destination SER, Asterisk, etc. in your core-network. The external (untrusted) connection ID (1001) is used to specify the destination IP of your partner SBC, partner SER, etc:

Untrusted:
1001 sip:193.22.119.66:5060 0 0 access=10.1.1.4:5060;socket=udp:10.1.1.4:5060;weight=100

Trusted:
2001 sip:172.168.5.152:5060 0 0 access=192.168.1.4:5060;socket=udp:192.168.1.4:5060;weight=100

In rtpengine.conf you can specify the internal and external IP the RTPEngine is using for RTP relay. This will also be linked with the IDs used in address table (trusted 1 & untrusted 101):

interface=1/10.1.1.4;101/192.168.1.4

Originally posted by @Micro-Mike in #9 (comment)

@adubovikov
Copy link
Collaborator

sorry, was a long week :-)

@adubovikov
Copy link
Collaborator

you can configure multiple hosts in the dispatcher and select it by round robin.

@khorsmann
Copy link
Contributor Author

@adubovikov that's right. I can insert multiple dispatcher targets with the same setid as target group.

Let me explain my question a bit more:

With the trunk config (not the reged one) there is IMHO an 1to1 relation between SBC-OS trusted ip and the untrusted upstream siptrunk.

So if I want to connect from the same SBC-OS trusted internal IP to different upstream Trunks I must use the same setid for all.

Or I setup more private trusted ips on the SBC OS.

is that the behavior SBC-OS config acts?

Target selection in trunk mode on diffrent trusted ips?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants