Wednesday, October 07, 2015

Porting numbers in Skype for Business Online

Today, Microsoft announced additional preview options in S4B Online.  One of which is number portability.  This is a huge step towards adoption - we can now tell customers we can port existing PSTN numbers to the Microsoft cloud.

Here's how it works:
  1. Log into your Skype for Business Admin portal in office 365
  2. Click on Voice, then "Port Orders (preview)"
  3. Note the text - you will need a list of numbers, 999 maximum per order, your account info, your letter of authorization, and a PIN if applicable.
  4. Click on + to add a new port order
  5. Note the text warning here
    To minimize delay in your transfer:
    - Please remove any features (i.e. Hunt Group) associated with your numbers before submitting your order.
    - Please do not place any new service orders with your current provider.
    - All numbers must be from the same carrier and under the same account.
    - You cannot transfer toll free numbers or numbers used for data (i.e. DSL lines).
    - Make sure the account information matches exactly what your carrier has on record. Mismatched information is the most common cause of errors.
  6. Complete your account info
  7. Enter your phone numbers, one per line - these need to be in E164 format!
  8. Select your transfer date.  Not sure if they will really get it done in 5 days, but that's was the choice I made.
  9. Digitally sign your letter of authorization
  10. Submit your port order!

I will be working on porting some numbers for real sometime very soon, but wanted to get this post up to show how it's done.  I will update this post as we gain more experience.

More technical detail is available here

Thursday, September 17, 2015

Spin up quick labs in Hyper-V

Wrote this a few days back to script spinning up VMs to test in lab.  Not putting on TechNet, but if you use it and have recommendations, please post in comments.  Using the lab build from @expta, I was able to get 6 VMs in about 8 minutes ready to go!

