#X lite softphone xmpp how to#
#X lite softphone xmpp install#
#X lite softphone xmpp password#
#X lite softphone xmpp download#
#X lite softphone xmpp free#

Go to Device Associations and associate the device you just created. Now go back to the user you are assigning this soft phone to (e.g.

Display and Alerting: Configure these as you would like.

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).

Directory Number: 2025550208 (I use 10d extensions).

The bare minimum settings I used for testing: After saving the phone, you can add an extension. I also tested Trusted Relay Point (TRP) and it worked as it should (TRP will be a topic in a later blog).Ĭlick on Save. I played with Presence subscriptions with marginal success (later blog maybe). Other phone parameters can use the default settings.

Device Security Profile: Third-party SIP Device (Basic) – Digest Required.

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)

#X lite softphone xmpp free#

The free X-Lite doesn’t support G.729 or other CODEC. 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.

Description: Bill Bell X-Lite (set it to something meaningful to you, it doesn’t matter to X-Lite).

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.

Digest Credentials: ******* (this is used by X-Lite!)Ĭlick on Save.

PIN: (this is not used by X-Lite, but … you get the idea).

Password: (this is not used by X-Lite, but you should always have one).

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. Search for profiles that contain the string “third-party” and copy the profile named “Third-party SIP Device (Basic) – Standard SIP Non-Secure Profile”. This is incorrect.Ĭonnect to your CUCM server ( and go to System->Security Profile->Phone Security Profile. You assigned to the user in CUCM when you configure the Account Settings in X-Lite.

#X lite softphone xmpp password#

NOTE: In the X-Lite configuration examples I have seen, it is suggested that you specify the password

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. 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. You will need to make some associations between the two and perform some other ancillary activities in preparation. In CUCM you will need to create a SIP device and a user object. I like to get the station configured in CUCM before I start playing around with the client.

#X lite softphone xmpp install#

The install is pretty straight forward and relatively quick.

#X lite softphone xmpp download#

I suspect that procedures for 6.0 to 7.1 would be near identical.įirst, 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. I like X-Lite, so I am using it as the example.įor my testing I used CUCM 7.0-1 (that is 7.1(3b)SU1 for the uninitiated).

#X lite softphone xmpp how to#

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. 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. The examples would have things like this: 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. First, I just wanted to add some 3rd party SIP phones to CUCM to start testing feature behaviors.