Thursday 10 January 2019

Microsoft Teams client automatically sets itself as the default chat and calling app in Office

Hello readers.  Happy New Year!  Hope you're well.

Ultra quick post today.

I noticed today that Outlook wasn't displaying presence for some people when it usually does. I checked the Skype for Business client (you know, not Teams, the other one ;) ) and I could see presence. So I found someone in Outlook that showed their presence and I moved the mouse cursor over their name to get the calling card popup.

Then I clicked the speech bubble to start an IM. Curiously, it opened Microsoft Teams instead of starting a new Skype for Business chat.

So I went one further and opened the contact card and expanded the ellipses menu to start a call.

And again, the Microsoft Teams application opened and started a call to the number. The call failed in my case since I don't have the Phone System license currently.

I didn't remember changing any associations for IM or Tel or Callto protocols, but thought I would check.  System settings -> Apps -> Default Apps - scroll down to the bottom.

Click on Set defaults by app and scroll down to Teams and click Manage

This opens the File type and protocol associations for Teams. Mine was largely set to choose a default.

I changed IM to Skype for Business and I closed and reopened Outlook. Tested again and IM still opened Teams.

I repeated with Callto and TEL and the same happened.

I remembered seeing a tick box in the Microsoft Teams client. Open Teams and click your photo and settings.

Under General, there is a tick box for Register Teams as chat app for Office.

And it was ticked. I didn't remember ticking this. I still use Skype for Business as the default for IM and calling and I use Teams for collaboration and some meetings and calling. At least for now.

I un-ticked this and restarted Outlook and tested. And low and behold, I was back to using Skype for Business for chat and calling.

A few things to think about here. 

  1. Somehow, this got ticked by itself. I didn't do it.
  2. Although it says default app for chat, it also means presence and calling.
  3. It overrides the Windows settings for default apps by protocol
It seems I'm not alone. I posted the question on Twitter and got a reply straight away that 'loads of users reported that this got automatically ticked' and 'that none of the users were TeamsOnly'.

I do mind that this got ticked by default, but I can live with that. I would love for the controls to be more granular. For instance, tick boxes for default app for chat, calling and presence in Office.  

I would also like to know how this one tick box controls the app behavior. I also looked in the registry, by the way, and none were set to Teams. If you want to know how, check this post by @shawnharry.

Would love to know if you have any thoughts and comments. 

That's all folks.


Thanks for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome. 

Monday 20 August 2018

Skype for Business Server 2019 management shell missing terminator

Hello readers,

Hope you're well.

A really quick one this time.

If you've been working with Microsoft UC server products as long as I have you'll no doubt be familiar with this one.  I've seen this error with every product since Lync 2010.  I don't know if it was present in OCS or LCS before it.

The problem
You go to open the Skype for Business Server Management Shell and you get an error on opening.
The string is missing the terminator: '. 
       + CategoryInfo                 : ParserError: (:) [], ParentContainsErrorRecordException
       + FullyQualifiedErrorId   : TerminatorExpectedAtEndOfString

The error doesn't stop you using it.  It is annoying, however and deserves to be fixed.  This is in Skype for Business Server 2019.  You'd expect it to have been fixed by Microsoft by now.

The cause
The reason you get the error is because when the shortcut was created it used a "Target Path" which was truncated from the full path.

Typically, the path looks like this
C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "cd $env:UserProfile; Write-Host 'Loading Modules for Skype for Business Server 2019...'; Import-Module 'C:\Program Files\Common Files\Skype for Business Server 2019\Modules\SkypeForBu

It should look like this
C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "cd $env:UserProfile; Write-Host 'Loading Modules for Skype for Business Server 2019...'; Import-Module 'C:\Program Files\Common Files\Skype for Business Server 2019\Modules\SkypeForBusiness'"

Clearly, this is missing the end of the word Business, an apostrophe and an end quote.

The problem is, that's too many characters for the field which is limited to just 259 (odd number) characters.

In the Lync days it was cased by the missing quotation at the end rather than number of characters (since Lync is a lot shorter than Skype for Business).

The solution
Shorten the path while completing the module name and including the terminators, of course.

All you need is siness'"

