-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Burden,
Mike
Sent: Thursday, February 11, 2010 12:11 PM
To: Scott Lawrence
Cc: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Weird eyeBeam / NAT issue
> Did you really expect anyone to try to
> There was only one firewall that they did not find any security
> vulnerabilities in. :)
There is nothing more secure than a down firewall :)
___
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/arc
.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: Robert Joly ; sipx-users@list.sipfoundry.org
Sent: Thu Feb 11 12:51:33 2010
Subject: Re: [sipx-users] Weird eyeBeam / NAT
> -Original Message-
> From: Burden, Mike [mailto:m...@lynk.com]
> Sent: Thursday, February 11, 2010 12:52 PM
> To: Joly, Robert AVAYA (CAR:9D30); sipx-users@list.sipfoundry.org
> Subject: RE: [sipx-users] Weird eyeBeam / NAT issue
>
> > Reboots?! Yikes. I
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: Robert Joly ; sipx-users@list.sipfoundry.org
Sent: Thu Feb 11 12:51:33 2010
Subject: Re: [sipx-users] Weird eyeBeam / NAT issue
> Reboots?! Yikes.
> Reboots?! Yikes. If you go back to the old version of x-lite do
things
> go back to normal?
Yes, it does. The really bizarre part is that Counterpath says that
both are based on the same codestack. It's possible that there's
something that's correct in my X-Lite config that's wrong in my ey
> First, a little topology:
>
> Our sipXecs server is on a DMZ with the address
> 192.168.9.1/24. The firewall address on that DMZ (which is
> also the default route for the sipXecs server) is 192.168.9.254.
>
> We have a workstation on the firewall's protected network
> with the address 192.
> Did you really expect anyone to try to use that?
Wasn't expecting anyone to interpret the packet... I was mostly
checking to see if anyone could tell me whether or not what I described
is expected behavior on sipXec's part (if sipXecs is doing the right
thing, then there's nothing to debug!)
On Thu, 2010-02-11 at 11:47 -0500, Burden, Mike wrote:
>
> 00 16 35 a2 f8 22 00 90 fb 0d c0 fc 08 00 45 00 ..5..".. ..E.
>
> 0010 05 5a 82 c8 00 00 3f 11 4a 86 c0 a8 09 01 c0 6f .Z?. J..o
>
> 0020 1f 2c 13 c4 dd bc 05 46 51 74 53 55 42 53 43 52 .,.F QtSUBSCR
>
>
Good morning,
First, a little topology:
Our sipXecs server is on a DMZ with the address 192.168.9.1/24. The
firewall address on that DMZ (which is also the default route for the
sipXecs server) is 192.168.9.254.
We have a workstation on the firewall's protected network with the
addr
10 matches
Mail list logo
