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

We should show RTP public IPs as well as SIP #228

Open
davehorton opened this issue Apr 5, 2023 · 1 comment
Open

We should show RTP public IPs as well as SIP #228

davehorton opened this issue Apr 5, 2023 · 1 comment
Assignees

Comments

@davehorton
Copy link
Contributor

Sometimes, a customer will want to whitelist our media addresses as well as our signaling addresses. Currently, we show a list of the SIP signaling addresses under the link "Have your carrier whitelist our SIP signaling IPs"

We should change the link wording to " your carrier whitelist our IP addresses", and then the list should contain both the SIP and RTP addresses, with the SIP addresses shown at the top of the list and RTP at the bottom, like so:

34.27.113.10 (SIP)
5.55.11.88 (SIP)
5.46.22.65 (RTP)
34.33.23.6 (RTP)

@xquanluu
Copy link
Contributor

xquanluu commented Apr 6, 2023

Hi @davehorton we have sbc-inbound and sbc-outbound.

Both of them are using rtpengine on the same machine that they are runing on. So Sip and RTP should the same IP.

For now We just show sbc-outbound IP addresses only. we are missing sbc-inbound as a source of RTP packages.

Should we add sbc-inbound IP address to sbc_addresses table?

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

2 participants