locked
No Call Forward option in OC, users configured for RCC RRS feed

  • Question

  • OCS 2007 R2 (2x EE front end servers behind F5 LTM HLBs), clients running OC 3.5.6907.0 or 3.5.6907.206

    Clients are configured for RCC and it is working fine (place / answer calls, call control, etc all working). None of the clients have the phone icon at the top right of the OC interface so are unable to set Call Forwarding options from the client. No options are available for Call Forwarding from CWA either (i.e as explained here: http://communicatorteam.com/archive/2008/05/29/251.aspx). I understand there is a DisablRCCForwarding registry / GP setting, have confirmed this is not set.

    Hoping someone can point me in the right direction.

    Thanks.

    Friday, October 1, 2010 2:32 AM

All replies

  • Hello,

    How are your users configured in AD?

    As: "Enable Remote call control"
    Or: "Enable Enterprise Voice" + "Enable PBX Integration" ?

    Both options will give RCC functions, but my guess is that you will not see call forwarding with the first option.

    /mk

    Friday, October 1, 2010 6:59 AM
  • What PBX are you doing RCC with?
    http://blog.lyncdialog.com/
    Monday, October 4, 2010 6:54 AM
  • Thanks for your response. The users are configured as Enable Remote Call Control only. Haven't tested them configured as EV since we are using RCC with a remote PBX

    Thursday, October 7, 2010 6:10 AM
  • PBX is a hosted BroadSoft BroadWorks platform
    Thursday, October 7, 2010 6:11 AM
  • Just tested with a user configured for EV + PBX integration and RCC, etc still works, but still no call fwd phone icon
    Thursday, October 7, 2010 6:15 AM
  • The problem I believe is when the Broadvox system is sending back the the response to the GetCSTAFeatures request, call forwarding is not one of the items in the list. Look at the example I have below and you can compare to your logs.

    TL_INFO(TF_PROTOCOL) [0]0700.0B88::01/22/2008-15:00:11.243.0000abb2 (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record
    Instance-Id: 000007EE
    Direction: outgoing
    Peer: 192.164.113.137:3449
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: <sip:someone@demo.net>;tag=f9c1404611;epid=f60275d516
    To:
    <sip:4115;phone-context=cdp.udp@CtfOcsProxySrv.demo.net>;tag=19182700-6a71a42f-13c4-40030-246ed-87f914b-246ed
    CSeq: 2 INFO
    Call-ID: 43b8e87da6574930a5ffef8ec55e37e8
    Content-Length: 1048
    Content-Dishandling=required
    Via: SIP/2.0/TCP 192.164.113.137:3449;branch=z9hG4bKE8D4DCEE.DFAF4230;branched=FALSE;ms-received-port=3449;ms-received-cid=3E00
    Via: SIP/2.0/TCP 192.164.154.177:1202;ms-received-port=1202;ms-received-cid=5800
    Supported: 100rel,x-nortel-sipvc,replaces,timer
    User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
    Contact: <sip:4115;phone-context=cdp.udp@demo.net:5060;maddr=192.164.113.106;transport=tcp;x-nt-net-feature=x-nt-redirect;x-nt-redirect=redirect-server>
    Content-Type: application/csta+xml
    Message-Body: <?xml version="1.0" encoding="UTF-8"?><GetCSTAFeaturesResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><supportedServices><systemStatServList><requestSystemStatus /></systemStatServList><monitoringServList>
    <monitorStart /><monitorStop /></monitoringServList><callControlServList><answerCall /><clearConnection />
    <conferenceCall /><consultationCall /><deflectCall /><holdCall /><makeCall /><retrieveCall /><singleStepTransfer />
    <transferCall /></callControlServList><callAssociatedServList><generateDigits /></callAssociatedServList><logicalServList>
    <getDoNotDisturb /><getForwarding /><setDoNotDisturb /><setForwarding /></logicalServList></supportedServices>
    <supportedEvents><callControlEvtsList><conferenced /><connectionCleared /><delivered /><diverted /><established />
    <failed /><held /><originated /><retrieved /><transferred /></callControlEvtsList><logicalEvtsList><doNotDisturb />
    <forwarding /></logicalEvtsList></supportedEvents></GetCSTAFeaturesResponse>


    http://blog.lyncdialog.com/
    Thursday, October 7, 2010 2:49 PM
  • Thanks Jon. I'll see if I can get my hands on a sample GetCSTAFeatures response from the PBX and compare. Could take some time unfortunately, I need to do it via a service request from our hosting provider.
    Thursday, October 7, 2010 11:11 PM
  • You should be able to see it from client logs if you turn them on via the Options menu. You can install the OCS 2007 Res Kit and use snooper to make it easier to view.

    jonmck


    http://blog.lyncdialog.com/
    Friday, October 8, 2010 12:57 AM
  • oops, thanks for that. Yep, this is what I'm seeing (as you say, looks like no forwarding items):

    <?xml version="1.0" encoding="UTF-8"?>

    <GetCSTAFeaturesResponse

    xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

    <supportedServices>

    <systemStatServList>

    <requestSystemStatus/>

    </systemStatServList>

    <monitoringServList>

    <monitorStart/>

    <monitorStop/>

    </monitoringServList>

    <callControlServList>

    <alternateCall/>

    <answerCall/>

    <clearConnection/>

    <conferenceCall/>

    <consultationCall/>

    <deflectCall/>

    <dialDigits/>

    <holdCall/>

    <makeCall/>

    <transferCall/>

    <retrieveCall/>

    <singleStepTransfer/>

    </callControlServList>

    </supportedServices>

    <supportedEvents>

    <callControlEvtsList>

    <conferenced/>

    <connectionCleared/>

    <delivered/>

    <diverted/>

    <established/>

    <failed/>

    <held/>

    <originated/>

    <retrieved/>

    <transferred/>

    </callControlEvtsList>

    </supportedEvents>

    </

     

    GetCSTAFeaturesResponse>

    Sunday, October 10, 2010 11:33 PM
  • Looks like the BroadSoft platform doesn't support that feature. Might give them a call and see if it is something they can enable.

    -jonmck


    http://blog.lyncdialog.com/
    Monday, October 11, 2010 1:00 AM