[Serusers] Re:Serusers Digest, Vol 17, Issue 7

[??]

Yes, we've succefully installede ser 0.8.14 and the newest version of serweb on redhat9.


-----  Original Message  -----
From: serusers-request at lists.iptel.org 
To: serusers at lists.iptel.org 
Subject: Serusers Digest, Vol 17, Issue 7
Sent: Mon Sep 06 18:00:24 CST 2004

> 
> Send Serusers mailing list submissions to
> 	serusers at lists.iptel.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.iptel.org/mailman/listinfo/serusers
> or, via email, send a message with subject or body 'help' to
> 	serusers-request at lists.iptel.org
> 
> You can reach the person managing the list at
> 	serusers-owner at lists.iptel.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Serusers digest..."
> 
> 
> Today's Topics:
> 
>    1. Finding offline users. (serusers at jtoga.org)
>    2. NAT and protocol aware firewalls (Helge Waastad)
>    3. 0.8.14 on Redhat Linux 9.0 (Rose, John)
>    4. Sip to Pstn Problem (Vishal Pandhre)
>    5. ERROR on Request line ACKNOWLEDGE (Nicolas RUIZ)
>    6. how to forward without VIA (hong cheng)
>    7. (no subject) (HUIMING YU)
>    8. Re: [Serdev] ser's birthday (Adrian Georgescu)
>    9. Finding offline users. (Juha Heinanen)
>   10. Ser problem about too much share memory demanded
>       (=?GB2312?B?xaPApA==?=)
>   11. Re: NAT and protocol aware firewalls (Jesus Rodriguez)
>   12. Re: ser's birthday (Mike Tkachuk)
>   13. Re: how to forward without VIA (Jan Janak)
>   14. Re: (no subject) (Jan Janak)
>   15. Re: Ser problem about too much share memory demanded (Jan Janak)
>   16. Re: NAT and protocol aware firewalls (Jan Janak)
>   17. Re: Domain suffix bug in ser enum module? (Jan Janak)
>   18. Re: receive_msg: no mem for sip_msg (Jan Janak)
>   19. RE: sems+ser+ivr (ser die)
>   20. wm 4.7 / subscribe error message 500 (Graham Turner)
>   21. ser-mysql (kcassidy at kakelma.mine.nu)
>   22. ser-mysql (kcassidy at kakelma.mine.nu)
>   23. SIP & PSTN via MD Evolution PBX (g.billoudet at arwen-tech.fr)
>   24. Postgres support in 0.8.14  ? (Johan Landerholm)
>   25. Re: ser-mysql (Daniel-Constantin Mierla)
>   26. Re: 0.8.14 on Redhat Linux 9.0 (Daniel-Constantin Mierla)
>   27. Re: how to forward without VIA (Daniel-Constantin Mierla)
>   28. Re: ser-mysql (kcassidy at kakelma.mine.nu)
>   29. Re: error starting ser 0.8.14 - failure to connect to DB
>       (Daniel-Constantin Mierla)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 01 Sep 2004 14:44:17 -0400
> From: serusers at jtoga.org
> Subject: [Serusers] Finding offline users.
> To: serusers at lists.iptel.org
> Message-ID: <5.1.0.14.2.20040901143819.033484a8 at jetx.jtoga.org>
> Content-Type: text/plain; charset="us-ascii"; format=flowed
> 
> Hi,
> 
> I'm trying to have a caller (eg sender of invite) be able to detect the 
> difference between a user that is 'offline' and one that really doesn't 
> exist.   Current cfg methods allow for doing a lookup in the location 
> table, but if the target isn't there - then a 404 is returned.
> 
> I think what I would like to do is then check the subscriber table....what 
> is the best way to accomplish this?
> 
> (trying a 'lookup' on the subscriber table didn't work....)
> 
> Thanks in advance.
> Jim.
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 1 Sep 2004 22:06:10 +0200
> From: "Helge Waastad" <Helge.Waastad at smartnet.no>
> Subject: [Serusers] NAT and protocol aware firewalls
> To: <serusers at lists.iptel.org>
> Message-ID: <27DFDD544A6F0D4E897A054667CCADC028021C at mail.smartnet.no>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi,
> 
> I just want to dwell around a couple of things.
> 
> Several vendors have "application awareness" for instance Cisco has
> <fixup protocol sip...>
> 
> Hence the ser will not se the client as nat'ed and will not send
> nat-ping to the clients.
> 
>  
> 
> If the client does not support some kind of keep-alives, I guess you
> will loose connectivity with the clients when standard register expiry
......