My suggestion is to remove the word "server" and remove one of the "." at the end of the Write-Host statement.
C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "cd $env:UserProfile; Write-Host 'Loading Modules for Skype for Business 2019..'; Import-Module 'C:\Program Files\Common Files\Skype for Business Server 2019\Modules\SkypeForBusiness'"

This saves you enough characters to let you finish the statement.

How to do it
You need to open up the properties on the shortcut.

Browse to 
%AppData%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar

Right click on the shortcut and click properties

If, like me, you pinned the shortcut to the taskbar.  Right click on the icon, then right click on Skype for Business Server Management Shell and click properties.

This opens up the properties page

As you can see the Target field has the truncated statement ending in SkypeforBu.

Paste in your new, shortened target
e.g. C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "cd $env:UserProfile; Write-Host 'Loading Modules for Skype for Business 2019..'; Import-Module 'C:\Program Files\Common Files\Skype for Business Server 2019\Modules\SkypeForBusiness'"

and click apply and OK

Now click on the shortcut to open the management shell

That's all folks.  Hope this helps.


Thanks for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome. 

Thursday 2 August 2018

Skype for Business Server 2019 hybrid features

Hello readers.  Hope you're well.

Now that Skype for Business Server 2019 has landed in preview, there are a few (very few) new things you can configure.  There aren't really any new "features" in Skype for Business Server 2019 (Preview).  Skype for Business Server 2019 is all about hybrid with Office 365.  This means you can use services in Office 365 for your on-premises topology and users.

The two most notable (only) features are Cloud Voicemail and the Call Data Connector.

Cloud Voicemail 

Cloud Voicemail is the voicemail service for Skype for Business Online users with the Phone System add-on.  It is hosted in Azure alongside Office 365.  It is the only voicemail option for Skype Online users.  As in, it isn't possible to use Exchange Online or Exchange Server Unified Messaging (UM) as the voicemail service for Skype Online users.  The reason is because Microsoft is finally deprecating the UM role from Exchange Server.  

Some background

Exchange Unified Messaging has been around since Exchange 2007.  It is used by a LOT of companies as the voicemail service for OCS, Lync and Skype for Business.  It is even used as the voicemail service for some PBX vendors.  I see a lot of Cisco campuses using Exchange UM for voicemail instead of Unity.  

In its simplest form, UM allows callers to record a voicemail message for users.  This voicemail is sent as a media file to the users mailbox.  The recipient can listen to that message in a number of ways:

  • Outlook (Desktop) using integrated playback controls, either through PC speakers or on your desk phone (Play on Phone).  You can also get voicemail preview, which attempts to transcribe the message using speech to text.
  • Play on Phone deserves a separate mention because what this does is call you back.  If you use Skype for Business, UM calls your SIP address.
  • Lync or Skype for Business client.  You get a "visual voicemail" feature similar to the experience on a smart phone.
  • Mail client on a smart phone that is capable of playing the attached media file.
  • Outlook Web App which also has integrated playback controls.
  • Dialling from a desk phone.  You can dial the pilot number or just hit the dedicated voicemail hard key.  Some desk phones also have a dedicated voicemail tab or soft key that takes you to a list of voicemails.
  • You can also play a saved voicemail media file using your favourite media playback app.
More than just Voicemail
UM can do a lot more than just record a voicemail and send it as an email though.  It also includes a bunch of features that I don't often see used.  Auto Attendants, Call Answering Rules and Outlook Voice Access are a great example of such features.  

I've set up Exchange UM Auto Attendants for companies previously and used it instead of the Response Group Service in Lync.  It does work well, but most Lync and Skype orgs (probably) use RGS.  Remember, however, that Exchange UM isn't just for Skype for Business.

The one I don't think I've ever seen used is the Call Answering Rules.  Call Answering Rules are a way for a user to choose how calls are handled if they don't answer.  You're saying that's simple, it goes to voicemail right?.  The answer is if that's what you want to happen.  You can also configure a rule to transfer the call or try to find you.  You can also configure additional granularity for what happens when you get calls.  Apply to all calls or just calls from certain people or just when your out of office is on.  The list goes on.  You're also saying that you'd usually get the user to configure what happens to their calls in Skype for Business, right?  Well, yes, to a point.  You can configure additional call routing in Skype for Business.  You can configure Call forwarding or Simultaneous Ring to contacts, telephone numbers, team call groups or delegates.  UM kicks in if you have none of those configured or if you do, but the last action is transfer to voicemail.  Call Answering Rules start when the call leaves the telephone system (Skype for Business, Cisco etc) and hits your Unified Messaging mailbox.

