Transfer button in cisco Phone greyed out

Few days back encountered a issue on one cutomer location related to soft key, The transfer soft key in the cisco ip phone 7941 is inactive .
after doing a hour of reaearch came across a interesting fact that the maximum call in the Phone conmfiguration is set to 1 :-(

This is the root cause for transfer soft key to be inactive.

increasing the maximum call to a value 3  resolve the issue

Discover new phone in Informacast

Here are the steps that need to be done for discovering any new phone added .

1. Go to  Receipent > Edit receipent Group > Discover recepient

Click on Update

In the next screen click on update

 It will take sometime to discover based on the CUCM database .
Note: You need to make sure that all the server in the cluster have the SNMP string available and the web access on the phone is enabled
Also make sure authentication url is mentione in the phone setting

Creating Recepient Group in InformaCast

For creating a recepient group go to the informacast url https://<IP Address of InformaCast>:8444/InformaCast/admin

1. Go to Recipients >Edit Receipients Group

Option for adding device in recepient group are

Individual
Filter with recepient group
Filter wit rules
Exclusions

tag can be used for group a search so that control over the search results is good.  

You can select the selection criteria based on the above options

To send a message to group...

Go to  Message > Send and Edit Message
under the action tab select send

Click the option where you want to send the messages...For sending a message you can choose a recepeint group or a DN

Cisco Jabber configuration for iOS (i phone)

Here in this post i am giving the overview of the steps that we need to do for configuring Cisco Jabber on apple iphone.

Before doing anything we need to install the cop file for jabber

1. Download the cop file from the CCO

2. Install the cop file from the menu 

3. CUCM -> OS Administration -> Software Upgrades -> Install/Upgrade

once the upload is successful reboot the server 

4. Repeat the procedure for all the subscriber 

5. Repeat the Tomcat service so that the device icon can be displayed

6. Increase the SIP Dual Mode Alert Timer value from

CM Administration -> System > Service Parameters -> [Server] Cisco CallManager (Active) -> Increase the SIP Dual Mode Alert Time to

3000 milliseconds -> Save



7. create a dedicated SIP Profile and modify the below parameter in the SIP profile to 660

    Timer Register Expires
 * Timer Keep Alive Expires
 * Timer Subscribe Expires
8. Add the Phone:

CM Administration -> Device -> Cisco Dual Mode for iPhone -> Add New ->TCT<name>

9. Add the Line to the phone and Associate the Device with the End User



10.Launch the App on the iPhone .

 

 

H323 slow start and fast start .. With Cisco IOS gateway configuration

Before discussing on this topic we must be aware of how the basic call flow occurs on h323 protocol.
here is the basic call signalling that happens with h323

here the the h225 and h245 signalling uses two different TCP connection.

In case of h323 fast start the h245 steps which is the capability and media negotiation steps occurs in the setup message of h225 step.

In normal scenario as per the above diagram can be considered as slow start as h245 negotiation is occurring with separate TCP connection .

so with fast start few message transaction occurs compare to slow start.

Now lets focus on the configuration for the same in cisco IOS gateway.

we can configure this either globally or dial peer level.

In case of global level.

1. Go to configutaion mode

2. Go to voice service mode. with command " voice service voip"

3 Configure the command "h323 call start slow" to revert to fast start configure "h323 call start fast"


In case of individual dial peer level


1. Go to configutaion mode

2. Create a Voice class using command " voice class h323 tag "

3. under the voice class command configure 'call start slow"

4. use the voice class command under the the voip dial peer  command 



Done...:-)

SIP Early offer/early Media vs Delay Offer/Delay Media

Sip is a Request/Response protocol and it uses different mechanism to establish session.This article i am going to discuss about early/delay offer used by SIP for
capability negotiation

Early offer: SIP uses SDP (Session description protocol) in order to negotiate capability between two parties.In case of the early offer the SDP message is sent from the Calling party to calllee party in the initial invite message and the callee party respond with the negotiated capability  in the 200 OK it send to the calling
 party

Delay Offer : In this case the called party send the SDP message in the 200 OK message to the calling party and the calling party respond back with the negotiated parameter in the ACK message it send to callee party

Early Media : In case of early media the media between the callee and calling party establish before the session established between the two.In normal condition the SIP endpoint play ringing sound from its local source when it recieve a ringing message from the callee party.This is sometime confusing as no one knows what is happening at the callee party,Early media play a important role here what t does is the calle party send a message 183 instead of 180 and let the calling party establish a bearer channel between the two party so that they can share the message directly.

Delay Media : In case of delay media the media is established after the SIP session negotiation is complete

CAD Login Step in UCCX

Here is what all event occurs when a CAD uses login to UCCX .

1. CAD will connect to the UCCX (LRM service) to check if there are licenses available. If it fails at this stage, we get the error "License Server is Down". The login screen is not even provided.
2. Once the user enters the userid/password, the same is sent to the UCCX. Now, the user is searched within the LDAP database of the UCCX. If the user is not present, we get the "Invalid User" error.
3. The AXL request is sent to the CUCM for authentication. Post that, the CTI Control is opened on the agent device. Here we either get the "Authentication fail" or the "Error with CTI or RMJTAPI" respentively if either fails.
4. User configuration is loaded from the LDAP of UCCX i.e. agent specific config such as integrated browser setting etc. and also the connection is made to all the services such as recording, chat, playback and so on.