Re: [pfSense] Fwd: Issue with states

2013-07-30 Thread Hannes Werner
Thank you for the answer, I've Outbound rules for quite some time without
success.
I added the qualifyfrequency option yesterday to my asterisk settings and
the peer registration last till this morning which is much longer than I
had since pfSense as router.

I hope it helps, but I will leave the outbound rules aswell. A one week
test should give stronger results.


On Mon, Jul 29, 2013 at 3:34 PM, J. Echter 
j.ech...@echter-kuechen-elektro.de wrote:

 Am 29.07.2013 14:45, schrieb Guido Falsi:
  On 07/29/13 12:06, Hannes Werner wrote:
  Thank you very much,
  I tried increasing qualify frequency without any success. I'm not on the
  site with that installation and I might be able to get there this
  afternoon.
  I'll give a feedback after some tests. Untill now I never had a
  registration for longer than 6 hours.
 
 
  I'm not sure this really fixes the problem...it seems to work for me
  though, so I shared it. YMMV.
 
 Hi,

 here it worked the following.

 go to

 firewall - nat - outbound

 switch from automatic to manual

 then there should be lots of rules created.

 on the first line add something similar:

 If-src-  src port-   dest.-
 dest. port-nat addr.-   nat port-static port
 WAN192.168.0.1/24udp/*sip provider   udp/*
 **yes

 src = subnet where asterisk sits
 dest. = provider ip (ask them to be sure)

 good luck
 ___
 List mailing list
 List@lists.pfsense.org
 http://lists.pfsense.org/mailman/listinfo/list

___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list


Re: [pfSense] Remote Digium IP Phone Provisioning via pfSense - Update!

2013-07-30 Thread Mark Tinka
Hi guys.

So just an update on this - it appears the issue is with 
Switchvox (confirmed with them and their partner as well).

Even though there is quite some documentation to suggest 
that the Digium phones can register to a remote Switchvox 
device, this isn't a supported method to do so.

Digium's solution is to pre-register a phone on a LAN 
segment, and then send it out to the remote site. Once it 
boots at the remote site, it will try to locate the 
Switchvox on the LAN and won't find it, and then present a 
couple of options, one of which is Keep Old Server. Once 
that is selected, it will locate the remote Switchvox via 
IP.

This seems to work, but has stability issues. 

It's a little weird, given X-Lite is able to register 
remotely with no fuss.

Seems like quite the mess from Digium.

Mark.


signature.asc
Description: This is a digitally signed message part.
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list


Re: [pfSense] Fwd: Issue with states

2013-07-30 Thread J. Echter
Am 30.07.2013 08:34, schrieb Hannes Werner:
 Thank you for the answer, I've Outbound rules for quite some time without
 success.
 I added the qualifyfrequency option yesterday to my asterisk settings and
 the peer registration last till this morning which is much longer than I
 had since pfSense as router.

 I hope it helps, but I will leave the outbound rules aswell. A one week
 test should give stronger results.


 On Mon, Jul 29, 2013 at 3:34 PM, J. Echter 
 j.ech...@echter-kuechen-elektro.de wrote:

 Am 29.07.2013 14:45, schrieb Guido Falsi:
 On 07/29/13 12:06, Hannes Werner wrote:
 Thank you very much,
 I tried increasing qualify frequency without any success. I'm not on the
 site with that installation and I might be able to get there this
 afternoon.
 I'll give a feedback after some tests. Untill now I never had a
 registration for longer than 6 hours.

 I'm not sure this really fixes the problem...it seems to work for me
 though, so I shared it. YMMV.

 Hi,

 here it worked the following.

 go to

 firewall - nat - outbound

 switch from automatic to manual

 then there should be lots of rules created.

 on the first line add something similar:

 If-src-  src port-   dest.-
 dest. port-nat addr.-   nat port-static port
 WAN192.168.0.1/24udp/*sip provider   udp/*
 **yes

 src = subnet where asterisk sits
 dest. = provider ip (ask them to be sure)

 good luck
 ___
 List mailing list
 List@lists.pfsense.org
 http://lists.pfsense.org/mailman/listinfo/list



 ___
 List mailing list
 List@lists.pfsense.org
 http://lists.pfsense.org/mailman/listinfo/list
ah i forgot to mention, set this rule on the first place. so it gets hit
first.

cheers

juergen
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list