Acme Packet SBC looping after attempted upgrade

When upgrading the Oracle SBC it fails and keeps looping without actually booting up>

boot device          : eth
unit number          : 0
processor number     : 0
host name            : XX.XX.XX
file name            : /boot/nnECZ730mXX.XX
inet on ethernet (e) : x.x.x.x:ffffff00
gateway inet (g)     : x.x.x.x
user (u)             : vx
ftp password (pw)    : vx
flags (f)            : 0x0
target name (tn)     : XX.XX.XX

Loading /boot/nnECZ730x.x.x.bz…/boot: volume uses UTF-16 on disk, but Unicode is disabled

CAUTION: 32bit CPU attempting to boot an untagged Linux image.
If system hangs, power cycle and set boot file to a 32bit image.

Boot protocol version 2.10

Found kernel version string: 2.6.39-el6uek.v2.6.39-400.298.2-cov (acme@goose) #2SMP PREEMPT Thu May 17 16:19:36 EDT 2018

Kernel cmdline = console=ttyS0,115200,n8 flags=0x00000000 hostname=x.x.x.x  acmeplatform=SD3 crashkernel=128M quiet

Starting at 0x1f863d5a…

kernel_start = 0x208a9010
kernel_size = 0x0388b7d0

Acme Packet Net-Net 3820
Processor speed: 1.866 GHz
Stage 1 (built Nov  1 2013 11:09:15)
/boot: volume uses UTF-16 on disk, but Unicode is disabled
Stage 2 (built Nov  1 2013 11:09:15)

Resolution is to boot back to previous image by changing the /boot/oldimage and freeing up space on the /boot/ folder. revert back to new image and it should upgrade.

other possibilities could be incorrect stage3 bootloader.

 

Advertisements

Cisco WebEx share

Bold and ProudThe New Cisco WebEx share is targeted towards making any room into a conference room, sometimes you may have a conference room but not enabled for Video Conferencing, thereby enhancing the conference experience. This product is a low cost option to convert the TV in that room into a high quality  collaboration experience whereby one can enable wireless content sharing without the need to connect any dongles to enable it to work. It allows you to book a room, display the calendar on screen and join the meeting with the WebEx Teams Application. The WebEx Teams Application will show you the room in proximity that you are able to connect to. This easily simplifies and enhances the meeting join experience by simply launching the WebEx Teams application and connecting to a device:

If it has identified a device it will show up as such:

The WebEx share is a nice and compact device designed to transform any TV into a WebEx device. This makes use of the great cisco innovations we are used to in a traditional video endpoint packed in a dongle. Turning on the HDTV display is triggered by;

  1. A person simply entering the room
  2. A WebEx client app pairing with the room device
  3. Calendar event scheduled 15 mins before the meeting
  4. Making noise in the room

The device supports HDMI with a 1080p resolution and 30fps.

You can connect using it in three ways;

  1. Wi-Fi this is the default option – on powering up with no wired connection it will initiate AP mode, while in this mode it the connection will be secured via WPA2 with a numeric password – once the connection is established AP Mode is disabled. The Dongle supports 802.11ac, an IEEE standard with speeds reportedly reaching 1.3 Gbps,
  2. PoE – Yes Power over Ethernet, this will plug into any PoE enabled switches
  3. Wired – Non-PoE

It has Enterprise grade security for wireless by supporting the EAP Protocol suite including PEAP, FAST and TLS. It Supports wired 802.1x port based Authentication & Proxy Support. The EAP/TLS and 802.1x can have local or customer CA signed certificates.

How to provision:

  1. Login to WebEx Control Hub
  2. Setup a new ‘place’
  3. Enable calendar service and associate a calendar mailbox to the ‘place’
  4. Generate activation code and enter on WebEx Share activation screen

As with any cloud registered webex device, WebEx chare will recognise and greet you upon entrance to the conference room as long (as you have the WebEx Teams App running). This technology is identical to WebEx room kits or the WebEx board.

When a room is reserved you can see the Room Name (top left), Current Time, any current and upcoming  meetings:-

Comparison to Competition
There are a number of players in this space, namely Polycom, Crestron, Barco and some others. While they all have Local Wireless sharing in common Enterprise management is offered by some but Meetings and calendar integration is not offered by any except Cisco WebEx Share. The Price it will be released at is incredibly competitive and especially considering the technology it is packed it will be worth it.

