[Serusers] ser+nat+siproxd+asterisk

[Greger V. Teigre]

>Thanks for the active replies =) ... I guess we can use a combination of the various nat solutions we have to suite as the need be. Lets say, >SER has nathelper and mediaproxy for nated clients, but when UA is from a NAT with Siproxd, SER does not need to use mediaproxy .
>
If siproxd adds itself as user agent in REGISTER, this will be easy to detect.

>As for how many simultaneous calls it can support there seems to be no data for that yet even on their official website. Maybe the >community there could schedule some tests later.

;-)

g-)
  On 9/2/05, Greger V. Teigre <greger at teigre.com> wrote:
    IMHO, siproxd is not suited for a far-end NAT traversal scenario and certainly not capable of scaling if you have a large user community. It is suitable (and made) as a way to simplify traversal through firewalls in the corporate network and can be used standalone to handle mydomain.com calls (company internal and email-based calls).  
    With ser, I assume it can be used to move the NAT issue from centrally managed closer to the user community.  It may make sense to in some scenarios if the corporation is not ready to upgrade the FW to one with SIP ALG or upon up lots of ports.  
    Summary:
    - If you are on the inside of the FW (i.e. you are the corporation), siproxd should do fine
    - If you provide services to the corporation and the ser is on the outside, it should be installed on a case by case basis (some FWs have SIP ALG already)
    - If you provide single user services and they happen to be behind corporate FWs, forget about siproxd

    g-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050902/7465e25e/attachment.htm>