Session Manger opening SIP connections with random (source ) port instead of 5060

[rejackson]

I have a link defined to an ESNA server. the entity link shows both ends should use port 5060. When SM opens a connection and sends an invite it sends it from a random high number port. The SIP application trace shows a timeout on the Invite but a wireshark packet trace shows the ESNA host acking the packet at the TCP level. I think the problem is that SM is not sending from port 5060. The Avaya application note said to use Other as the Entity type. Could that be causing this? The Ap notes is for SM 6.0 and I am on 6.2.

-------------------------------------------------------------------------------------------------------------------------------
CM-MM ESNA_ENT
SM100
-------------------------------------------------------------------------------------------------------------------------------
10:17:33.253 |--INVITE-->| | | (6) T:100080 F:101348 U:100080 P:terminating
10:17:33.254 |<--Trying--| | | (6) 100 Trying
10:17:33.256 | |--INVITE-->| | (6) T:100080 F:101348 U:100080 P:terminating
10:17:37.259 |<--Request-| | | (6) 408 Request Timeout
10:17:37.289 |----ACK--->| | | (6) sip:100080@ryanco.com

 

[kyle555]

No, that's the ephemeral port and perfectly OK.

server A sending to server B will be from source IPort to destination IPort. It's normal for your outgoing connections to be "not 5060" because that's the port your SM is listening on for incoming SIP.

 

[rejackson]

OK thanks. I think I got around that by rebooting the server to kill the existing connection. On to a new problem and new post.

 

[dialtonebone]

In most cases, if you have to reboot a server to fix a problem, you haven't fixed the problem.