Outlook Voice Access is a feature that is only partially used if at all.  Outlook Voice Access (OVA) allows you to call your voicemail from a phone.  You can either dial the pilot number and enter your extension and (Exchange UM) PIN when prompted to authenticate you or hit the voicemail key on your Skype for Business desk phone to go straight in.  It is common to use OVA to listen to messages and even change your greeting.  What's less common is using OVA to read your emails to you or list your calendar appointments or to access contacts.  

The reason is simple.  Exchange UM was launched in Exchange 2007.  That was a simpler time, before modern day smart phones.  I had many of the predecessors to modern day smart phones.  I had a Nokia 9110 and a 9210 (look them up) and a Compaq iPaq and then several Windows Phones, I think mostly HTC.  I could get access to email and calendar using Active Sync or similar on all of those.  Blackberries and Palm Pilots were also being used by some, but it wasn't that widespread.  OVA reading emails and calendar appointments was a way to let people with "dumb phones" get at their info on the move.  Once the iPhone 3G was launched in July 2008 (10 years ago) with Exchange Active Sync support, that was it for OVA's advanced features.  They have remained in the product since then because why not.

Many Lync/Skype for Business pro's think voicemail should be native to Skype for Business rather than in Exchange.  UM in Exchange made sense because it was also used by PBX's though.  Unless voicemail was made a role in Skype for Business and it could be used by PBXs in the same way, that is.  Maybe Microsoft missed a trick here.  It could have been a way to get PBX houses to have Lync or Skype for Business installed.  If they used it for voicemail on the PBX and that's all, we could have reminded them that they had access to the desktop client and IM etc.

As I said above, Exchange Server 2019 (Preview) doesn't have the UM role.  Right now, Exchange Online is based on Exchange Server 2016, which does have the UM role.  Before long, Microsoft will be upgrading Exchange Online to 2019 and thus killing the UM role in Office 365.  Now remember, Exchange Online UM can be used by Skype for Business Server and PBXs as voicemail.  For PBXs, however, time is running out.  Microsoft announced that they were discontinuing support for session border controllers to connect PBXs to Exchange Online UM over a year ago.  The initial deadline was July 2018.  This has been extended in April 2018 from July 2018 to to April 2019 to give people more time to prepare and find an alternative.  This, too, is clearly a precursor for UM being dropped from Exchange.

This is a way to give your on-premises users a voicemail service when they have no other options.  i.e. after they have upgraded to Exchange server 2019.


Call Data Connector

The Call Data Connector is a new feature in Skype for Business Server 2019.  It is a connector that pushes call data to the cloud service so that you can leverage the Skype for Business Online Call Analytics (CA) and Call Quality Dashboard (CQD) tools.

Call Analytics is a new(ish) feature in Office 365 that was the result of the acquisition of certain assets from Event Zero.  It is a portal that gives you access to call history and call detail records for users in Skype for Business Online with of without Phone System.  You can get to the Call Analytics dashboard using a dedicated URL - 

...or from the User form within the Skype and Teams Admin Console (STAC) - that's what I call it anyway ;) at

The Call Quality Dashboard is a dashboard that gives you complete insights into call quality overall.  Basically a series of graphs that show different metrics.

You can get to the Call Quality Dashboard from the STAC at

...or a direct link here -  It opens in a new page and asks for you to sign in again.

Some background

Lync and Skype for Business server have a role called the monitoring role.  This collects call detail records and sends them to a SQL database.  You can use SQL Server Reporting Services (SSRS) in conjunction with the monitoring reports to get at that CDR data and produce reports.
You can see usage reports to find out how used the system is or you can use it for troubleshooting failures of, not just calls, but all communications.  

There is also a dashboard view.

The monitoring reports have remained largely unchanged since they were introduced.  The thing is, you don't rely on Lync/Skype built-in monitoring reports as a stats tool in the same way you did a call logger like Proteus or Oak.  The reports do give you insights, but I would say it is more for admins to troubleshoot and do inventories than for call centre managers.  Since the data is just logged in SQL it means that it is possible to extract that data and use another application to slice and dice and produce reports that are meaningful to managers.


