Call manager 5 in cisco phone

Hello All,
Maximum 3 call managers can be added in CM group and one SRST reference. So totally 4 CM servers but why we have CM server 5 in all cisco phones under network configuration.
-Murali

perhaps the plan at one point was to support more, and nobody ever bothered to adjust the page. In either case 3 +1 as you state is the max.
HTH,
Chris

Similar Messages

  • "click to call" posibillity in cisco phones ?

    Hello
    Is there any way to call numbers on cisco phones directy from clik on website ?
    I am looking for sollution like in skype :
    https://support.skype.com/en/faq/FA12264/what-is-the-skype-add-on
    Users install add on on computer webbrowsers and numbers are automicaly highlited and then user can click this and call
    I am looking this for hardware voip phones.
    Is this possible on any cisco or non-cisco phones ?
    Sorry for my bad english

    Skype is working to provide a Click to Call update as close to a Firefox browser update release as possible. The current Skype click to call plugin is compatible with Firefox 26.
    Follow the latest Skype Community News
    ↓ Did my reply answer your question? Accept it as a solution to help others, Thanks. ↓

  • Cisco call manager and ip phone software.

    Hi everybody.
    Does Cisco call manager also include software required for ip phone? Or software for ip phone needs to be installed on tftp server and it does not come with cisco call manager.?
    thanks and have a great weekend.

    Hi Sarah,
    by ip phone software, do you mean Cisco IP Phone Agent software?
    if  yes, then you need to have Customer Response Solution (CRS) and Call Manager together to setup ip phone software (services).
    check this link for further info:
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a00801c5765.shtml
    plz Rate if it helped.
    Soroush.

  • Call manager and Cisco IP phones

    I would like to know if it's possible to use Cisco IP phones in small environments, without having Call manager, or it's mandatory to have always CallManager if one wants to use the IP phones.
    Thank you

    You can use Call Manager Express, which runs on cisco 1751/60, 2600 and above routers. it can support up to 120 users. Cisco Unity Express will provide voice mail. this is a network module in 2600 and above routers. for more info, see www.cisco.com/go/ccme

  • Cisco Call Manager - No all phones uses License

    Hi Community.
    I've upgraded from Call Manager 8.0 to 9.1. I did the License Count Utility Report and the License request from ELM.
    Cisco sent me then afterwards the license, I've installed the license and all done.
    But as you see on the print screen only few devices uses a license. Why?
    Best Regards Patrick

    Hi Patrick,
    From the ELM snapshot, there is no Unused license. This means all licenses are  being consumed.
    Can u please click on View Usage report on Unassigned devices in CUCM is first attachment shared by you and check how licenses are being used?
    rgeds,
    aman

  • Call Manager, Tandberg Video Phone bandwidth

    We have recently rolled out a Tnadberg Video Phone.
    Is the Tandberg phone considered an endpoint in call manager?
    Can you adjust what bandwidth the phone uses from within call manager?

    Locations in Cisco Unified CallManager Administration specify how much audio and video bandwidth is allowed for all calls in a specific location.

  • Call Manager and Avaya Phones

    Hello Guys,
    I am running Cisco Call Manager 7.0. I ahve 2 Avaya 4620 IP Phones and want to add them to my existing VOIP network. How do I go about doing this? All of my other phones are Cisco 79xx.

    I tkink you can add avaya phone to cisco environment as a thirt party  sip phones.

  • Call manager and IP phones

    after the basement remodel i will have a server and computer repair area for my testing. I have a call manager server and a couple of ip phones and would like to setup a phone at each of my families houses. what would i need and how would i set it up.

    there might be a way to do it using SIP but I have not done it and I am just giving you an idea of how to do it with SCCP default and in a secure way
    Forget about the router model I was talking about.
    You would have to assume that your home where the CCM is as the Main site and pretty much have all othere families as remote sites, you would need to setup VPN between the houses and if you want everyone to dial each other you would need DMVPN(Dynamic Multipoint).
    You would need a good router at the main site, depending on how many sites you have you may be able to use just a 2801. For the remote sites, I would think you can use an 871 or 831 router which does VPN and also has a few PoE ports switch.
    You would have to create tunnels between each other house.
    JoeL

  • Calls record on Cisco Phones

    Hi,
    I just want to know that if i will change my cisco ip phone with another cisco ip phone (same model or different model) is it possible to move all the missed, received and placed calls data onto the new phone?
    These phones would be registered to Cisco CallManager 7.1.5.

    Hi,
    the phone maintains logs of all missed, recived and placed calls.
    you cannot move them..
    http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7962g_7961g_7961g-ge_7942g_7941g_7941g-ge/8_0/english/user/guide/62614241log.html
    regds,
    aman

  • Call Manager 5.1 How to calculate UM phone "points"

    We are going to install a new UM 4.x on call manager 5.1. phones = 800 , mix of several models.
    I spoke w/ Ingram Micro and they stated that UM 5.x requires "points" to enable the phones.
    7911 = 4 points
    7970 = 5 points
    7940 = 4 points
    Softphone = 3 points
    Where is it documented the "points" system, any info I can read ?
    Any reply would be great

    Hi Mark,
    This is correct :) These points are called Device License Units (DLU's). Here is some more detailed info;
    Device licenses are required for Cisco devices and for third-party devices, with the flexibility to replace third-party devices with Cisco devices. Device licenses are sold in increments of device-license units (DLU's). Device-license units are assigned to each device connected to Cisco Unified CallManager 5.0. Each device is assigned a unit number based on the type and capabilities of the device. Devices with more complex and high-end capabilities are assigned a higher number of units compared to devices with basic capabilities,
    Here is the DLU breakdown;
    Cisco Unified IP Phone 7902G = 1
    Cisco Unified IP Phone 7905G = 2
    Cisco Unified IP Phone 7911G = 3
    Cisco Unified IP Phone 7912G = 3
    Cisco Unified Wireless IP Phone 7920 (no battery) = 4
    Cisco Unified IP Conference Station 7936 = 3
    Cisco Unified IP Phone 7940G = 4
    Cisco Unified IP Phone 7941G = 4
    Cisco Unified IP Phone 7941G-GE = 4
    Cisco Unified IP Phone 7960G = 4
    Cisco Unified IP Phone 7961G = 4
    Cisco Unified IP Phone 7961G-GE = 4
    Cisco Unified IP Phone 7970G = 5
    Cisco Unified IP Phone 7971G = 5
    Cisco Unified IP Phone 7985G = 6
    Third-party SIP device (basic) = 3 (third-party)
    Third-party SIP device (advanced) = 6 (third-party
    From this doc;
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_qanda_item0900aecd805009fc.shtml
    Here is another excellent doc;
    http://www.cisco.com/warp/public/765/tools/quickreference/ipphones.pdf
    Hope this helps!
    Rob

  • CUCM 8.6 Dropped call transfers involving SIP phones

    Hi All,
    I am a developer who has been tasked with figuring out why call transfers are being dropped by Cisco CUCM when the original call comes from a SIP phone.  This scenario works:
    Cisco phone calls another Cisco phone, which transfers the original call to a SIP phone
    These scenarios do not work:
    SIP phone calls Cisco phone, which transfers the original call to another Cisco phone
    SIP phone calls Cisco phone, which transfers the original call to another SIP phone
    I have researched the Call Manager traces to the best of my ability, and I see some info in there that could potentially point to the source of the problem.  I am just unable to understand what the trace means:
    10:23:08.672 |//SIP/SIPCdpc(1,74,2342)/ci=24377698/ccbId=175645/scbId=0/active_CcDisconnReq: ccDisconnReq.onBehalfOf=Media : ccDisconnReq.s.sv=2 : ccDisconnReq.c.cv=47 |1,100,63,1.93259^10.10.10.85^*
    10:23:08.672 |//SIP/Stack/Info/0x0/sipConstructContainerContext #### Created container=0xb0b42f58|1,100,71,1.1^*^*
    10:23:08.672 |//SIP/SIPCdpc(1,74,2342)/ci=24377698/ccbId=175645/scbId=0/appendReasonHdr: appendReasonHdr - Invalid Disconnect Cause(cause=47), No Reason Header Appended|1,100,63,1.93259^10.10.10.85^*
    10:23:08.672 |//SIP/SIPCdpc(1,74,2342)/ci=24377698/ccbId=175645/scbId=0/appendRPIDHdrForOriginalCalledParty: SIP device does not Support Orig Dialled Phone nego: 0|1,100,63,1.93259^10.10.10.85^*
    I have been wondering whether this could be a codec issue, however the SIP phones we are using are configured with the following codecs:
    G711U
    G711A
    G722
    ILBC
    GSM
    and our SIP software is  also set to accept the first codec offered by the remote side.  It seems from the SIP client logs that G722 is being used as the codec to communicate with the Cisco phones, but perhaps I'm misinterpreting.
    I have attached a CUCM trace of a call from a SIP phone (ext. 491) to a Cisco handset (ext. 170) where the Cisco handset attempts to transfer the call to another SIP phone (ext. 492).  The trace snippet shown above is from this log.
    I would really appreciate it if someone more experienced with VoIP/SIP/CUCM could take a look and offer any ideas on what the issue might be, and also how we might be able to address it.  I can try to provide more info about our CUCM configuration if needed.
    Thanks in advance!

    Leslie, so here is what I found from the traces....
    To understand the difference we need to understand how cucm performs call transfers from a sccp signalling point and a sip signalling point
    SCCP
    When the transfer key is pressed
    1. CUCM sends a CloseReceiveChannel and StopMediaTransmission to the IP phone involved in active media (referenced by the callids)
    NB, here CUCM updates the call state on the phone to a call state of 8 which is "Hold"
    2.CUCM tells the held party to listen MOH from MOH server
    3.CUCM establishes newcall leg with the intended transfered destination..Once this call is connected
    4.CUCM receives a new Transfer instruction from the transferring phone to connect the held party
    5..CUCM sends a CloseReceiveChannel between the held phone and MOH server (to tear down the media)
    6. Next CUCM sends a CloseReceiveChannel and StopMediaTransmission to the transfering party & transfered party to remove Xferring party from call
    7. finally CUCM sends OpenReceiveChannel between the original called party and the transfered party..and call is done
    For SIP signalling. when the first transfer key is pressed
    1. CUCM sends invite (re-invite) with an inactive SDP (a=inactive) to indicate a break in media path
    2. CUCM sends a Delayed offer to insert MOH or to resume Media stream
    NB: CUCM expects a sendrecv offer with SDP to the DO. (NB:if cucm gets an inactive offer SDP in the 200 OK instead of providing a send-recv offer SDP, the media path remains in an inactive state and causes calls to dropcall will drop),CUCM sends an ACK with sendonly to the 200 OK
    3.CUCM establishes newcall leg with the intended transfered destination..Once this call is connected
    4.CUCM receives a new Transfer instruction from the transferring phone to connect the held party
    5. Next CUCM sends a re-invite with an inactive SDP to indicate a break in media path to MOH (in attempt to complete transfer)
    6.Next CUCM sends an inactive SDP to indicate a break in media path between transfering party & transfered party to remove Xferring party from call
    7. Next CUCM sends a DO re-invite to connect the transfered party. The far end then sends 200 OK with the required SDP to connect the call
    Now having explained all of these, we need to look at where the call is failing for SIP-----SCCP----SIP calls without MTP
    lets look at succesful SCCP-----SCCP-----SIP without MTP
    Point 4 above
    ++++++++Extension 170 presses the transfer button to connect the two calls (Callid=24378483)+++++++++++++
    (0003395) SoftKeyEvent softKeyEvent=4(Trnsfer) lineInstance=1 callReference=24378483
    Point 5 above
    ++++Next CUCM closed the media between extension 160 and MOH server callid=24378480(this is the only active call on this callid)+++
    (0003396) CloseReceiveChannel conferenceID=24378480 passThruPartyID=16777845.  myIP: IpAddr.type:0 ipv4Addr:0x0a0a0a89(10.10.10.137)
    Point 6 Above
    +++++Next cucm closes the call between extension 170 and 490 callid=(24378483)++++++++
    (0003395) CloseReceiveChannel conferenceID=24378483 passThruPartyID=16777847.  myIP: IpAddr.type:0 ipv4Addr:0x0a0a0a8b(10.10.10.139)
    (0003395) StopMediaTransmission conferenceID=24378483 passThruPartyID=16777847.  myIP: IpAddr.type:0 ipv4Addr:0x0a0a0a8b(10.10.10.139)
    Point 6 above for the sip side (since the destination is SIP, to tear down media to SCCP phone, so as to connect the caller to the xfered party)
    +++++++Next CUCM sends a re-invite with a=inactive SDP to the sip phone ++++++++++++
    //SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.10.10.104 on port 62220 index 1890
    [885626,NET]
    INVITE sip:[email protected]:62220;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK23332dbee978
    From: ;tag=192115~d8e94532-127d-4dca-bba0-64b1675da032-24378484
    o=CiscoSystemsCCM-SIP 192115 2 IN IP4 10.10.10.195
    s=SIP Call
    c=IN IP4 0.0.0.0
    m=audio 24560 RTP/AVP 9 101
    a=rtpmap:9 G722/8000
    a=ptime:20
    a=inactive-----------------------------------------------------Inactive
    Still part of Point 6 for SIP signalling
    ++++++++++++Next sip phone responds with a 200 OK recevonly SDP +++++++++++++++++++
    //SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.10.10.104 on port 62220 index 1890 with 683 bytes:
    [885628,NET]
    SIP/2.0 200 OK
    v=0
    o=- 18077 11099 IN IP4 10.10.10.104
    s=yasdjip
    c=IN IP4 10.10.10.104
    t=0 0
    a=ptime:20
    a=recvonly-------------------------------------a=recvonly
    Finally Point 7 above..
    +++++++++++++=Next cucm sends a DO re-invite to extension 492-sip phone++++++++++
    //SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.10.10.104 on port 62220 index 1890
    [885630,NET]
    INVITE sip:[email protected]:62220;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK233534ffec4a
    From: ;tag=192115~d8e94532-127d-4dca-bba0-64b1675da032-24378484
    To: ;tag=5B0E9816C2CA6D70F3166FB972EDE4C2
    +++++++Next we get a 200 OK from sip phone with sdp=sendrecv+++++++++=
    /SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.10.10.104 on port 62220 index 1890 with 683 bytes:
    [885634,NET]
    SIP/2.0 200 OK
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK233534ffec4a
    Contact:
    From: ;tag=192115~d8e94532-127d-4dca-bba0-64b1675da032-24378484
    Call-ID: [email protected]
    v=0
    o=- 18077 11099 IN IP4 10.10.10.104
    s=yasdjip
    c=IN IP4 10.10.10.104
    t=0 0
    m=audio 16574 RTP/AVP 9 101
    a=rtpmap:101 TELEPHONE-EVENT/8000
    a=fmtp:101 0-15
    a=ptime:20
    a=sendrecv
    +Now CUCM sends an OpenReceiveChannel and start media xmission to sccp phone (callid=24378480) with media parameters of sip phone++++++
    (0003396) OpenReceiveChannel conferenceID=24378480 passThruPartyID=16777848 millisecondPacketSize=20 compressionType=6(Media_Payload_G722_64k) RFC2833PayloadType=101 qualifierIn=? sourceIpAddr=IpAddr.type:0 ipAddr:0x0a0a0a68000000000000000000000000(10.10.10.104). myIP: IpAddr.type:0 ipv4Addr:0x0a0a0a89(10.10.10.137)
    (0003396) startMediaTransmission conferenceID=24378480 passThruPartyID=16777848 remoteIpAddress=IpAddr.type:0 ipAddr:0x0a0a0a68000000000000000000000000(10.10.10.104)
    remotePortNumber=16574 milliSecondPacketSize=20 compressType=6(Media_Payload_G722_64k) RFC2833PayloadType=101 qualifierOut=?. myIP: IpAddr.type:0 ipv4Addr:0x0a0a0a89(10.10.10.137)
    +++++++++++=Next Phone sends its ACK+++++++++++++++
    (0003396) OpenReceiveChannelAck Status=0, IpAddr=IpAddr.type:0 ipAddr:0x0a0a0a89000000000000000000000000(10.10.10.137), Port=20352, PartyID=16777848
    +++++++++++=Next CUCM sends ACK to 200 OK from SIP Phone+++++++++++
    //SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.10.10.104 on port 62220 index 1890
    [885635,NET]
    ACK sip:[email protected]:62220;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK23366067b8c0
    From: ;tag=192115~d8e94532-127d-4dca-bba0-64b1675da032-24378484
    To: ;tag=5B0E9816C2CA6D70F3166FB972EDE4C2
    Date: Tue, 19 Feb 2013 21:44:45 GMT
    Call-ID: [email protected]
    Max-Forwards: 70
    CSeq: 103 ACK
    Allow-Events: presence
    Content-Type: application/sdp
    Content-Length: 237
    v=0
    o=CiscoSystemsCCM-SIP 192115 3 IN IP4 10.10.10.195
    s=SIP Call
    c=IN IP4 10.10.10.137
    b=TIAS:64000
    b=AS:64
    t=0 0
    m=audio 20352 RTP/AVP 9 101
    a=rtpmap:9 G722/8000
    a=ptime:20
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    Now at this point all is well...and the call is connected....
    Now here is where the call is failing on the SIP-SCCP-SIP call without MTP
    From Point 2 above, CUCM sends a DO to insert MOH, and then gets response, then sends an ACK to 200 Ok back to SIP Phone..
    //SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.10.10.104 on port 53361 index 1810
    [881160,NET]
    ACK sip:[email protected]:53361;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK22035ecc1fcb
    From: ;tag=190666~d8e94532-127d-4dca-bba0-64b1675da032-24378214
    To: "492" ;tag=97C34E1FB9A11F83DD8D8F5BA4C87C57
    Date: Tue, 19 Feb 2013 17:38:50 GMT
    Call-ID: 1CCA5149B966DC89AE0F752B8EF86480BC7102DB
    Max-Forwards: 70
    CSeq: 102 ACK
    o=CiscoSystemsCCM-SIP 190666 3 IN IP4 10.10.10.195
    s=SIP Call
    c=IN IP4 10.10.10.195---------------------------------------IP address of MOH server
    t=0 0
    m=audio 4000 RTP/AVP 0--------------------------------MOH port 4000
    a=rtpmap:0 PCMU/8000
    a=ptime:20
    a=sendonly---------------------------------------------------------sendonly
    +++++NOW Point 6 above (SIP) CUCM sends a=inactive to break media path to MOH server to connect caller and xfered party++++++
    //SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.10.10.104 on port 53361 index 1810
    [881161,NET]
    INVITE sip:[email protected]:53361;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK22045bb7f918
    From: ;tag=190666~d8e94532-127d-4dca-bba0-64b1675da032-24378214
    To: "492" ;tag=97C34E1FB9A11F83DD8D8F5BA4C87C57
    Date: Tue, 19 Feb 2013 17:39:04 GMT
    Call-ID: 1CCA5149B966DC89AE0F752B8EF86480BC7102DB
    Supported: timer,resource-priority,replaces
    Min-SE:  1800
    User-Agent: Cisco-CUCM8.6
    Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
    CSeq: 103 INVITE
    Max-Forwards: 70
    Expires: 180
    Allow-Events: presence
    Remote-Party-ID: ;party=calling;screen=yes;privacy=off
    Contact:
    Content-Type: application/sdp
    Content-Length: 164
    v=0
    o=CiscoSystemsCCM-SIP 190666 4 IN IP4 10.10.10.195
    s=SIP Call
    c=IN IP4 0.0.0.0--------------------------------------------------------------------Media IP is 0.0.0.0
    t=0 0
    m=audio 4000 RTP/AVP 0
    a=rtpmap:0 PCMU/8000
    a=ptime:20
    a=inactive---------------------------------------------------------------------media inactive
    At this point, we should get a response back from the sip phone...
    and here is what we got..
    ++Trying which is expected++++
    //SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.10.10.104 on port 53361 index 1810 with 331 bytes:
    [881162,NET]
    SIP/2.0 100 Trying
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK22045bb7f918
    From: ;tag=190666~d8e94532-127d-4dca-bba0-64b1675da032-24378214
    Call-ID: 1CCA5149B966DC89AE0F752B8EF86480BC7102DB
    CSeq: 103 INVITE
    To: "492" ;tag=97C34E1FB9A11F83DD8D8F5BA4C87C57
    Content-Length: 0
    ++++++++Then we get a BYE+++++++++++++++
    /SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.10.10.104 on port 53361 index 1810 with 576 bytes:
    [881163,NET]
    BYE sip:[email protected]:5060;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.104:53361;branch=z9hG4bKa2vdQvR7J9OiMyjU;rport
    Contact:
    Max-Forwards: 70
    From: "492" ;tag=97C34E1FB9A11F83DD8D8F5BA4C87C57
    Allow: OPTIONS, INVITE, ACK, REFER, CANCEL, BYE, NOTIFY
    Supported: replaces, path
    User-Agent: Acrobits Softphone Business/2.4.8
    To: ;tag=190666~d8e94532-127d-4dca-bba0-64b1675da032-24378214
    Call-ID: 1CCA5149B966DC89AE0F752B8EF86480BC7102DB
    CSeq: 3 BYE
    Content-Length: 0
    So this is the root cause of the problem. Your SIP phone does not know how to respond to multiple media break between it and the MOH server.
    The difference between this and the succesful SCCP-SIP--SCCP, is that the held party was a sccp phone, hence the sip phone only has to process one a=inactive SDP message, where as in the SIP-SCCP-SIP, the help party was sip, so the sip phone has to process two a=inactive SDP messages
    Now what is the difference when MTP is involved! A Big difference. MTP stays in the media path. So there is never a break in media and no inactive SDP attribute is sent. The flow looks like below:
    for the initial call...The SIP phone sends its media to MTP and likewise the SCCP phone
    SIP------Media------MTP------------Media-------SCCP Phone
    When the new destination is dialled and transfer is commited,
    SIP-------------media----MTP--------media---------MTP
    The final invoite sent to connect 492 and 491 has MTP as the IP address to connect Media to.
    ++++++++Ivite to 492 ++++++++++++++
    INVITE sip:[email protected]:61303;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK231a3b24b862
    From: ;tag=192048~d8e94532-127d-4dca-bba0-64b1675da032-24378472
    To: ;tag=78FF5BF6C019A55EA020B69BB6A767E2
    Date: Tue, 19 Feb 2013 21:24:59 GMT
    Call-ID: [email protected]
    Supported: timer,resource-priority,replaces
    Min-SE:  1800
    User-Agent: Cisco-CUCM8.6
    Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
    CSeq: 102 INVITE
    Max-Forwards: 70
    Expires: 180
    Allow-Events: presence
    Remote-Party-ID: ;party=calling;screen=yes;privacy=off
    Contact:
    Content-Type: application/sdp
    Content-Length: 214
    v=0
    o=CiscoSystemsCCM-SIP 192048 1 IN IP4 10.10.10.195
    s=SIP Call
    c=IN IP4 10.10.10.195---------------------------------------------------------------the MTP ip address
    t=0 0
    m=audio 25038 RTP/AVP 0 101
    a=rtpmap:0 PCMU/8000
    a=ptime:20
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    +++++++Invite to 491 +++++++++++++++++
    //SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.10.10.94 on port 50376 index 1887
    [885429,NET]
    INVITE sip:[email protected]:50376;transport=tcp SIP/2.0
    Via: SIP/2.0/TCP 10.10.10.195:5060;branch=z9hG4bK231b78d1b56
    From: ;tag=192046~d8e94532-127d-4dca-bba0-64b1675da032-24378467
    To: "491" ;tag=F13CE94DE942C47680356A647DC7F916
    Date: Tue, 19 Feb 2013 21:24:59 GMT
    Call-ID: AE7045FFB2D8D9C28D54651473A14A5D41B5B93C
    Supported: timer,resource-priority,replaces
    Min-SE:  1800
    User-Agent: Cisco-CUCM8.6
    Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
    CSeq: 101 INVITE
    Max-Forwards: 70
    Expires: 180
    Allow-Events: presence
    Remote-Party-ID: "Leslie2" ;party=calling;screen=no;privacy=off
    Contact:
    Content-Type: application/sdp
    Content-Length: 237
    v=0
    o=CiscoSystemsCCM-SIP 192046 1 IN IP4 10.10.10.195
    s=SIP Call
    c=IN IP4 10.10.10.195----------------------------------------MTP
    b=TIAS:64000
    b=AS:64
    t=0 0
    m=audio 25030 RTP/AVP 0 101
    a=rtpmap:0 PCMU/8000
    a=ptime:20
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    Wao! That was a long one isnt it...It was fun too.
    So now you can look at your sip phones and see if they can accept two inactive sdp messages within the same call. That way you can remove MTP. otherwise you will have MTP involved in every single call involving a sip phone, even if they do not involve transfers
    Please rate all useful posts
    "opportunity is a haughty goddess who waste no time with those who are unprepared"

  • Call Manager & Telepresence

    Hi,
    Do we need Call Manager for Cisco Telepresence Codec C40 Point to Point connection?
    Thanks,

    Hi,
    No need CUCM for Point-Point connection.
    You may use search :
    https://supportforums.cisco.com/discussion/12158971/mx300-endpoint-standalone
    https://supportforums.cisco.com/discussion/12384286/standalone-two-ex90-public-ip-can-make-video-calls-among-them-self-over-internet   see Jens post
    https://supportforums.cisco.com/discussion/11307921/how-do-i-point-public-ip-address-my-tandberg-unit
    br Oleksandr

  • Cisco ip phone 7960 cannot connect to call manager express

    The 7960 ip phone seems not to connect to the call manager express
    router and i have already put the firmware and configured the tftp
    server,the rest of the phones the 7911`s are all working ok,i have tried
    to reset the phone but it doesnt respond to the # key so as to reset to
    factory defaults.
    I have tried all the options of resetting it but to no avail.
    could someone give me some techie tips on this ? could it be a hardware issue ?? please assist.

    Go to the phone and check if the TFTP server is correct (should be the CME IP address). Also check the DHCP address.
    Resetting 7900 Series IP Phones to Factory Defaults:
    http://www.cisco.com/en/US/products/hw/phones/ps379/products_tech_note09186a00800941bb.shtml
    Check the bug:
    CSCed93627: Not able to reset 7970 back to factory defaults

  • Cdr doesn't bill Cisco phone 6901 Call Manager release 9

    Hello Engineers,
    Actually I opened a TAC for a problem that I got in my customer's environment.
    I have CUCM release 9 and Cisco phone 6901 - firmware: SCCP6901.9-3-2.loads
    When I tried to see the calls from CAR I didn't get output from the CAR/CDR.
    I did an upload to the firmware SCCP6901.9-3-1-SR1-3.loads.
    After that all calls were ok.
    I hope this post can help anothers engineers

    Hi Karina,
    Thanks for taking time out of your busy schedule to help others
    here @ CSC Much appreciated!
    Cheers!
    Rob
    "Seek it out and ye shall find  " 
    - OneRepublic

  • Hi Team, I wuold like to know if you have any app to make Firefox OS working with cisco Call Manager 10.5. Something like Cisco Jabber for Android or iOS.

    I'm interesting on buying a Firefox Smart Phone, but
    I would like to know if are any app to install on Firefox OS smart phone in order to work with cisco call manager 10.5.
    Something like Cisco Jabber for Android o iOS.
    Thanks,

    Hi Itech,
    If Cisco Jabber has a webapp, or mobile version of their website available, you should technically be able to access it through Firefox OS.
    You may also search Firefox Marketplace for an alternative solution:
    * [https://marketplace.firefox.com/]
    - Ralph

Maybe you are looking for