Cisco Call Manager and Skype connect
For one project, it was decided to test Skype Connect for coexistence with Call Manager. At the same time I’ll figure out how it works and whether all this bunch can be used in production to reduce telephony bills.
Used version CCM 6.1.X
First you need to register with Skype Manager and, accordingly, put money into your account. All this is described in detail on the Skype website and I will not focus on this. In addition to one point, money must be added to the account in the Skype manager itself, otherwise it will fall directly to the Skype account and will not be available in Skype Manager. To use credit cards, you need to re-verify account. I for test needs requested $ 10 with pay pall.
After the money appeared on the account, go to Skype Connect and create a SIP Profile.
We select the Name, the number of channels we need (here we need the money in the account) and get the data for authentication.
To make outgoing calls, you still need to put money on the created SIP Profile.
Now we have everything (SIP User, Password and money in the account) for making calls using the Skype network.
Getting started configuring CCM. In the process of tuning, I had to talk with the skype support which said that you need to buy CUCM for skype connect and there are also such rumors on the Internet, I did not believe them and pulled out the main thing from them that the alarm goes via UDP, not TCP. This was a revelation to me.
By crawling through the menus and questions to the experts, it became clear where to change the Outgoing Transport Type and then in a couple of hours using tcpdump a working configuration was created.
Create a new SIP Security Profile. Like the screenshot. In place of the X.509 Subject Name, I entered the user name obtained in Skype Connect, but this is probably not necessary.
Create SIP Realm. Realm itself I spied tcpdumpom and this is the internal IP CCM. User and Digest Credentials that we got on Skype Connect.
Next, create a SIP trunk. Caller ID DN - User obtained via Skype Connect.
Create a Route Pattern and call. The number must be e.164.
Results
1) It works
2) MTP is not needed
3) in order to reduce accounts you can use
4) It was not possible to make calls to the business account work, but as part of my research it wasn’t necessary to do the same, Online Numbers also do not work
Used version CCM 6.1.X
First you need to register with Skype Manager and, accordingly, put money into your account. All this is described in detail on the Skype website and I will not focus on this. In addition to one point, money must be added to the account in the Skype manager itself, otherwise it will fall directly to the Skype account and will not be available in Skype Manager. To use credit cards, you need to re-verify account. I for test needs requested $ 10 with pay pall.
After the money appeared on the account, go to Skype Connect and create a SIP Profile.
We select the Name, the number of channels we need (here we need the money in the account) and get the data for authentication.
To make outgoing calls, you still need to put money on the created SIP Profile.
Now we have everything (SIP User, Password and money in the account) for making calls using the Skype network.
Getting started configuring CCM. In the process of tuning, I had to talk with the skype support which said that you need to buy CUCM for skype connect and there are also such rumors on the Internet, I did not believe them and pulled out the main thing from them that the alarm goes via UDP, not TCP. This was a revelation to me.
By crawling through the menus and questions to the experts, it became clear where to change the Outgoing Transport Type and then in a couple of hours using tcpdump a working configuration was created.
Create a new SIP Security Profile. Like the screenshot. In place of the X.509 Subject Name, I entered the user name obtained in Skype Connect, but this is probably not necessary.
Create SIP Realm. Realm itself I spied tcpdumpom and this is the internal IP CCM. User and Digest Credentials that we got on Skype Connect.
Next, create a SIP trunk. Caller ID DN - User obtained via Skype Connect.
Create a Route Pattern and call. The number must be e.164.
Results
1) It works
2) MTP is not needed
3) in order to reduce accounts you can use
4) It was not possible to make calls to the business account work, but as part of my research it wasn’t necessary to do the same, Online Numbers also do not work