SIP can't register over WSAM

[Jonas_]

Hello all.

I'm trying to get Tandberg MOVI (a SIP based videoconference app) to run over my SA4000.

It works fine over NC, but I want a one click-ish solution for guest users calling in from the internet.

MOVI is hosted on an embedded webserver running java and a small activeX app that is automatically downloaded to the client. Just using the rewriter rules I am able to start the web app on a guest PC however it won't launch the activeX properly.

With WSAM capturing and redirecting the initial SIP connection it goes a little further, then stops and complains that it cant complete registration on our main SIP server. My guess is that the return traffic needs to be directed to the SA4000, but I'm not sure.

Presumably this problem would be similar for any SIP client that wants to register to an internal service.

Is there anyone out there who has got this working without resorting to the full Network Connect?

Cheers!

Jonas Eriksson

[-red-_]

I'm afraid you may have to stick with NC. I would be willing to bet if you review your firewall logs, you will see traffic from your video conference server attempting to hit the SA, though they are actually intended to reach the worksation which has initiated the original connection.

I've experemented with several flavors of video conference solutions, all resulting in the same outcome; Network Connect.

If someone managed to make it work via SAM, I'd love to hear details.

[zanyterp_]

The SIP protocol for registration, I believe, also involves a server-initiated connection. This type of connection is Network Connect-only.

[Jonas_]

Sadly this seems to be true, SIP is one crap protocol suite considering it was so recently developed...

Considering the versatility of JSAM: May I suggest that a future version that can handle dynamic port forwarding on the IVE (a feature prevalent in many medium budget nat routers). This would enable clientless access for any number of sticky client applications.