SIP Timeout with noresource RRS feed

  • Question

  • First of all: Thanks a bunch for making the SIP logging tool availble on the OCS 07 beta. It really was much needed.


    On one of the VXML transfer in the OCS 07 beta server, we received timeout condition and the call was dropped. My question is: Will this situation result in a error.connection.noresource event?


    The following piece is from the SIP log seen using the tool:


    <<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_2BDA2AF>], GatewayID:GP<-OCSIPSurpriseCSP

    NOTIFY sipSurpriseCSBOX.DMZ.com:3365;transport=tcp;maddr=GatewayID SIP/2.0

    FROM: Gateway <sip:ani(callid-1184274345-479460-14146-2061)(location-OCSIP)@GW_HOST_IP:5061>;tag=callid-1184274345-479460-14146-2061ds-c5e-a435f56f

    TO: <sip:called_number@OCSBOX:5060>;tag=e8617a4d2

    CSEQ: 31398 NOTIFY

    CALL-ID: a85e5659-30bb-11dc-9eb2-877266f48410@GW.DMZ.com


    VIA: SIP/2.0/TCP OCSIP:5060;branch=z9hG4bKbd1c0e13-30bb-11dc-9ebc-cf5e572f9d44

    CONTACT: sipStick out tonguearaxipGateway@OCSIP:5060;transport=tcp


    EVENT: refer

    SUBSCRIPTION-STATE: terminated;reason=noresource

    CONTENT-TYPE: message/sipfrag;version=2.0


    SIP/2.0 408 Request Timeout

    ------------EndOfIncoming SipMessage




    Thursday, July 12, 2007 9:23 PM


  • Hi Ashish,


    Short answer is that you won’t get the "error.connection.noresource" event.


    In case of consultation transfer when the transfer fails with either SIP error code 408 (request timeout) or 504 (gateway timeout) then our VoiceXML implementation will set transfer status to "noanswer".


    In case of blind transfer you’ll receive either "connection.disconnect.hangup" event indicating that the current call was already disconnected when blind transfer was attempted or "connection.disconnect.transfer" event will be generated in all the other cases.

    Monday, July 23, 2007 8:31 PM