Jabber/Movi clients being relayed (without STUN/TURN)
Thanks ahead of time for any help on this.
I was doing a wireshark capture of both the free version of Jabber and the Enterprise version and came across a media routing issue that's rather perplexing.
The client (Movi/Jabber) was on a NAT'd guest network. The destination is an 8510 MCU.
When I fired up the Enterprise version of Jabber on the NAT'd network and proceeded to make a call, I noticed all of my UDP media flows had a destination that was MY expressway (on a different network where the Jabber client was NAT'd, but still local to me and not out on the internet).
When I fired up the free version nof Jabber and proceeded to make a call to the same destination, the media flow UDP was going directly to the 8510 IP address.
I don't have STUN or TURN enabled on my expressway. The call history on our expressway says the call was a SIP call (so it wasn't doing an H.323 to SIP interwork call).
Why would my Enterprise client's UDP media go to our expressway first, but the free version's media route goes directly to the destination?
Re: Jabber/Movi clients being relayed (without STUN/TURN)
So you are saying that by enabling ICE/STUN a direct connection between endpoints outside of my expressway is possible, but without ICE/STUN turned on with my clients they will route through my expressway if they are NAT'd regardless of where they are?
I have some additional data as well. I did repeated tests with wireshark using the free Jabber client/service that CISCO offers. Interestingly enough, the direct connection between the NAT'd free client and our hosted 8510 only happened once, subsequent connects went through CISCO's expressway (or whatever they are using for a SIP registrar/ICE/STUN server. I'm wondering how ICE/STUN decides if it needs to use TURN on the expressway because it's obvious that some sort of detection process makes the decision. The head scratcher is that in at least ONE instance during my tests using the free client it routed directly to the externally hosted MCU (which is ideal).
The goal is of course to avoid having external Jabber/Movi clients route media through our expressway on their way to our hosted MCU.
Currently, the hosted MCU is not registered to our expressway. It has a public IP though.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.