IBM Support

PK79566: 480 TEMPORARILY UNAVAILABLE" RESPONSE IS NOT SENT UPSTREAM.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem is that a 480 Temporarily Unavailable response is
    not sent upstream by the Session Initiation Protocol (SIP)
    Container. The scenario is:
    UAC is calling an UAS through the SIP Proxy. SIP Proxy forwards
    the initial INVITE to the UAS. UAS responds with a 100 Trying
    response, then with a 180 Ringing response. After that UAS
    rejects the call with a 480 response. SIP proxy does not send
    this response to the UAC. The log file shows the following:
    ******************
    12/21/08 10:03:34:404 IST] 0000003d ProxyImpl     3 ProxyImpl
    sendResponseUpstream Temporarily Unavailable 480
    ,call-id=1-26016@9.148.45.153
    [12/21/08 10:03:34:404 IST] 0000003d ProxyImpl     3 ProxyImpl
    sendResponseUpstream Response NOT sent upstream, transaction
    already
    commited. SIP/2.0 480 Temporarily Unavailable
    Content-Length: 0
    ********************
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Application Server   *
    *                  V6.1                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The problem is that a 480 Temporarily   *
    *                      Unavailable response is not sent when   *
    *                      expected                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ProxyTo scenario does not send a 480 Session Initiation
    Protocol (SIP) error response
    

Problem conclusion

  • A specific SIP object was invalidated prematurely. This issue
    was fixed and now the SIP container is postponing it to a later
    phase.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.23  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK79566

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-28

  • Closed date

    2009-02-26

  • Last modified date

    2009-02-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021