| Asset ID: |
1-71-2148749.1 |
| Update Date: | 2017-01-04 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2148749.1
:
Why Is SIP-T Response 487 "Request Terminated" Not Correlated?
| Related Items |
- Oracle Communications Performance Intelligence Center (PIC) Software
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
|
In this Document
Created from <SR 3-12831979251>
Applies to:
Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.4 and later
Information in this document applies to any platform.
Goal
Why are SIP-T 487 "Request Terminated" failure response and related confirmation not correlated to the xDR exisiting for the entire transaction?
Solution
Normally SIP-T builder will close xDR following receipt of RLC (Bye). However in some of the network implementations it is possible that SIP response 487 "Request Terminated" is sent after RLC (mostly within 3 seconds from RLC, but can be later). In order to address this behavior, there is a way to customize SIP-T builder so that it will wait for a configured time for new PDUs with same Call-ID even after the receipt of RLC. This can be enabled by setting value other than 0 (seconds) for "Transaction maximum release timer" in SIP-T Reconsitution builder.
Attachments
This solution has no attachment
