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.

Knowledge Base

Sip trunks create signalling with port 5061

Publication Date:  2019-07-09  |   Views:  3840  |   Downloads:  0  |   Author:  Mauro80021720  |   Document ID:  EKB1000034707


Issue Description

The scenario consists on a NGN Softswitch, Asterisk server and a SIP trunk between them. The SIP trunk have no problems, but from MSoftx3000 the SIP packets are being sent from port 5061, despite that the configuration was specified to use port 5060.

SIPTG ip pair information
              IFM Module  =  132
       Local server port  =  5060
              Remote URI  =
       Master/Slave type  =  Master
       Second Remote URI  =
Second Master/Slave type  =  Slave
              Techprefix  =  NULL
      IsDeleteTechprefix  =  True
           Protocol Type  =  UDP
        PBX Equipment ID  =  NULL
         PBX Domain Name  =  NULL

Alarm Information


Handling Process

We have asked customer to share the packet capture information, and the MSoftX3000 version. 

Root Cause



We have informed customer that this behavior is normal, because when softx3000 is client, the peer side is server , the softx3000 will use the local port, this means , softx3000 will send the message with the MSGI port

If the softx3000 is the server, the peer side send the message to the port we will use. In the message, the peer side send the message to 5060

We will reply with 5060.