Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
MOC2007 RCC PBX Integration Problm (Result-Code: 0xc3e93ec6 SIP_E_AUTH_CANNOT_CHALLENGE) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Greetings,

     

    OCS Setup:

     

    Enterprise Edition

    (4) FE server pool

    (1) Med server

    (1) Application proxy server

    (2) Redundant f5 load-balancers

     

    I am trying to get my MOC2007 clients integrated with a Nortel CS1K PBX, but I get the dreaded telephony integration error message on the clients. From the traces performed, I can see that the client originates the CSTA INVITE to the OCS FE Pool, and then to the PBX via a static route pointing to an application proxy servicing the Nortel's routing MCM application. The problem occurs when the PBX responds back to the client with the supported CSTA features. The "200 OK" packet is sent back by the PBX via the application proxy to the f5 VIP of the FE Pool. Once the assigned FE server receives the response, it does not forward it to the originating client and I see the resulting error warning message in the trace logs of the FE Pool:

     

    TL_WARN(TF_DIAG) [0]0C14.1470::06/17/2008-04:47:10.489.02d556bc (SIPStack,SIPAdminLog::TraceDiagRecord:1224.idx(142))$$begin_record
    LogType: diagnostic
    Severity: warning
    Text: Message was discarded by the application
    Result-Code: 0xc3e93ec6 SIP_E_AUTH_CANNOT_CHALLENGE
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 6a462c4ad5b940bea1fe38821e01123e
    SIP-CSeq: 1 INVITE
    Data: application="http://www.microsoft.com/LCS/UserServices"
    $$end_record

     

     

    I am at a loss.

     

    Any suggestions would be received with gratitude.

     

    Full packet trace and message:

     


    TL_INFO(TF_COMPONENT) [0]0C14.1470::06/17/2008-04:47:11.192.02d564a8 (SIPStack,CRecvContext:rocessCompletion:974.idx(155))( 05F83EE8 ) Received 1908 bytes
    TL_INFO(TF_PROTOCOL) [0]0C14.1470::06/17/2008-04:47:11.192.02d56531 (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record
    Instance-Id: 01E006E1
    Direction: incoming
    Peer: PKDWOCF07.EQ.Intranet:5061
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    From: <sip:UCTest02@Embarq.com>;tag=245d81eaa8;epid=b113200f68
    To: <sip:5347453;phone-context=udp@pkdwocf07.eq.intranet>;tag=180853f0-173e560a-13c4-40030-797fa-6ec7f57f-797fa
    CSeq: 2 INFO
    Call-ID: 6a462c4ad5b940bea1fe38821e01123e
    Content-Length: 1010
    Content-Disposition: signal;handling=required
    Via: SIP/2.0/TLS 10.206.150.171:4085;received=10.206.169.77;branch=z9hG4bKCAD1B3B0.562EC7BC;branched=FALSE;ms-received-port=4085;ms-received-cid=103200
    Via: SIP/2.0/TLS 10.86.34.245:1826;received=10.206.169.77;ms-received-port=1826;ms-received-cid=EA87F00
    Supported: 100rel,x-nortel-sipvc,replaces,timer
    User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
    Contact: <sip:5347453;phone-context=udp@Embarq:5060;maddr=10.86.62.23;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><getForwarding /><setForwarding /></logicalServList></supportedServices><supportedEvents><callControlEvtsList><conferenced /><connectionCleared /><delivered /><diverted /><established /><failed /><held /><originated /><retrieved /><transferred /></callControlEvtsList><logicalEvtsList><doNotDisturb /><forwarding /></logicalEvtsList></supportedEvents></GetCSTAFeaturesResponse>
    $$end_record

    TL_INFO(TF_COMPONENT) [0]0C14.1470::06/17/2008-04:47:11.192.02d56661 (SIPStack,CTransactionStateMachine::MakeStateTransition:1365.idx(576))( 03475F70 ) Event[TS_EV_RESPONSE_2XX] transitioned to state[TS_ST_INACTIVE] generating event[SIP_TRANSACTION_REPLY_SUCCESS_COMPLETED] timeout [0]
    TL_INFO(TF_COMPONENT) [0]0C14.1470::06/17/2008-04:47:11.192.02d566af (SIPStack,CModuleManager:ubmitItemToEM:85.idx(160))( 029D5CB8 ) Calling OnEvent into App [SIP_MODULE_ES][http://www.microsoft.com/LCS/UserServices][0x1] for eventIP_TRANSACTION_REPLY_SUCCESS_COMPLETED
    TL_WARN(TF_COMPONENT) [0]0C14.1470::06/17/2008-04:47:11.192.02d566c2 (SIPStack,CISIPMessage<ISIPResponse>::VerifySourceIdentity:1160.idx(3177))( 0928AE38 ) Exit - cannot challenge a response
    TL_WARN(TF_DIAG) [0]0C14.1470::06/17/2008-04:47:11.192.02d566ce (SIPStack,SIPAdminLog::TraceDiagRecord:1224.idx(142))$$begin_record
    LogType: diagnostic
    Severity: warning
    Text: Message was discarded by the application
    Result-Code: 0xc3e93ec6 SIP_E_AUTH_CANNOT_CHALLENGE
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: 6a462c4ad5b940bea1fe38821e01123e
    SIP-CSeq: 2 INFO
    Data: application="http://www.microsoft.com/LCS/UserServices"
    $$end_record

     

    Friday, June 20, 2008 1:25 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm pretty sure that your issue here is that the application proxy is responding to your NLB instead of talking directly to the FE server that sent the request.  Once initiated, I don't think the RCC conversation should not be going through your F5.

    Sunday, June 22, 2008 11:59 PM