Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-30-2014, 03:25 AM
rime rime is offline
Brainiac
 
Join Date: Dec 2011
Posts: 56
rime has 10 reputation points
Default Source Port/Destination Port for SIP messages

When tracing on a Session Manager (putty as "cust" to the security module IP address, then run traceSM, filter on the IP address of the peer with "-i <ip address>"), I see that the Session Manager sends messages with ports widely different from the configured 5061 for that particular signaling connection. Is it predictable which ports will be used? Can't they be nailed down to 5061 or other configured values? I ask because priority on the router is based on IP addresses, protocols and also source and destination ports. Here an interpreted trace extract where the issue is visible:

SESSION MGR............................ PEER
-----------............................-----
Source port: .....0 ....-----INVITE---> Destination Port: 5061
Destination port: 45561 <--- TRYING --- Source Port: .....5061
Destination port: 45561 <--- RINGING -- Source Port: .....5061
Source port: .....0 ....-----PRACK----> Destination Port: 5061
Destination port: 45561 <--- OK ------- Source Port: .....5061

Last edited by rime; 04-30-2014 at 03:31 AM.
Reply With Quote
  #2  
Old 05-02-2014, 11:37 AM
ilalpatidar ilalpatidar is offline
Whiz
.
 
Join Date: Jan 2014
Posts: 37
ilalpatidar has 11 reputation points
Default

The ports shown in the trace seems to be from the originating device and I think they cant be controlled as these will be random UDP port from the range defined on the communication controller. (For example H.323 Avaya phones ports are controlled through the ip- network region form)

I hope this helps.
Reply With Quote
  #3  
Old 05-05-2014, 04:13 AM
rime rime is offline
Brainiac
 
Join Date: Dec 2011
Posts: 56
rime has 10 reputation points
Default Source Port/Destination Port for SIP messages

In the trace shown, both endpoints are Session Manager systems, of different enterprises, interconnected by a SIP trunk. So it is the Session Managers which decide to use port 0 to initiate a dialogue, respectively 45561 (or other) to reply to it. The SIP entity links explicitly list TLS port 5061 for both ends of the links, on both Session Managers of both enterprises. But in reality, we see different ports in protocol traces. Building a reliable ACL is the challenge that results.
Reply With Quote
Reply

Tags
destination port, sip trace, source port, tracesm

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 12:58 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.