locked
Outbound PSTN Calling from an OCS Response Group RRS feed

  • Question

  • When I call a OCS Response Group from PSTN the call end witout the transfer beeing done to a PSTN number.

    If I call the same Response group from a OCS phone the treanfer is done correcly.

    I have the problem since I have instaled the april updates. Before it was working ok.

     

    The log says:

    TL_INFO(TF_PROTOCOL) [2]0AB0.1714::06/07/2010-12:33:42.397.0005a693 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 000122D7
    Direction: outgoing;source="local"
    Peer: OCSMediation.reseau.cvm:51804
    Message-Type: response
    Start-Line: SIP/2.0 404 Not Found
    From: <sip:+15140002110@reseau.cvm;user=phone>;epid=64A4C47F02;tag=d5956d322c
    To: <sip:+15140002110@reseau.cvm;user=phone>;tag=55EA870F88E7C9F8C71ACDA4395B7DC4
    CSeq: 4688 SERVICE
    Call-ID: 38e5a5c18979473ebac58be43e51ba0b
    Via: SIP/2.0/TLS 10.19.3.154:51804;branch=z9hG4bKeae693d;ms-received-port=51804;ms-received-cid=6F200
    ms-diagnostics: 1003;reason="User does not exist";source="OCS1.reseau.cvm";TargetUri="+15140002110@reseau.cvm"
    Content-Length: 0
    Message-Body: –
    $$end_record

     

    Also:

     

    Creating a OutboundRoutingTransaction object (208)
    Enter
    Enter.
    From uri: +15140002110@reseau.cvm
    From User Uc Enabled: False
    From User Policy: <null>
    Referrer URI: <null>
    IsAvMCUDialOut: False
    Applying From URI's outbound policy
    Routing request based on caller: +15140002110@reseau.cvm
    Caller not UC enabled.
    Stamping request from non UC enabled user
    Exit

    I have applied the correction proposed on http://blogs.technet.com/b/dougl/archive/2009/08/12/outbound-pstn-calling-from-response-groups.aspx

     

    I sill have the problem

     

    Alain

    Monday, June 7, 2010 5:56 PM

All replies

  • Alain, we have this same issue. Since the April updates, we're unable to route calls to any external numbers via Response Group.

    The workaround I used was to create a new user, and set that user to forward all calls to the external number.

    In the Response Group settings, I set the action to forward to a SIP URI instead of Telehone Number.

    Thursday, June 10, 2010 11:37 PM
  • Hi Alain,

    This is unfortunately a known issue when applying the latest cumulative update (CU5) to the mediation server. The product group is currently working on a fix, stay tuned...

    Cheers,
    Frédéric

    Monday, June 14, 2010 6:26 AM
  • I am also experiencing the same behavior.  Is it ok to remove KB977937 from the mediation servers until the next update?
    Monday, June 28, 2010 9:10 PM
  • Any update on this from the Product Group on a potential fix date?  I'm also experiencing this issue and have been using the same workaround as RLiberty.  Would like to get this issue resolved and remove the cumbersome workaround...
    Trevor
    Wednesday, July 7, 2010 3:13 PM
  • I have found that removing both Mediation server and UC Managed API Core Redist updates from April 2010 restores the previous functionality.
    Wednesday, July 14, 2010 9:01 PM
  • 2010 July update pack has fixed this (at least that is what they promise). Just be warned, my OCS EE env. was completely screwed up after installing this pack, so test everything first, before going to production.
    Sunday, July 25, 2010 5:41 AM
  • On that note, check out this link.

     

    If installing the July updates, you MUST install the DB backend update first, silly I know...

     

    http://www.confusedamused.com/notebook/ocs-2007-r2-cumulative-update-6-and-stored-procedure-mismatches/

     

     


    Randy Wintle | MCTS: UC Voice Specialization | Winxnet Inc
    Tuesday, July 27, 2010 12:45 PM
  • Thanks, already found the solution by myself. Another successful update story of OCS...
    Tuesday, July 27, 2010 6:42 PM