Stay tuned...

Stay tuned for part two or possibly two and three where I go though configuration steps for both Call Data Connector and Cloud Voicemail.

I was hoping to include it here, but I'm having all kinds of problems with Cloud Voicemail.  Perhaps I'm trying to do too much too early.  After all, it is a preview. 😉


Thanks for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome. 

Wednesday 11 July 2018

Microsoft Teams Federation is here, sort of

Hello Readers,

Hope you're well.

This post is going to change a lot in the coming days/weeks so you will probably want to keep checking back.

One of the features that everyone is waiting for for Teams is Federation.  That is the ability to communicate with people outside your organisation.  When I say communicate, I mean presence first and foremost, chat (instant messaging), audio/video calling and sharing.  I know you can already do this if you set up a meeting with someone outside, but this isn't federation.  This works because you invited external people with an email address (MPN) to your meeting.

Federation has been in Microsoft UC since Messenger in Exchange 2000.  In Skype for Business you can turn federation on and off and create policies, allowed domain lists and even federate with non Lync/Skype for Business contacts using Consumer Skype or Cisco Jabber for instance.  

With federation enabled, you can add external contacts using Lync, Skype, Skype for Business, Jabber and more to your contact list and see their presence and easily start an IM with them or escalate to add audio or video over the internet.  To say that federation is ubiquitous is an understatement.

Federation in Teams

The title of the post suggests federation is available in Teams.  And it is, sort of.  Once again, this post will change as more becomes available.  But some things work.

What's works now - 11th July 2018

Presence in Skype for Business of a Teams user.  If you tag a user for status change you'll see immediately when the user signs into Teams or becomes available.  

Sadly, presence information isn't exchanged between two Teams users.

Calling, both audio and video, works between Teams users in different organisations.

I tried this in a few scenarios.  
  • Teams desktop client to desktop client works
  • Teams desktop client to mobile client works
  • Teams desktop client to browser client (Edge) works to start with, but the session crashes in Edge shortly after the call starts.  Desktop client thinks it is still in the call until the Edge client is back in.  Then it says the call failed and gives you a rejoin link which clearly doesn't work.

Teams to Teams doesn't work.  You actually get an error message

Skype for Business to Teams does work.  
In Skype for Business (Server), double click on a Teams contact who is only signed in to Teams to start a chat.  Send a message.  There is a delay of up to 30 seconds, but it eventually pops up in the chat window in Teams.  It actually pops up as a new chat, separate from the one between Teams accounts and the contact has a little Skype for Business logo on it.

The failed message was because I closed the Skype for Business chat window too early.  As I said, there is a delay between sending and receiving of upwards of 30 seconds.  Once I did see that the message had been received I started a new chat from Skype for Business to Teams and was able to chat in both directions.

Another word of warning.  The chat session can time out it seems.  If you leave the chat open between Skype for Business and Teams and do nothing while you write more of a blog post, then go to Teams and send a new message, it will fail with the same error.  If you send a new message from Skype for Business it first appears in Teams as a peek and then pops into the same chat window.

Teams to Skype for Business doesn't work.  This is probably because I'm testing between an account with Teams and Skype Online to an account with Teams and Skype for Business Server.  More likely it is because Teams to Teams doesn't work.  

I also tested a new chat to someone I know that has Skype for Business Online but not Teams and that failed.

And lastly, I tried a chat between Teams and a Skype for Business server account only (no Teams).  And that failed.

How do you chat to an external contact?
Type their SIP address into the address bar of a new chat.  You'll get a message saying that "We couldn't find any matches" and it offers to let you search externally.

Once you click on the Search externally message it opens up a chat window.  It said that the contact is external and that some Teams features won't be available.

What do you need to do to enable?
The answer is External access.  If you browse to the Skype and Teams Admin Centre (STAC) aka Microsoft Teams and Skype for Business Admin Centre (MTSBAC) and expand Org-wide settings and click on External access, and make sure External access is switched on.  I also switched on external Skype users.

Sadly the Learn More link goes to a 404 not found. 

But it does include links to a couple of useful posts.

This one says to enable External Access and wait 24 hours.

This one says enable external access and add a domain (which isn't in the admin centre).

More to considerWhen two Teams users in separate tenants/domains are communicating with each other they can only use Teams features that are turned on in both organisations.  
I'll update this post when I know more.  
Go and test.  I'd love to hear how you get on.


Thanks for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome. 

Tuesday 26 June 2018

How to: Configure Microsoft Teams Direct Routing with Anynode SBC

Hello readers,

Hope you're well.

This is the first follow up to my post on configuring Microsoft Teams Direct Routing.  In this post I'll take it one step further and show how to configure an SBC for Direct Routing and a VoIP provider.  

I said in my last post that I wanted to write posts on any SBC I got my hands on.  I'm starting with an SBC I've blogged about before, Anynode from TE-Systems.


I covered all of this in my previous post, but just to summarise.  Direct Routing is Microsoft's name for On-premises Call Handling (OPCH) for Microsoft Teams using an SBC.  Its a way to connect Teams in Office 365 with on-premises lines and PBX systems.  

Once configured, Direct Routing enables users homed in Teams to call the PSTN through existing telco lines or SIP trunks on-prem or to make or receive calls to/from users on a connected PBX.  This is a much simpler version of how we configured this for Skype for Business Online with Phone System (Cloud PBX) which also needed a variant of Skype for Business Server on-prem.

On with the show!

Configure an Anynode SBC for Direct Routing and a VoIP provider

At this point I'm going to assume that you have Direct Routing configured in Office 365 and you have a gateway, PSTN Usages, Voice Routes and Voice Roputing Policies which are assigned to your users.  If you don't, go to my previous post and follow the steps.  I'll wait ;-)

I'll also assume that you already have your Anynode SBC installed and running.  It is very simple and can be summarised as download, double click, next, next, finish.  No really, that's just about it.

Once installed just browse to the Web UI.  Click start and find "anynode frontend" in the list.

Or open a browser and browse the default URL http://localhost:8088.  

Log in with admin and the password you configured.  This will open up the dashboard.  Your Anynode will be completely default with no configuration entries.

Now click Configuration Mode

Now click Wizard

And choose the template "Microsoft Teams Direct Routing and VoIP Provider" and click next

Now click configure

Create a new network controller.  Choose your NIC and IP if you have multiple... 

or "any" if you only have one interface.

Specify your TLS port.  The default in Anynode is 5067.  This is the port that the Anynode is listening on for SIP connections from Microsoft.

Be sure that you use the same port you used when you configure your PSTN Gateway in PowerShell.

e.g. New-CsOnlinePSTNGateway -Fqdn -SipSignallingPort 5067 -MaxConcurrentSessions 10 -ForwardCallHistory $true -Enabled $true -MediaBypass $true

Now configure your certificate and private key.

If you already have a certificate you want to use you can import here.  You can also create a certificate signing request to give your certificate issuer when placing your order for a new certificate.

Complete your details including common name and address etc

Add additional subject alternate names or leave as the default.  By default, Anynode adds the local IP address you have configured in the CSR along with the common name.  Click next to continue

Configure the key length.  The default (and minimum) is 2048 bit.  Click next.

Here's the summary of the CSR.  Click download to save a copy of the request file on your local PC.

Once you have downloaded, click finish.

If you can order and obtain a certificate in a few minutes, congratulations!  Simply import it here.  I went away and ordered the certificate and it took a little while to verify and get back.  Of course the browser session got bored waiting and timed out to the login screen.  So just repeat all the previous steps except for generating a CSR.  

Just tick import and click next.

When I received my certificate I used the DigiCert certificate tool to install it, them I exported it to a file with the private key and the certificate chain to a single pfx file.

Click choose files and browse to your certificate file.

Once the certificate is imported, a summary of the certificate is displayed.  Check the details and click next.

If your certificate file doesn't have the certificate chain intact you can click request chain to obtain it.  Otherwise click next.

Now configure your SBC FQDN.  Anynode guesses what it should be from the certificate you created.  If you created or imported a wildcard cert, enter the correct name here. This is the name you will use when you configure your Online PSTN gateway.

Configure any incoming and outgoing manipulations here.

Now give your node a name.  It is a good idea to make them descriptive enough so you know what your looking at later if you have multiple.  In this case leave it as the default and click next.

Here is the summary of your new Direct Routing node.  Check it over and click next to configure your VoIP provider.

Click configure to add a connection to your VoIP (SIP trunk) provider.

In my case I use Sipgate.  Select your provider from the list or other if your provider isn't in the list and click next.

TE-Systems periodically add new provider templates to the list.  If you don't see yours and think you need to use it a lot, ask your account manager and they may add it in a future version.

Now create a new network controller for your SIP connection and configure it as before.  If you have a dedicated link to your provider make sure you choose the correct NIC.  Once configured, click next.

Configure the ports your provider uses for the connection.  Sipgate uses 5060 and 5063 as standard.  Once configured, click next.

If you connect to your provider through a NAT tunnel, configure it here.  Otherwise click next to continue.

Configure the remote SIP domain and click next

If your VoIp provider doesn't use credentials to connect, tick no credentials needed.

Sipgate issues credentials to use for connecting to VoIP phones and SBCs.  Enter your details and click next.

Now configure the SIP registration.  Click edit... 

...and enter the following and click Ok

The SIP registration settings you just entered should be present.  Sipgate uses the address of record which includes your account number/name to form part of the connection.  Verify and click next.

Configure a SIP proxy if you have one and click next.

This next screen configures your network peer white list.  Add more if you have any or just click next.

Give your SIP node a name.  If you selected a provider from a template the default name will the the name of the template.  Again make it meaningful if you have multiple.  Don't just call it "SIP Trunk".  This will help you when you need to edit later on.  Now click finish

Now you will see the summary screen for your VoIP provider.  Click next to configure routing.

Anynode calls their source and destination routing Routing Domains.  You can choose to use Direct Routing to route calls with or without a prefix.

Configure what you want and click finish.

And that's just about it.  You now have a connection to/from Microsoft Teams for Direct Routing and to/from your VoIP or SIP Provider.

You should see your Nodes and Routing Domains listed in the configuration screen.  Now click commit to commit the config to memory.

Then click monitor mode to go to the dashboard.  You will see a node and network controller for your Direct Routing and SIP connections.  OK means they are connected outbound.

To make sure Microsoft Teams can connect to your SBC click on the node to open it up.  You should see SIP Options and packets being sent and received.  As you can see, the SBC connects outbound to your primary, secondary and tertiary hubs.

If you haven't received any options or you have failed packets there is a problem.  Most likely the network or firewall or possibly a misconfigured SIP Signalling Port in your Online PSTN Gateway.

There are a couple of things to configure still to make sure it all works.  In particular, for your SIP provider.  Sipgate uses the address of record as standard in the SIP header for security. You also want to make sure your SBC forwards the called number to Teams or any other connected node.

Click on Configuration Mode

Now expand Configuration and Nodes and click on Sipgate (or the name of your provider) and click SIP User Agent.

Scroll down and tick "To Header" under Derive Destination-URI from.  

Sipgate sends "" as standard for all incoming SIP messages.  When your routing group forwards that on to Teams, Teams won't know what to do with that because your telephone number isn't your SIP provider account number.  It is probably some E.164 number.

Sipgate also sends an automated area code which adds a 00 before your area code.  In my case 0044 and the number.  You need to create an incoming manipulation to change that and convert the called number to E.164.

Click on SIP Node and where it says dial string manipulations, click add.

Choose Prefix and Suffix Manipulation and click next

Enter 00 in Prefix
Delete the first 2 leading characters
Add prefix + to convert to E.164
And click finish

You'll see your manipulation in the list

Now just click Commit to save and write the changes to memory.

Time to test

Go back to monitor mode to open the dashboard and click Active Sessions.

Place a test call from Teams.  You should see your call on the SBC and with any luck, the person you called will receive a call and will answer.

One last thing.  Save your config to a local file just in case.  Go back to Configuration mode and click configuration and export.

And that's it!  I know it seems like a lot of steps, but this represents about 5 minutes' work.  Maybe 10.  It will be 5 if you've done it a few times.

That's all for now folks!

Additional Info
If you want information about this or any of the other products from TE-Systems visit their website.

For detailed information about the Anynode SBC click here.

TE-Systems produced a great YouTube video on how to do it.


Thanks for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.