This Device will be available Q4 CY 2018 across North America, Australia and Europe, limited orderability is available before that.

Cisco WebEx Assistant

Webex-AssistantWe all agree Technology should be an enabler not a hindrance. In the collaboration area, enabling colleagues to be able to communicate with each other without the need to understand technology but rather to ensure the medium used to contact another is simple and causing the least hindrance possible. Aside from the area of interoperability – which is in itself an entire topic for discussion, in recent years vendors have tried to prioritise the usability as a main focus. In this fast pacing world, users already have a vast number of things they need to specialise in and the last thing they should be worried about contending with should be the technology. 

in my experience, Cisco has successfully managed to standardise the usability aspect across all their video enabled endpoints so there is no need to learn how to use one endpoint to another. For their part, they have generally been focussing on making most of its products more ‘intuitive’ and in the workspace based collaboration arena they have been pretty consistent in achieving this ‘more intuitive’ way of working.

while continuing on working to enhance the user experience they are now working on leaveraging the use of Artificial Intelligence to take it to the next level. With the upcoming introduction of Cisco WebEx Assistant it aims to take the collaborative experience to the he next level by making it more personal. With WebEx Assistant it now powers a more natural way of communicating with technology as if it was a person. This way, it does away with the need to know how to dial a person rather now to just speak to the Assistant asking it to make the call. 

What makes this different to the use of Amazon’s Alexa, Google Home and any other consumer based offering out there? On the face of it, it seems like a valid question, but when you consider the broad nature and superficial depth of the queries it does not fully apply in the business context. When querying Amazon Alexa for the name of an actor on a particular movie one is watching will be different to a business application where its application has more a specific context, for example in an organisation there would be thousands of users and the AI component can identify differentiate John from another user based on his speech patterns, and then to link the relevance of John’s calling habits, meeting information and organisational structure to identify the most likely match for John wanting to call Jon ABC as opposed to Jon DEF on the basis of his interaction and organisational placement and a number of other factors. If John has a impending meeting to then just join the meeting:

Okay – WebEx, Join my meeting …

Hi John, Joining your meeting…

From a corporate perspective there is also the consideration of security, we may have all read the reports of Amazon Alexa listening in on and recording private conversations and sending to other people – would this be acceptable in corporate organisations ? 

The Initial release of cognitive AI from WebEx assistant allows users to perform basic functions such as Start Meetings, Join and Leave Meetings, Call anyone in the organisation, providing basic capabilities such as:

  • Meeting Rooms
    • ‘Start the Meeting’
    • ‘End The Meeting’ 
  • Personal Room
    • Join my personal room ‘
    • ‘Join Tim’s Personal Room’
  • Calling
    • ‘Call Joe Bloggs ‘
    • ‘End the call ‘
  • Device Control
    • ‘Turn up the microphone’
    • ‘Mute the microphone’ 

 

Error connecting to a S4B and CMS Dual Homed Call

When attempting to Join a Microsoft Skype meeting the call from a Cisco Endpoint fails, a point to point however does not, looking at the logs it suggests that it cannot find the conference “meet.alictrify.com/joe.microsoft/2h2g6c6r” not found

2018-06-19 12:53:27.669 Info 2000 log messages cleared by “admin”
2018-06-19 12:53:34.558 Info call 16: incoming encrypted SIP call from “sip:dx80@alictrify.com” to local URI “sip:meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com”
2018-06-19 12:53:34.625 Info lync conference resolution: C3p query error
2018-06-19 12:53:34.626 Info lync conference resolution: conference “meet.alictrify.com/joe.microsoft/2h2g6c6r” not found
2018-06-19 12:53:34.626 Info forwarding call to ‘sip:meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com’ to ‘meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com’
2018-06-19 12:53:34.629 Info call 17: outgoing SIP call to “meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com” (Lync)
2018-06-19 12:53:34.652 Info call 17: ending; remote SIP teardown with reason 18 (not found) – not connected after 0:00
2018-06-19 12:53:34.653 Info call 16: ending; local teardown – not connected after 0:00

Since we are attempting to join a Lync Meeting and not a gateway call which would be converted to MS-SIP, CMS needs to convert the user portion of the URI into an HTTPS target and try to find an Office365 meeting hosted at that URL. This is achieved by setting the SimpleJoin to be enabled and set to Yes.

Once configured, the resolution will work and this will now show up as:

