SIP Trunk cannot be established

[Hamsa]

Hi Team

Trying to configure a sip trunk with an unsupported provider. As per the provider authentication is IP based and provider has given below information's.

Ip 10.2.xx.xx
G.W-IP 10.2.xx.xx
Subnet 255.255.xx.xx
Signaling 10.197.4.xxx
Media 10.197.xx.xx
10.197.xx.xx
10.197.xx.xx
10.197.xx.xx
10.197.xx.xx

How to configure the SIP trunk with these details. Here signaling IP and media IP are different subnets. Is that fine with 3cx.
3cx is on premise installed on a windows operating system with2 NIC card. One is connected to LAN and the other is connected to ISP device (SIP line).

 

[Nathan@Voxtelesys]

One solution is to use a preferred provider, like Voxtelesys

But my best guess with the information you gave would be to use the "Ip 10.2.xx.xx" or "Signaling 10.197.4.xxx". Try both and see which one works. They are giving you both the signalling and media so you can allow them in your firewall on-premise.
It is surprising they didn't give you a DNS domain for redundancy, at some point this unsupported provider will need to do maintenance on the IP your trunk is setup for and it will need to go down unless they have something like an anycast network implemented. I believe most supported providers are pointing to a domain record.

 

[Hamsa]

Hi Nathan

Thanks for the reply, Unfortunately I do not have any supported provider here in Bahrain. So I need to allow both signaling and media IP in the firewall to 3cx server right?

 

[Nathan@Voxtelesys]

Depends on how restrictive your firewall rules are. If you cannot get connected with them or make a test call with audio, it is a completely plausible idea to try.