RuhNet

Yes, the UAC module would need to be loaded, but also some additional config. You add the registration details to the database. Check out the "Nick vs Networking" blog for more info on this--he has a very good UAC explanation and example that you can work from. Not for Kazoo specifically but vanilla Kamailio, but as far as the UAC config it should be the same. As for method 2, (using external Asterisk as "carrier" for Kazoo) yes you are correct.

@Mehedi Hasan Tanim Although outbound registration is not supported with Kazoo, you can make it work by modifying the Kamailio config to use the UAC module. Alternately, (and this is probably the easiest way) you could place an external Kamailio/Asterisk/Freeswitch server outside of Kazoo and use it for the "carrier" for Kazoo; have the external server do your registrations and pass calls along to your Kazoo Kamailio server like normal carrier calls.

No problem, glad to help. :-)

Great stuff, @Mehedi Hasan Tanim When I asked you to document this so that other people could benefit, I did not expect you to start from the beginning with auth and the Flowroute setup, I just meant the part we covered about the click2call, but this is fantastic. Bravo for your contribution to the community; I'm sure others will benefit now. Good job!

This is why registration is not part of default Kazoo---it breaks the scalability and redundancy. Although some providers do require registration before allowing outbound calls, registration is generally a thing for incoming calls, which come in to Kamailio, not Freeswitch, so registering from Freeswitch will likely break incoming calls for you. A better solution is to register with Kamailio. You can do this with the UAC Kamailio module (not enabled by default). Then Kamailio will register to your provider for incoming calls, and outbound calls will just use the user/password auth from all Freeswitch servers you have. But IF your provider requires registration before allowing outbound calls, as well as inbound, then you can still make it work. What you'll need to do is in addition to using UAC, append ;fs_path=sip:KAMAILIO_IP_ADDR to your gateway server in your Kazoo carrier resource (whether offnet or account level). Example: sip.ruhnet.co;fs_path=sip:111.222.123.123 where sip.ruhnet.co is your carrier sip server and 111.222.123.123 is the IP of your Kamailio server. This will force Freeswitch to send outbound calls to that carrier through your Kamailio server. If you have more than one Kamailio server, you'll have to pick which one you want to use for this carrier. In theory, it's possible to still have redundancy for this situation, but it would require two additional external Kamailio servers sharing a floating IP (your own intermediate "carrier" just to connect to this one limited registration-only carrier.) But if you must do something like that then it's probably a lot smarter just to change carriers to one that supports IP auth. 😀

Yealink has an XML developer's guide that is freely available (just Google search and find the latest version, or one that matches your firmware version). You can check it for info on how to modify the XML so that it works properly.

The problem with some of the Cisco phones that I've had (the ones designed to be used with Cisco Callmanager, not the SPA series) is getting them to register to a domain, rather than an IP address.

Anruag, if you paid via credit card or PayPal, you may be able to reverse the transaction.

Yes, you can use the TFTP Recovery method to put a stock firmware back on the phones. (Just Google "Yealink TFTP recovery".) You can actually do the process without using a TFTP server if you wish, by putting the files on a USB thumb drive. Either way, you hold down the speakerphone button while the phone boots up and you'll be presented with a simple menu where you can load the recovery files.

Ah ok; that's much clearer information. I checked on those specific gateways, and they appear to be versatile enough to do it several ways. The easiest way would be to give each gateway a static IP address, disable registration, and use user/password authentication to select the proper outbound channel, and set your Kamailio server IP as the outbound server address. Then setup the "trunks" as regular outbound carriers in Kazoo, with user/pass, and add the gateway's IP to the carrier ACLs on your Kamailio servers to allow incoming calls. You may also be able to mess with some settings in the gateways and avoid using individual credentials for each line, and use a single credential for each gateway, and have a ring group or something within the gateway select a free outbound line.

Well, yes, I and probably others have experience with this but there are many many different multiport gateways, all with various ways of being setup and with various features/limitations/etc. So, more detail is needed before a useful response can be provided. Are you working with a specific brand/device you are having an issue with, or looking for recommendations, or ???

What are the types of issues that v85 firmware is causing?

You might find this link helpful. Although it's for AWS, the same config (at least mostly) would apply to Azure. https://github.com/OpenTelecom/kazoo-install-guide

Gagan it looks like you are missing the "register" string in sip.conf. A look at your kazoo logs or SIP trace when you try to send a call from Asterisk into Kazoo would confirm, but it looks like with what you have, your Asterisk isn't actually trying to register. To have it do that, you need to have an additional line in the [general] section of sip.conf like this: register=>SIP_ID:Password@20201126085320.sip.XXXX.com Also you have "nsecure" where it should be "insecure" 😄