| 1 |
On 12/23/18 8:21 PM, Grant Taylor wrote: |
| 2 |
> I'm guessing that you need to get voice messages as attachments from the |
| 3 |
> VoIP PBX, 192.0.2.123, to the corporate email server, 203.0.113.234. The |
| 4 |
> problem is the site-to-site VPN only allows 198.51.100.0/24 and |
| 5 |
> 203.0.113.0/24 to communicate. Meaning that the site-to-site VPN won't |
| 6 |
> pass traffic from the VoIP PBX. |
| 7 |
> |
| 8 |
> Here's an important question: Does the VoIP PBX have a default gateway |
| 9 |
> configured? Or does it /only/ know about the voice VLAN, 192.0.2.0/24? |
| 10 |
> Because if it doesn't have a default gateway, then (what it knows as) |
| 11 |
> the mail server will have to be local to the voice subnet. |
| 12 |
|
| 13 |
Was a little hasty posting... |
| 14 |
|
| 15 |
Yes the new server emails voice messages as attachments. It also does |
| 16 |
things like tracking staff status (in office, away, etc) and so it has |
| 17 |
other notifications relating to that and some other features. |
| 18 |
|
| 19 |
The VoIP PBX has a gateway; it is using sip trunks to provide phone |
| 20 |
service. However, it will be severely locked down on install, I will |
| 21 |
only let it talk to the sip trunk provider and its update server and |
| 22 |
nothing else. |
| 23 |
|
| 24 |
Dan |
Archives