Algo Door box

[kevin@m2sintegration.com]

To whom it may concern, 

We are trying to connect an Algo 8028 Sip device to a customer of ours and we cant seem to get it to work. The Customer is L&M. I have tried to create this device as a VOIP Device as well as a SIP URI and a Softphone with no connection from any of them. I do not see a BYOD option. I have entered in the SIP credentials, authentication ID and password. I gave the doorbox an extension of 555 and set it to dial 500 which is my main callflow group. When I press the doorphone button I hear ringing, but the phones are not. Has anyone ever set one of these up before and if so can you guide me into doing this? 

Edited February 13, 2018 by kevin@m2sintegration.com (see edit history)

[mc_]

Have you captured the Kazoo/FreeSWITCH logs of an attempt? If we could see those it would help figure out where things are going awry.

[Mark Diaz]

On 2/13/2018 at 3:03 PM, kevin@m2sintegration.com said:

To whom it may concern, 

We are trying to connect an Algo 8028 Sip device to a customer of ours and we cant seem to get it to work. The Customer is L&M. I have tried to create this device as a VOIP Device as well as a SIP URI and a Softphone with no connection from any of them. I do not see a BYOD option. I have entered in the SIP credentials, authentication ID and password. I gave the doorbox an extension of 555 and set it to dial 500 which is my main callflow group. When I press the doorphone button I hear ringing, but the phones are not. Has anyone ever set one of these up before and if so can you guide me into doing this? 

Sorry I'm a tad late to this post. However, we have Algo in the field and if you're still having issues I'd be happy to tap one of my peeps for a sample of their configuration. 

[Alex Aristides]

On 2/13/2018 at 4:10 PM, mc_ said:

Have you captured the Kazoo/FreeSWITCH logs of an attempt? If we could see those it would help figure out where things are going awry.

Where is this you're referring to? Is this in the debugging app? If not, where do we go to obtain?

[mc_]

Typically there's a call-id associated with the call that can be used to grep the logs of Kazoo, FreeSWITCH, and Kamailio. Those logs are helpful in seeing what might have gone wrong.

[Alex Aristides]

1 hour ago, mc_ said:

Typically there's a call-id associated with the call that can be used to grep the logs of Kazoo, FreeSWITCH, and Kamailio. Those logs are helpful in seeing what might have gone wrong.

Again im not understanding what freeswitch and kamalio are? If the logs are being created in kazoo, these other softwares can grab these logs?

[mc_]

FreeSWITCH and Kamailio are two open source telephony projects upon which Kazoo sits. They log their processing of the calls in addition to Kazoo's logging.

[ryan@m2sintegration.com]

Just to update this one for everyone planning to using an Algo Door Box:

Create a user in advanced callflows. 
Assign a device to that user as a soft phone. Take note of the SIP username, SIP password, and realm/domain of that device. Make sure you save!

Now through the WUI of the Algo device:
Basic settings --> 
SIP Domain = "realm" field from the device
Extension = SIP username of the device  (this is where we were stuck! It wasn't the dial by extension. "Duh" moment)
Authentication ID = SIP username of the device
Authentication password = SIP password of the device

Dialing extension = extension that the door box dials. We like to set up an extension in advanced callflow, then point it to a group. 

Make sure to save!

Now navigate to Advanced settings --> Advanced SIP:

Outbound proxy = us-east.zswitch.net (or Central or West, depending on location. We're on East Coast)

Backup Server #1 = us-central.zswitch.net

Backup Server #2 = us-west.zswitch.net

Click save!

Now navigate to Advanced settings --> Advanced SIP: 

Time: Set your time zone. Click Save! 

Check the status page to see if it registers. 

That should be it. We were getting a "unauthorized" error at first when attempting to register. This was because we were putting the actual dial by extension number in the "extension" field instead of the SIP username, which should actually match the authentication ID. 

See screen shots for an example of what the tabs look like. These aren't the actual credentials, as this was just to help anyone else having trouble in the future! Hope it helps someone out there!