$vmpath = "c:\virtual machines"
$vmswitch = "LAN"
$templatepath = "c:\templates\w2012r2-template-sysprepped.vhdx"
$servers = ("fe1",
Import-Module BitsTransfer
$servers | ForEach {
    Write-Warning -Message "Copying VHDX and setting it to RW for $_"
    Start-BitsTransfer -Source $templatepath -Destination $vmpath\$_.vhdx -Description "Copying $_ VHD" -DisplayName "Copying $_ VHD"
    attrib -r $vmpath\$_.vhdx  # Recommend your template being RO so you don't lose it!
    Write-Warning -Message "Creating and Starting Virtual Machine for $_"
    New-VM -Name $_ -VHDPath "$vmpath\$_.vhdx" -MemoryStartupBytes 2GB -generation 2 -SwitchName $vmswitch | Out-Null
    Start-VM -Name $_ | Out-Null

Tuesday, August 25, 2015

Skype for Business Server 2015 Protocol Poster 24x36

One of my favorite things Microsoft has done for every flagship product was a Visio and PDF poster, suitable for framing.  It really was handy with Lync as the number of protocols and workloads got higher, it was great to have a reference.

Here's a picture of my Lync 2013 poster in my office today - I've had this for almost 3 years now!

So of course, earlier this year, Microsoft released a new poster for Skype for Business and while not much technically had changed, the format became seven 8.5"x11" pages.  The information was great, but the change in format made this a reference document in my download folder instead of an actual poster.

I posted on Twitter about my disappointment when Microsoft released the new poster download.
Recently posed with the decision of buying a frame for my Lync 2013 poster or not...   Something clearly had to give, so I grabbed the Visio and got to work.   The download link below for the poster will get you both the Visio and a printable PDF.

I have found a semi gloss printing option for $25 here.  YMMV!


Here's a preview image of the poster:

If you print and get it hung, send a pic!  Tag me on twitter @chrislehratx!

This one hangs at Polycom Austin:

Friday, July 10, 2015

Parse-TransportLogs - Which IPs on my network are sending SMTP through that connector?

I get asked this at some point in almost every Hybrid migration. The answer is always to turn up your SMTP logging to get those details. The problem is that parsing that data is difficult. Unlike an HTTP log where each hit was a transaction, SMTP logs contain the entire SMTP conversation, so one transaction can be 10-30 lines in an SMTP log file.

Additionally, SMTP logs store the remote-endpoint as a single field of IP and Port.

This script takes *.log from the directory you specify, and will search for lines containing "Queued" - meaning an email was accepted by the connector and write those to a temporary file.  Then it will parse the data, the Top client IP addresses along with a count!

Depending on the size of your log file data, this can take some time to run!

Download today from the TechNet Gallery!

Wednesday, July 08, 2015

SIP DHCP Option 120 DeMystified

On the surface, Option 120 seems simple - it's the Pool FQDN, encrypted.

Everyone knows to run the DHCPUtil.exe -sipserver and it spits out a long hex value for you.  Option 43 is a little fancier, and gets more press.  Option 120 seems straightforward in comparison.  What if I asked you to create the hex code without DHCPutil?  Sure sounds easy, you take that FQDN, run off to your local hex to asc convertor and punch in your FQDN, you get a non-human readable string, and you set your DHCP options.  Done and done -  What do you mean it's not working?

So, reading through RFC3361 (as I am known to do in front of the fireplace, pouring over dot-matrix printed copies, burning the parts I have already committed to memory) we learn that Option 120 has a VERY particular format.

That format can be seen below - where "##" is the hex code for the length of the ASCII section following it.


That's confusing, but for a machine with limited CPU/RAM, that's a pretty sweet input.

So, let's un-Lync this for a minute and pretend our SIP server was Keep in mind, the 00-FF range is 0-255 characters in each section of the FQDN.  I don't know a TLD above 10 characters, but I guess they really wrote this code openly!

Section Characters Hex Code
www 3 03
bing 404

I'll avoid the haiku here but the encoding for this would look like:

00 03 HEXCODE(www) 04 HEXCODE(bing) 03 HEXCODE(com) 00

Or this (bolded the Hex count codes)
Armed with information, I began working in Excel to make it so I could build these codes without having RDP to a Lync or S4B server available to me, or from a place where I might not have DHCPUtil.exe access.

Taking an input in Excel using the FQDN, you need to do some fair complicated text manipulation to break down the sections, perform the ASC to Hex conversions and concatenate the text.  I am pleased to report that in my search for this code already existing, I was able to find this Design Document Generator written by Alessio Giombini.

I have taken the tab and modified it some to release it separately to you here.
Download from the TechNet Gallery!

Here's a quick Office Mix I made on this.

Tuesday, June 30, 2015

Seven Office 365 Video success tips - you won't believe number five!

I have recently begun using Office 365 video more for internal and customer shared videos.  It's been fairly successful and I wanted to give out a few lessons learned for those also working on Office 365 video adoption.
  1. You can not choose your title image - because of this, you NEED to make sure that frame 1 of any video has the title screen you want.  If that's a video of you, or an title page of a PPT so be it. Depending on how you record your video (Office Mix versus a Lync/Skype for Business Recording) you may not be able to set frame 1 without video editing tools.  If you use Lync/S4B - I recommend sharing a title screen/image prior to hitting record to ensure frame 1 has content shared.
  2. Office mix audio levels - I have already submitted this feedback to the Office Mix team.  (if you are not familiar)  When you record from a slide recording, you are able to select your audio recording device of choice.  When you record a screen recording, you are not able to, and default device is used.  If you have multiple headsets/devices for audio this might be an issue.
  3. Upload and processing times - they are not the quickest in terms of other video hosting services for upload nor processing time.  Expect time there.
  4. Sharing - Recently, sharing embed code for Office 365 videos was announced, and this works quite well in SharePoint - but the user watching the video needs to be signed into YOUR Office 365 tenant for the video to load currently. Choosing Insert->Video and Audio->Embed and paste the embed code proved by Office 365 video there. There is no "anonymous" sharing at this time.  If you are playing with Mix, there is an anonymous or private link sharing for the Mix upload service, I think that is where this traffic should be driven at this time.  Also, the other sharing options are Yammer, which works as expected, and Email, which at this time is a "mailto:" hyperlink which is a pretty weak implementation at this point.
  5. SharePoint Taxonomy - At this point there is no taxonomy integration.  You are not able to tag videos for easy search.
  6. Descriptions - Within the description section, there is no real formatting control.  It doesn't seem to take HTML, RTF or properly formatted text for a CR/LF no matter what.  Nor links or other relevant data.
  7. Versioning - If you want to overwrite/update a video, be SURE to name it the same filename as the current video's title and upload.  Office 365 video should see this and ask if you want to replace or create new.  If you choose replace, the video links and/or embed code you have previously utilized should continue to work (similar to uploading a new Office document to a SharePoint library)

I will add/update additional information as I learn more or as the service changes.  Thanks for reading!