Mailing List Message #106166
From: Roberto Michelena <>
Subject: Re: PBX
Date: Sun, 04 Sep 2016 02:42:41 -0500
To: CommuniGate Pro Discussions <>
X-Mailer: Apple Mail (2.3124)

Thanks for the heads-up, but the thing is precisely that I’m entirely on a local network.
Now I begin to think it might have to do with the server not being aware of it’s own network address. And it’s something that has been ongoing on CGPro/OSX versions for some time now, I’ve just compared a fresh CGPro-OSX install vs. a Windows one. On the Windows install when you go into CGPro’s webadmin in the “settings” page it shows two addresses, and also the assigned LAN IP. But the OS X install only shows ; however if I kill (nowadays “unload”) the CGPro process on OS X and launch it again, it properly shows both addresses.
CGPro on OS X launches very early during booting, earlier than many of the OS’s own daemons and any app. It seems by the time CGPro is launched the OS has not yet acquired it’s address (even if static/manual!). Maybe there’s a way to introduce some delay in CGPro’s launch.

My planned architecture (as the hardware is already there) is to have all the VoIP on a Cisco 3560 PoE switch, and everything else as it is now, on a plain 3Com switch. And two network interfaces with the server, one connected to the VoIP network and one connected to the regular data network. So the CGPro server would actually have two LAN addresses, one foot on each network so to say. One interfase would deal exclusively with VoIP and the other with (as always) mail.
When I started configuring it that way, the log showed a lot of failures trying to register the phones, which improved when I changed the phone configs to look for the server by name instead of IP. But then still there were some messages like “invite rejected, originated on another network” or something like that, showing a valid address (of one of the networks) and really now I believe it was because of the server not being aware of it’s addresses. Will test further.


> Roberto,
> I have zero experience with CGP and VOIP, but I do have a fair amount of experience with SIP. If the clients you are using are using SIP, and you are having issues with one-way audio (especially) and/or no audio, that is (almost) always a NAT problem in my experience.
> You probably know all of this already, but SIP traffic is split into two parts, the session control and the actual audio/video payload (RTP). The session control uses port 5060, but the RTP is sent over a different port/ports, so if NAT is in the middle, you need to configure CGP and/or your clients to work around it. This normally presents in a few ways, but first, if the CGP machine is behind a NAT firewall, you’re going to need to tell it what its external address is, and also which networks are local and not behind NAT.
> If you have not already, try doing all of this in a simplified environment that has no NAT anywhere. Keep everything on the local LAN and see if that works. Then start adding complexity.
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster