| 1 |
On 12/24/18 8:40 AM, Grant Taylor wrote: |
| 2 |
> On 12/24/18 8:48 AM, Daniel Frey wrote: |
| 3 |
>> Was a little hasty posting... |
| 4 |
> |
| 5 |
> That happens. |
| 6 |
> |
| 7 |
>> Yes the new server emails voice messages as attachments. It also does |
| 8 |
>> things like tracking staff status (in office, away, etc) and so it has |
| 9 |
>> other notifications relating to that and some other features. |
| 10 |
>> |
| 11 |
>> The VoIP PBX has a gateway; it is using sip trunks to provide phone |
| 12 |
>> service. However, it will be severely locked down on install, I will |
| 13 |
>> only let it talk to the sip trunk provider and its update server and |
| 14 |
>> nothing else. |
| 15 |
> |
| 16 |
> Does "I will only let the VoIP talk to the SIP trunk provider and it's |
| 17 |
> update server" mean that the VoIP PBX won't be able to talk to the |
| 18 |
> intermediate mail server that you're talking about building? Or would |
| 19 |
> you also allow the VoIP PBX to talk to the intermediate mail server? |
| 20 |
> |
| 21 |
> This is a critical question as it determines if the intermediate mail |
| 22 |
> server needs to be in the same subnet as the VoIP PBX or not. |
| 23 |
> |
| 24 |
|
| 25 |
|
| 26 |
In that case I meant restrictions to the general internet; it'll only |
| 27 |
talk to the sip provider's IP and the update server IP. It'll have a |
| 28 |
separate rule to allow it to talk to the other vlan where the smtp |
| 29 |
forwarder will reside. |
| 30 |
|
| 31 |
Dan |
Archives