Menu

#465 Hold doesn't work with Cisco CallManager 7

Invalid
nobody
None
Medium
Defect
2010-12-08
2010-12-08
Anonymous
No

Originally created by: aydei...@gmail.com

What steps will reproduce the problem?
1.Connect a call
2.Press the "pause" button on the phone to put the call on hold
3.

What is the expected output? What do you see instead?
Expect Cisco phones with shared lines to show the call has been placed on hold so it can be picked up

What version of the product are you using? On what operating system?
0.00-16 [r410] on Android 2.2

Please provide any additional information below.
On the Android itself, the call can be placed on hold and taken off hold without a problem, but the Cisco phones sharing that extension do not recognize the call has been placed on hold

Related

Commit: [r410]

Discussion

  • Anonymous

    Anonymous - 2010-12-08

    Originally posted by: r3gis...@gmail.com

    And CSipSimple UI changes to something yellow? Or it just ignore your hold request?
    (Maybe it's just not supported as a SIP command by the Cisco phones).

     
  • Anonymous

    Anonymous - 2010-12-08

    Originally posted by: aydei...@gmail.com

    The UI does change to a yellow background when placed on hold, and will switch back to green when taken off hold

     
  • Anonymous

    Anonymous - 2010-12-08

    Originally posted by: r3gis...@gmail.com

    So I guess that's something with your phone that doesn't interpret the SIP message.
    Is the call actually hold? (I mean other party doesn't hear you anymore?)

    If so I guess these Cisco phones doesn't use SIP standard to interpret Hold feature. They have maybe their own proprietary protocol.

    <mode alcatel employee on> Use Alcatel phones instead :p<mode alcatel employee off>

    Seriously again. Did you try with other SIP phones? Which have the hold feature working?
    CSipSimple relies on the pjsip SIP stack and pjsip coders try to respect RFC. I'm not really expert in their implementation but most of the time I was really impressed by the fact they really follow RFCs. If there is something wrong with the implementation I can report to pjsip coders, but I'll need more infos to report them a precise info about what is going wrong with SIP packets they send.

     
  • Anonymous

    Anonymous - 2010-12-08

    Originally posted by: aydei...@gmail.com

    I just spoke with my network admin, and he says the Cisco phones are using SCCP.

    I did a call from my phone to his, and put him on hold using CSIPSimple.  It did successfully hold (he couldn't hear me anymore, and vice versa), and it did successfully resume.  However, the hold music from the CCM7 server didn't play, and the other Cisco phones with the shared extension (Cisco IP phone 7961) registered the phone as off the hook, but not on hold

     
  • Anonymous

    Anonymous - 2010-12-08

    Originally posted by: r3gis...@gmail.com

    Ok, quiet normal if CCM7 doesn't use *SIP* to hold calls.
    So I think it's not a bug in CSipSimple, it is just your equipment that is not compatible with this SIP features. I think the server should do the conversion from SIP to SCCP but do not.

    I think that any SIP client that you'll use will produce exactly the same result.

    At least that's for the hold feature. For transfer feature on your other issue, for now it's a alpha feature that is included in CSipSimple, I'll merge that with the other open corresponding issue. While the issue 305 is not marked as fixed I consider that transfer and conference are not useable so other issue regarding this feature will be merged. However it could also be something with the "SIP" server too. (But in this case I guess I should detect that your server doesn't support REPLACE (transfer) and don't propose you the feature. But this will be done for the implementation of the feature.

    Status: Invalid

     

    Related

    Tickets: #305


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.