What range of RTP/SRTP ports does IBM Voice Agent use for inbound SIP / SIP+TLS?
Voice Gateway port documentation provides the default RTP port range (16384-16394) but I figure Voice Agent may have a wider/different range.
Why? The range is needed to configure our SBC for bridging calls to IBM Cloud.
The RTP port range used by IBM Voice Agent is 1024-65148.
Related
K8s wont allow external servers to push udp packages from arbitrary ports to pods.
RTSP protocol uses random udp ports to push data every frame.
RTSP-UDP initially connects to 554 TCP port, and gets assigned to a random UDP port between ~18000-25000 at every request.
Is there any way I can allowthis without using hostNetwork? Something like open a range of ports or, allow all UDP traffic from outside the cluster?
To recreate:
ffplay <rtsp-url>
And use a network tool like tcpdump, wireshark to probe udp packages.
You can expose plain TCP and UDP services using the standard nginx ingress controller - see the documentation.
Port ranges are not supported for services. Here is a related issue on github
https://github.com/kubernetes/kubernetes/issues/23864
IBM Voice Agent provides SIP domain names to configure Twilio etc.
sip:us-south.voiceagent.cloud.ibm.com (169.61.56.226)
sip:us-east.voiceagent.cloud.ibm.com (169.62.26.42)
Are these current IP addresses static?
The IPs are static but SIP trunks should be configured using the domain names. The IPs that the domains resolve to may change due to infrastructure changes or updates but the domains will always be consistent.
I need to write a client server code. the client can send\receive packets from multiple multicast addresses and also should check the validity of those IP\port range before sending\receiving packets.
so I looked on the RFC-5771 IANA Guidelines for IPv4 Multicast Address Assignments and found the range of multicast IP addresses.
where can I find the range of legal (not taken by other application) multicast ports?
thanks.
There are no ports specific to multicast. You can use any free UDP port available.
I was implementing a sip client for android and i installed Asterisk SIP server(installed in windows 2003 server).Testing with JITSI client.But problem is "able to communicate when both clients are in LAN" Where as if i try to call a client from out side the LAN or through wifi, I'm able get the call but not able to hear the voice on both sides.
-I have enabled ports 5060 in fire walls too
port 5060 is for SIP Messages communication only. The media (audio) is going through RTP packets, which go through their own ports.
Check out in your asterisk rtp.conf file the RTP port-range (if I am not mistaken the port-range is 10000-20000 by default).
You have to also open that port range in your firewall settings.
Update:
it will always work in the LAN, because that port range is enabled by default in Asterisk. It won't work if any of the devices is outside of the LAN (and the port range is not opened in the firewall), because the ports defined in the SDP bodies won't be accessible.
I´ve searched and didnt find which ports does XMPP uses.
I need to implement XMPP server and client and use XML transfer, file transfer and streaming.
Do they use different ports?? Is there a way I can make them use all the same, so I dont need to bother the network admin?
Thanks
According to Wikipedia:
5222 TCP XMPP client connection (RFC 6120) Official
5223 TCP XMPP client connection over SSL Unofficial
5269 TCP XMPP server connection (RFC 6120) Official
5298 TCP UDP XMPP JEP-0174: Link-Local Messaging / Official
XEP-0174: Serverless Messaging
8010 TCP XMPP File transfers Unofficial
The port numbers are defined in RFC 6120 § 14.7.
According to Extensible Messaging and Presence Protocol (Wikipedia), the standard TCP port for the server is 5222.
The client would presumably use the same ports as the messaging protocol, but can also use http (port 80) and https (port 443) for message delivery. These have the advantage of working for users behind firewalls, so your network admin should not need to get involved.
The ports required will be different for your XMPP Server and any XMPP Clients. Most "modern" XMPP Servers follow the defined IANA Ports for Server-to-Server 5269 and for Client-to-Server 5222. Any additional ports depends on what features you enable on the Server, i.e. if you offer BOSH then you may need to open port 80.
File Transfer is highly dependent on both the Clients you use and the Server as to what port it will use, but most of them also negotiate the connect via your existing XMPP Client-to-Server link so the required port opening will be client side (or proxied via port 80.)
The official ports (TCP:5222 and TCP:5269) are listed in RFC 6120. Contrary to the claims of a previous answer, XEP-0174 does not specify a port. Thus TCP:5298 might be customary for Link-Local XMPP, but is not official.
You can use other ports than the reserved ones, though: You can make your DNS SRV record point to any machine and port you like.
File transfers (XEP-0234) are these days handled using Jingle (XEP-0166). The same goes for RTP sessions (XEP-0167). They do not specify ports, though, since Jingle negotiates the creation of the data stream between the XMPP clients, but the actual data is then transferred by other means (e.g. RTP) through that stream (i.e. not usually through the XMPP server, even though in-band transfers are possible). Beware that Jingle is comprised of several XEPs, so make sure to have a look at the whole list of XMPP extensions.