SIP Proxy and IM (MSN, AIM, iChat etc)
Status: Beta
Brought to you by:
tries
Menu
▾
▴
Is it possible to use SIP Proxy with IM clients/services that use SIP for initiating audio/video conversations (RTP) but use proprietary protocols for login, presence, text chat etc? Some examples of such clients/services are MSN, AIM, iChat.
Thanks,
Mikael
It SHOULD be possible to proxy the SIP and RTP part. However, the proprietary protocols can not be handled by siproxd - there another solution must be found.
The client *must* provide a way to configure an SIP outbound proxy. Any other aids to traverse a firewall must be disabled (like STUN for example).
/Thomas
Many thanks Thomas! Yes, Im thinking of proxying only the SIP/SDP/RTP part. Proprietary protocols are as they are proprietary :-( By careful configuration of a flexible firewall it is possible to get them through even in the NAT case. In some cases one has to make few non-general assumptions but it works. This is also possible with SIP/SDP/RTP part but only for one and only client on the internal net. This is where SIP proxy comes in. To be able to share one external IP, to use NAT, and to have more than one IM client machine on the local net. Would you say that siproxd is the right tool?
Im not sure that I understand what you mean by The client *must* provide a way to configure an SIP outbound proxy.
/Mikael
I mean: The SIP client must have the possibility to configure an SIP outbound proxy (somewhere in the configuration dialog). This outbound proxy must be the host running siproxd.
/Thomas
Now I see what you mean. Some of those clients allow you to configure a proxy but then everything will be sent to that proxy. We would like only SIP and RTP to go to SIP proxy, proprietary protocols should go directly.. Im not sure whether you can ask those client to do so. Some of the clients and/or proprietary protocols are friendly in that they always use standard SIP port 5060. Thats a hook to hold on. Some others use the proprietary part to send their SIP port number to the peer. Thats tough one. If we can not tell IM client to send SIP and RTP to SIP proxy then it looks like we need a special router sitting between IM clients and SIP proxy or maybe having SIP Proxy running on that special router and cooperating with routers forward/mangle/NAT functions it sounds like netfilter/iptables plus a special module to me. In the tough case we probably have to parse the proprietary protocols at least partially and have to do it before forwarding/mangling/NAT. Hmmm
/Mikael