The API method

Log into the Skyswitch Manager Portal and create a new user under the customer's domain. This user makes the API calls, so give it the scope of Office Manager.

Note the username and password down; they go into Orion when you set the client up.

Then go to Domains and copy the domain name associated with the customer.

The SIP proxy method

As an alternative to the API, Fetchit can connect over SIP. This avoids keeping API credentials in Orion and instead relies on a Fetchit SIP agent extension registered directly in the Skyswitch PBX.

How it works

Instead of Skyswitch API credentials in Orion, a Fetchit SIP extension such as 102F is created in the PBX and registered as a device on an existing extension. The SIP agent logs in and listens for calls routed to that extension. Because the Fetchit device is an additional phone on an existing extension rather than a separate one, it does not incur extra extension billing.

Setting up the Fetchit SIP extension

1. In the Skyswitch PBX portal, open the customer's domain.
2. Identify the extension Fetchit should monitor, for example extension 102.
3. Add a new device or phone to that extension, named with an F suffix, for example 102F. As an additional device on an existing extension, it is not billed separately.
4. Configure the SIP connection for that device in Orion.

Adding the extension to a ring group

If the customer routes incoming calls through a ring group, for example "Group Front" at extension 200 fed by an auto attendant or phone tree, the Fetchit SIP extension has to be a member of that group as well. Without it, Fetchit only sees calls that ring the individual extension directly and misses everything routed through the group.

1. In the PBX portal, open the ring group, for example "Group Front" at extension 200.
2. Click Edit.
3. Add the Fetchit SIP extension, for example 102F, to the member list.
4. Click Save.

Once saved, the SIP agent receives ring events for every call routed to that group, and bubbles appear on the clinic's desktops.

When SIP does not work

• The agent shows as logged in but no calls register. The Fetchit extension is probably not a member of the ring group the calls are routed to. Check the auto attendant or phone tree to see which group receives the call, for example when a caller presses 1, then add the Fetchit SIP extension to that group.
• Credentials were removed or corrupted in Orion. Re-enter the SIP proxy details to re-establish the connection. You do not need to recreate the extension in the PBX if it still exists.
• Choosing between SIP proxy and the API. Either works. SIP proxy avoids storing API credentials in Orion and can be simpler to set up; the API gives more control. If the client is already on one of them, stay on it.