2018-06-19 13:23:24.749 Info lync simplejoin resolution: successfully completed
2018-06-19 13:23:24.754 Info call 34: outgoing SIP call to “joe.microsoft@alictrify.com;gruu;opaque=app:conf:focus:id:2h2g6c6r” (Lync focus)
2018-06-19 13:23:24.758 Info call 33: setting up UDT RTP session for DTLS (combined media and control)
2018-06-19 13:23:24.785 Info conference “Lync conference meet.alictrify.com/joe.microsoft/2h2g6c6r”: unencrypted call legs now present
2018-06-19 13:23:24.790 Info call 34: SIP call ringing
2018-06-19 13:23:24.826 Info call 35: outgoing SIP call to “joe.microsoft@alictrify.com;gruu;opaque=app:conf:focus:id:2h2g6c6r” (Lync conference subscription)
2018-06-19 13:23:24.861 Info call 36: outgoing SIP call to “Joe.Microsoft@alictrify.com;gruu;opaque=app:conf:audio-video:id:2H2G6C6R” (Lync)
2018-06-19 13:23:24.862 Info call 37: outgoing SIP call to “Joe.Microsoft@alictrify.com;gruu;opaque=app:conf:chat:id:2H2G6C6R” (Lync IM)

This shows that the Lync Focus which is responsible for enforcing the Conference Control Policy,  Lync Conference Subscription, Audio / Video, Lync IM setup completes successfully for Skype Meeting ID 2h2g6c6r

in CMS you can also see the same channels setup in the active calls:-

OBTP not updating

When attempting to setup a Skype for Business meeting from a client inviting a Cisco DX80 endpoint it was not updating,

having a look at the logs it seems like a Credentials error :

2018-06-19 13:34:19,401 [MeetingSynchronizerThread] INFO – Forcing update for endpoint dx80@alictrify.com.
2018-06-19 13:34:19,401 [MeetingSynchronizerThread] INFO – Sending out OBTP information to endpoint dx80@alictrify.com for meeting ‘dx80@alictrify.com’.
2018-06-19 13:34:19,401 [MeetingSynchronizerThread] INFO – Updating endpoint dx80@alictrify.com with OBTP information; attempt 1
2018-06-19 13:34:23,682 [OBTPThread] INFO – Failed to connect to endpoint on ‘192.168.0.11’, now trying with a different protocol.
2018-06-19 13:34:24,526 [MeetingSynchronizerThread] INFO – Failed to connect to endpoint on ‘192.168.0.11’, now trying with a different protocol.
2018-06-19 13:34:28,510 [OBTPThread] ERROR – ConnectToSystem
System.Exception: The remote server returned an error: (401) Unauthorized.
2018-06-19 13:34:29,354 [MeetingSynchronizerThread] ERROR – ConnectToSystem
System.Exception: The remote server returned an error: (401) Unauthorized.
2018-06-19 13:34:29,526 [OBTPThread] INFO – Updating endpoint dx80@alictrify.com with OBTP information; attempt 2

this is corrected by navigating in SynergyJoin application to Video Systems and adding password to the endpoint in question.

SynergySky: updating calendar with OBTP

In the SynergySky Join Version 2.5 there is a preview feature that allows the calendar invite to be updated after the meeting invite has been sent out, for this to work additional permissions need to b configured in Exchange which allows the meeting organiser to update the meeting after the invite has been sent out otherwise the organiser will receive the following error:

Scenario:
User books meeting inviting Microsoft S4B Client and Cisco Video Endpoint (DX80). Calendar does not get updated as permissions not set in Exchange. Exchange Version used: 2016

The following power shell permissions applied to the Exchange will give users the right permissions needed to perform this action

This will give exchange service account ‘Editor’ access to be able to update the calendar appointment with dial in information:

Add-MailboxFolderPermission -Identity joe.microsoft@alictrify.com:\Calendar -User administrator@alictrify.com -AccessRights Editor

The service account also needs an AD user object permission: ‘sendas’ for each user to send a updated invite to all recipients –

Add-ADPermission “Joe Microsoft” -User alictrify\administrator -Extendedrights “Send As”

< this was previously implicitly included in the Exchange server “Full Mailbox Access” permission or added in Exchange Online as part of the Add-RecipientPermission

Now when you send a invite you will not receive a failure email but rather a update in the calendar as follows:

When the time for the meeting comes you will see OBTP appear on screen: