tycho
Guru (not...)
- Joined
- Aug 9, 2011
- Messages
- 652
- Reaction score
- 272
I have finally been able to receive incoming calls to my Signalwire DID registered to my IncrediblePBX CentOS 6.9, "13.13" instance.
I have Enable TLS = yes and SSL Method = sslv2. That's correct, or necessary? It works...
I can seemingly ONLY pull this off if I set Allow Anonymous Inbound SIP Calls = yes and Allow SIP Guests = yes. I don't ordinarily ever do that. Is there a way around this that I might be missing? Otherwise, the PBX complains "WARNING,"Rejecting unknown SIP connection from [applicable Signalwire IP address]."" This happens even though I have added all Signalwire-related IP addresses to IPTables.
The PBX will also complain "WARNING[14423][C-00000000] chan_sip.c: Declining non-primary audio stream: audio 16662 RTP/AVP 0 101 13" even though the Signalwire and PBX codec settings are [I believe, and have checked] identical.
Bumping the above post containing a couple of questions (edited in the above quite from the original for brevity and clarity).
These are the IP addresses, obtained after asking in the Slack channel, that I have added to IPTables:
nslookup sip.signalwire.com
Non-authoritative answer:
Name: sip.signalwire.com
Address: 104.248.150.114
Name: sip.signalwire.com
Address: 178.128.235.81
Name: sip.signalwire.com
Address: 188.166.126.7
Name: sip.signalwire.com
Address: 159.65.244.171
Name: sip.signalwire.com
Address: 104.248.176.184
Name: sip.signalwire.com
Address: 167.99.198.84
Last edited: