I’ve gotta say, I had a lovely time at HPE Discover London. If you couldn’t make it to the event or just want to re-cap there’s a load of on-demand videos from the event here.
I’ve been to lots of Aruba Networks events but never HP/HPE. I was pretty impressed by the size of the event.. over 16000 attendees! But when an event is that huge you can’t really see everything, well I couldn’t anyway, it’s just too big. I know you can pick and choose the bits you’re most interested in (wireless I assume?) but I like to soak up as much info as I can and see what’s new in all areas.
It was good to see the Aruba Networks presence there. It wasn’t a huge presence in terms of floor space but they (Dominic Orr) featured in the keynote speeches which surprisingly a large number of people walked out on. Dom did stumble a little in his delivery, which is uncommon for him, so I guess this is why?? Anyone who walked out reading this, please comment why! Maybe it was when HPE tried to give away American Football tickets and were met with.. *tumbleweed*
In terms of technology, presentations etc. I found it really interesting hearing from the HPE Labs team. They’re working on “The Machine” which discards the traditional computer architecture model in favour of a model where memory and storage are one and the same things (amongst other things). The benefits according to the Labs team are “quantum leap in performance and efficiency, while lowering costs over the long term and improving security”.
It was good to see Aruba release their Aruba Beacons management product Aruba Sensor. I would imagine it was a bit of a nightmare
managing Beacons without this… The Sensor will manage 10 or so Beacons and piggy back on your existing wireless. It should be noted that your existing wireless needn’t be from Aruba.
Here’s a Sensor in the wild at the event.
To sums things up I really enjoyed my time at the event. It was great to see the direction that the company is heading & their new products. I hope Aruba features more heavily at the next event.
I feel I must add… In the interest of full disclosure, HPE invited me to go to this event as an Independent Industry Influencer and paid for travel, accommodation and a few little treats but this hasn’t influenced my opinions.
Not sure if this is an issue with all certificate authorities but I saw this particular issue with GoDaddy.
Guest wireless captive portal is secured using a certificate from GoDaddy. When mobile devices get redirected to the captive portal they get a certificate error like the one shown below.
This does not occur on laptops though.
The resolution for me was to include the intermediate certificate in the issued certificate.
Open the certificate in a text viewer such as notepad. Also open the intermediate cert in notepad. Now copy the intermediate cert text and paste it after the issued cert text. It’ll look something like this….
This post is about how to set up a Lync Server Mediation server to support Direct SIP whilst utilising Gamma Telecom SIP and a Sonicwall Firewall.
This is the way that I did it, you may choose to do it differently. Leave a comment if you got this working another way.
The reason why you need to configure 2 NICs on the Mediation server is because Gamma require the external IP address to be present in the SIP OPTIONS. Normally this isn’t a problem as many firewalls have a SIP ALG. In simplified terms this means that they NAT the SIP traffic so that it appears to come from your external IP address. Sonicwall can do this for SIP over UDP but not for SIP over TCP. Because of this and the requirements from Gamma it’s necessary to have an external public IP address on your mediation server.
There’s a great post here about how to setup Lync Mediation server with “Duel homed” NICs. You’ll need to do this, and as it’s such a good post I’m not going to re-create it.
You’ll also need to stick one leg of your Mediation server in a DMZ on the Sonicwall and configure the DMZ in Transparent mode. Another good post here detailing how to setup your Sonicwall DMZ to support this.
Here’s how your mediation server should look in the topology builder.
Here’s the Gateway.
And here’s the Trunk.
That should get you going.
Bye for now.