No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


In the SE2900 I-SBC Scenario, the SBC IP Tracing Result Shows That Messages Sent by the Peer End Are Not Traced

Publication Date:  2019-04-12 Views:  369 Downloads:  0

Issue Description

In the SE1000 I-SBC scenario, the SBC IP tracing result shows that messages sent by the peer end are not traced.

No message can be traced in the SIP tracing task.

Alarm Information


Handling Process

Check the IP addresses and port numbers of the local and peer ends configured on the I-SBC.



According to the check, the local and peer IP addresses in the messages are correct. However, the local ( port of the peer trunk is 5060, which is 7764 instead in IP message tracing. As a result, the trunk matching fails and the SIP messages are not processed.

Root Cause

The local port of the peer trunk is 7764, which is inconsistent with the port 5060 configured on the SBC. As a result, the SBC and trunk fail to match and the SIP messages are not processed.


Change the peer trunk's local port number used to send messages, so that it is consistent with the port number 5060 configured on the SBC. The problem is then solved.


In the I-SBC scenario, make sure that the 5-tuple of "local IP address + local port number + transmission protocol + peer IP address + peer port number" is correct. Ensure that the local IP address + port number and destination IP address + port number are consistent with those configured on the SBC.