Second, the resources I have found on-line, including CouterPath’s own write up (which is a bit dated) and an article on Cisco’s “community” collaboration site, were just too light on details. X-Lite seemed like a reasonable choice as it was free and apparently pretty popular. If youre on Mac or Windows, download Bria Solo (formerly X-Lite).First, I just wanted to add some 3rd party SIP phones to CUCM to start testing feature behaviors. Here is a screenshot: And here is a video of SIPp in action (Windows Media Player 9 codec or above required): sipp-01.wmv.Plivo endpoints expand the capabilities of your existing SIP phones, allowing you to. It is also very useful to emulate thousands of user agents calling your SIP system. SIPp can be used to test various real SIP equipment like SIP proxies, B2BUAs, SIP media servers, SIP/x gateways, SIP PBX.I like X-Lite, so I am using it as the example.For my testing I used CUCM 7.0-1 (that is 7.1(3b)SU1 for the uninitiated). But, I hope to provide some examples to give you a better feel for how to add 3rd Party SIP endpoints to the CUCM. Every one of us has a slightly different environment that we operate in. Ims clients, boghe imsrcs.I ask you, what am I supposed to do with that if I try to deploy this application in the real world? Now, I am not saying that I am going to cover all bases adequately in this example. Sip client zoiper offers voice and video calling, video conferencing, call recording, call transfer and an autoanswering feature. The Telephony for Microsoft client is specifically oriented to customers that prefer the collaboration tools of Skype for Business, but wish to have the robust telephony service provided by the Mitel.
Sip Phone Client Download Bria SoloThe install is pretty straight forward and relatively quick.I like to get the station configured in CUCM before I start playing around with the client. I suspect that procedures for 6.0 to 7.1 would be near identical.First, you will need to download the X-Lite application here. From looking at some of the examples on line (dating back to CUCM 5.0), the basic configuration we are going to discuss is pretty applicable to all CUCM appliance models. This is incorrect.Connect to your CUCM server ( and go to System->Security Profile->Phone Security Profile. NOTE: In the X-Lite configuration examples I have seen, it is suggested that you specify the passwordYou assigned to the user in CUCM when you configure the Account Settings in X-Lite. This means that a client can connect by simply providing the extension number and a user ID. If you go with the standard SIP security profile, digest authentication is not used. I don’t, so we are going to create a SIP security profile that forces the use of Digest Authentication. You will need to make some associations between the two and perform some other ancillary activities in preparation.I suppose you could consider this an optional step if you don’t mind SIP endpoints just registering to your CUCM cluster without a password. The information you need to configure (values shown are used in our example): You can also use a user that was replicated from LDAP using the DirSync service. You can add a new user or use an existing user. Configure the new profile as follows:Go to User Management->End User. MAC Address: DEADBEEF0000 (set it to something unique, it doesn’t matter to X-Lite) At a minimum, you should configure the following settings (values shown are used in our example): Click on Add and select “Third-Party SIP Device (Basic)”. We will come back to the user object in a moment.Go to Device->Phone. Digest Credentials: ******* (this is used by X-Lite!)Click on Save. PIN: (this is not used by X-Lite, but … you get the idea) You will want to make sure that if you are using regions, to keep everything G.711. I like to stick my softphones in a separate bucket. Device Pool: HQ_User-SoftPhone_CSS (You should use a device pool that makes sense in your environment. I played with Presence subscriptions with marginal success (later blog maybe). I didn’t test Device Mobility yet. Device Security Profile: Third-party SIP Device (Basic) – Digest RequiredOther phone parameters can use the default settings. Calling Search Space: HQ_User-Std_CSS (this should be a CSS that fits into your dial plan, just like a standard Cisco SCCP station) Also, a Cisco tidbit – the default inter-region CODEC is G.729) The bare minimum settings I used for testing: Add the extension as you normally would. After saving the phone, you can add an extension. Mac emulator javaGo to Device Associations and associate the device you just created.Launch the X-Lite application. Display and Alerting: Configure these as you would likeNow go back to the user you are assigning this soft phone to (e.g. Call Forwarding: Configure Call Forwarding as you would normally, for example CFNA and CFB to voicemail Voicemail Profile: Use the VM profile that you normally would CSS: Apply line level CSS per your design Partition: CL_DN-1_PT (place the DN in your “phones” partition) Go to the “Account” tab and configure as follows:The figure above gives you some guidance on what should be configured in each field and what needs to match CUCM configuration fields. Click on Add to create a new SIP account. After the application loads, you will have a screen similar to the following:Right click on the “LCD Screen” and choose Account Settings. If you want the user experience on the X-Lite phone to mimic what your CUCM dial plan does for standard SCCP phones, then you will need to configure the dial plan on the X-Lite client. If you setup everything correctly, you should see a screen similar to the following:You’ll notice in the Account settings screen that there was a dial plan field. _sip._udp.netcraftsmen.net) that is configured with the correct UDP port (5060), the X-Lite client will query your DNS domain for the SRV record and register.Click on OK. I found that if you have an SRV record for SIP (e.g. I did some testing with SRV records. This was relatively straight forward. Have fun!I tested the X-Lite application with voicemail (Cisco Unity Connection). The goal is to mimic the digit patterns and lengths that your users are used to dialing. If something substantial is discovered I will plan on posting the findings here.William Bell is the Collaboration Practice Lead for Chesapeake NetCraftsmen. A few features don’t behave the way I would like them but that could be I am not configuring them correctly. The MWI notification functions as shown in the following figure.When you see the MWI envelope, you can click on it with your mouse and if you configured the voicemail pilot number correctly in X-Lite, you should be sent to your voicemail system and prompted to logon.Well, I am still playing around with the application and I have not concluded whether I would deploy this in a production environment or not. Use the pilot number you assigned to the voicemail profile in CUCM. In X-Lite, you configure the SIP account Voicemail tab and enter the voicemail pilot number. There is a Jabber for Mac client that will provide audio and video softphone capabilities. You can follow Bill on Twitter: does not have a softphone that runs on the Mac and leverages SCCP as a protocol. In addition to blogging on the NetCraftsmen site, Bill also maintains the UC Guerrilla blog. That is how the client registers to CUCM. Most 3rd party SIP clients I have tested will care about the directory number on the primary line. It leverages SIP for call processing with CUCM.Getting back to your original question, the device name assignment in CUCM for a 3rd Party SIP device isn’t that important as long as it is unique within the cluster. I use Bria (the paid version of X-Lite) with good success.
0 Comments
Leave a Reply. |
AuthorMichael ArchivesCategories |