Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
795
Views
0
Helpful
1
Replies

CUPC7 SIP and STUN SRV DNS Queries

Jonathan Schulenberg
Hall of Fame
Hall of Fame

‎09-26-2010 08:31 AM - edited ‎03-19-2019 01:39 AM

If I perform a packet capture of a CUPC 7 login I see that the client performs SRV DNS queries for:

  • _sip._tcp.cups-servername.proxydomain.local.
  • _sip._udp.cups-servername.proxydomain.local.
  • _stun._udp.proxydomain.local.

I have two questions that arrise from this observation:

  1. Why would the client perform a SIP SRV query against the servername instead of the SIP proxy domain? Unless I am missing something, querying the proxy domain would make a lot more sense.
    Note that this behavior does not change regardless of the SIP Proxy service parameters SRV Cluster Name or Address Resolution Type being changed from their default values of null and IP respectively.
  2. Does CUPS run a STUN server service and if so on what port; or, is the customer environment expected to provide its own STUN server if needed?
Labels:
0 Helpful
1 Reply 1

htluo
Level 9
Level 9

‎10-04-2010 12:21 PM

1. This is by designed (of CUPC).  I agree with you that it makes more sense to use proxy domain instead of FQDN.

2. If I remember it right, CUPS does not host a STUN server.  Default port for STUN was UDP port 3478.

Michael

http://htluo.blogspot.com

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents