< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [repro-users] repro - Recommendations for Production deployment


On Wed, Apr 6, 2016 at 6:03 PM, Julio Cabezas <jcabezas@xxxxxxxxxxxxx> wrote:

    Let me report an observation I made today with repro.  I hope that can be helpful.

    I have an instance of repro  V.1.9.8 running on Windows Server 2008R2, with an uptime of at some 3 months working normally.
    It showed the following today:
    Some 10 User Agents were on and should be registered with repro, but only 4 of those showed up normally in repro Registrations page.

    Wireshark showed that for the non-registered UAs:
    - REGISTER (over TCP) was sent by the UAs and arrived normally at repro interface and port
    - But there were only  TCP ACK replies to those REGISTERs and no SIP responses.

    After restarting repro, all UAs registered normally.

    Is that an already known behaviour ?  Maybe version 1.10.1 solved it ?

[Scott] I believe you are likely hitting the TCP connection limit and that 1.10.1 will solve it.

   By the way, what are the differences expected between restarting the “repro.exe” process and using “Restart Proxy” button in Settings page ?
   When use either one ?

[Scott]  The restart proxy button on the Setting page will leave the in memory copy of the current registrations in-tact.  If you restart the process then all endpoints must re-register before the proxy will know where they are again.
Best Regards.

From: slgodin@xxxxxxxxx [mailto:slgodin@xxxxxxxxx] On Behalf Of Scott Godin
Sent: Wednesday, February 24, 2016 1:51 PM
To: Julio Cabezas
Cc: repro-users
Subject: Re: [repro-users] repro - Recommendations for Production deployment

Hi Julio,

If you are using TCP clients, then 1.9 and earlier versions had issues with supporting more than 60 or so TCP clients on windows.  I am using repro 1.10 on Windows systems with out stability issues.  I'm not sure switching to linux will provide any benefit now that repro is able to use the WSAPoll mechanism for large scale TCP server support.  I would always recommend using the latest version.


On Thu, Feb 18, 2016 at 3:21 PM, Julio Cesar Esteves Cabezas <jcabezas@xxxxxxxxxxxxx<mailto:jcabezas@xxxxxxxxxxxxx>> wrote:

    I have been using repro version 1.9.8, running on Windows Server 2008R2 for some time in a number of test or less-demanding production environments.

    People report me once in a while of some “glitches” in repro operation, that they claim got instantly solved by restarting repro. I could not check them in detail.
    One such report was that repro ceased to react to incoming SIP messages.

    Now I intend to put repro in a more demanding production environment. I have a few questions:
    - Instead of version 1.9.8 already a bit old,  which one more recent version is deemed more stable ?  1.10.0 ?  1.10.1 ?
    - Instead of running on Windows Server 2008R2, is Linux version more advisable for being more reliable or at least more thoroughly deployed/tested/debugged ?
    - Then which Linux distribution(s) / version(s) would be recommended ?

    I appreciate any hints/pointers on improving repro deployment stability and its continuous monitoring / troubleshooting.

Best Regards,

repro-users mailing list

repro-users mailing list