Not sure if I should post this in another section, but here goes:
Recently I've come across a very strange issue with one of my customers.
They have a SIP-solution in place, which, after I set up a new firewall
running 5.2.3 (the same that had the in...
Greetings! I've recently come across a strange issue with two different
Fortigate-boxes, both running 5.2.2. On both of these, I am unable to
connect the built-in client on iOS to the iOS Wizard-created IPSec
VPN's. On a third box, also running 5.2.2...
Well, that didn't work too well. Did a set default-voip-alg-mode
kernel-helper-based at the LANA-location, with the net result that the
phones shut down completely both inbound and outbound. Changed it back
to Proxy-mode and it came back up. Back to ...
Came across two rather interesting Knowledgebase-articles about SIP and,
more specifically, SIP-processing on 5.2. SIP and SCCP Traffic is
handled by the VOIP ALG/Proxy by default in FortiOS 5.2
(http://kb.fortinet.com/kb/documentLink.do?externalID=F...
New update: Did some packetcaptures on the Fortigates in question when
an incoming call comes through, and found something very odd: The
analogue SIP-adapter (an AudioCodecs MP-112FXS) at LANB is the one
sending a BYE to the Aastra-unit after 32 seco...
I'll definitely keep you posted :) I plan to do a reboot of both the
handset at LANB and the Aastra-unit during the weekend, and then test
again on monday. Also had a co-worker check up on the policies just to
check that I hadn't gak'ed up things, bu...
