<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Daniel,
<p>I changed the timeouts as per your suggestion. When I send the message
from JAM -> WM I still get no messages (the ngrep output is below). First
off, there is obviously a duplicate message being send there. Then, the
400 comes back from WM client. What gives?
<p> Igor
<p><tt>U 144.14.255.145:5060 -> 144.14.62.75:12157</tt>
<br><tt> MESSAGE sip:144.14.62.75:12157 SIP/2.0..Record-Route: <sip:igorb@144.14.255.145;ftag=a5a3ce0e783e6e6de506638e4c2bc736-20</tt>
<br><tt> 4a;lr>..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK8dcb.214ce0e2.0..Via:
SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK7e1</tt>
<br><tt> 7.0bd7c7b5.0..To: sip:igorb@piias12.ms.com..From: <sip:igorb*jamny1@sait661>;tag=a5a3ce0e783e6e6de506638e4c2bc736-204a..</tt>
<br><tt> CSeq: 10 MESSAGE..Call-ID: 5fbc9eb5-11089@144.14.255.145..Content-Length:
3..User-Agent: Sip EXpress router(0.8.12dev-t1</tt>
<br><tt> 1 (i386/linux))..Content-Type: text/plain..Contact: <sip:igorb*jamny1@sait661>....zxc</tt>
<br><tt>#</tt>
<br><tt>U 144.14.255.145:5060 -> 144.14.62.75:12157</tt>
<br><tt> MESSAGE sip:144.14.62.75:12157 SIP/2.0..Record-Route: <sip:igorb@144.14.255.145;ftag=a5a3ce0e783e6e6de506638e4c2bc736-20</tt>
<br><tt> 4a;lr>..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK8dcb.214ce0e2.0..Via:
SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK7e1</tt>
<br><tt> 7.0bd7c7b5.0..To: sip:igorb@piias12.ms.com..From: <sip:igorb*jamny1@sait661>;tag=a5a3ce0e783e6e6de506638e4c2bc736-204a..</tt>
<br><tt> CSeq: 10 MESSAGE..Call-ID: 5fbc9eb5-11089@144.14.255.145..Content-Length:
3..User-Agent: Sip EXpress router(0.8.12dev-t1</tt>
<br><tt> 1 (i386/linux))..Content-Type: text/plain..Contact: <sip:igorb*jamny1@sait661>....zxc</tt>
<br><tt>#</tt>
<br><tt>U 144.14.62.75:1555 -> 144.14.255.145:5060</tt>
<br><tt> SIP/2.0 400 Bad Request..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK8dcb.214ce0e2.0..Via:
SIP/2.0/UDP 144.14.255.145;</tt>
<br><tt> branch=z9hG4bK7e17.0bd7c7b5.0..From: <sip:igorb*jamny1@sait661>;tag=a5a3ce0e783e6e6de506638e4c2bc736-204a..To:
sip:igorb</tt>
<br><tt> @piias12.ms.com;tag=6810f81b-2264-4a2a-8c11-f4002710fb62..Call-ID:
5fbc9eb5-11089@144.14.255.145..CSeq: 10 MESSAGE..User</tt>
<br><tt> -Agent: Windows RTC/1.0..Content-Length: 0....</tt>
<br><tt></tt>
<p>Daniel-Constantin Mierla wrote:
<blockquote TYPE=CITE>When that value is 1 the Jabber connection is going
to be closed, it has
<br>expired. The cache_time specifies the time to keep a jabber connection
<br>open if there is no traffic through it, when that time expires the
<br>connection is closed. Otherwise, if a message is not successfully
<br>delivered to SIP user then the jabber connection is closed, too. Watch
<br>your network traffic (using ngrep, tcpdump or ethereal) to see if any
<br>SIP request from Jabber gateway is launched on wire and whether it
gets
<br>a non 2xx reply code or not.
<p>Best regards,
<br>Daniel
<p>Igor Boguslavsky wrote:
<p>> I think I have just created that version myself :) This is what I
get
<br>> with more debug on (note the cbp value: xj_send_sip_msg() craps out
<br>> since it's non-zero - is that the way it should be?)
<br>>
<br>> 0(10655) XJAB:xj_worker:10668: something is coming
<br>> 0(10655) XJAB:xj_worker:10668: checking socket <8> ...
<br>> 0(10655) XJAB:xj_worker:10668: received: 121bytes Err:0/EA:11
<br>> 0(10655) XJAB: xj_jcon_update [sip:igorb@piias12.ms.com] 200
<br>> 0(10655) XJAB:xj_worker: JMSG START ----------
<br>> <message to='igorb@sait661/serXjab' from='igorb@jamny1/Office'
id='19'
<br>> type='chat'><body>;lkdfgdfgdfgdfg</body></message>
<br>> JABBER: JMSGL:121 END ----------
<br>> 0(10655) XJAB:xj_parse_jab: XODE ret:0 pos:121
<br>> 0(10655) XJAB:xj_manage_jab: jabber [message] received
<br>> 0(10655) XJAB:xj_address_translation:10668: - checking aliases
<br>> 0(10655) XJAB:xj_address_translation:10668: - domain is [jamny1/Office]
<br>> 0(10655) XJAB:xj_address_translation:10668: - doing address
correction
<br>> 0(10655) XJAB:xj_send_sip_msg: to = sip:igorb@piias12.ms.com
<br>> 0(10655) XJAB:xj_send_sip_msg: from = igorb*jamny1@sait661
<br>> 0(10655) XJAB:xj_send_sip_msg: msg = ;lkdfgdfgdfgdfg
<br>> 0(10655) XJAB:xj_send_sip_msg: cbp = 1
<br>> 0(10655) XJAB:xj_manage_jab: ERROR SIP MESSAGE was not sent
...
<br>> 0(10655) XJAB:xj_worker:10668: msgs from socket <8> parsed
...
<br>>
<br>> Thank you,
<br>> Igor
<br>>
<br>> Daniel-Constantin Mierla wrote:
<br>>
<br>>> Hello,
<br>>> it seems that one of the parameters for sending messages (i.e.,
from,
<br>>> to, body) is null or the connection to jabber is going to be closed.
The
<br>>> second seems more viable so please set cache_time parameter greater
than
<br>>> sleep_time (at least two times) and try again. If it does not work
I
<br>>> will send you a version of the module with more debug messages to
track
<br>>> what happens there.
<br>>>
<br>>> Thanks,
<br>>> Daniel
<br>>>
<br>>> Igor Boguslavsky wrote:
<br>>>
<br>>> > Daniel,
<br>>> >
<br>>> > Thanks a lot for getting back with me
on this - I did grab the
<br>>> > latest snapshot and it fixed the problem COMPLETELY! No more duplicate
<br>>> > processes, and the gateway actually works. Now, I've managed to
set
<br>>> > the config file up so I can see presence in both directions (from
<br>>> > WMessenger side, as well as Jabber) and I can send messages from
WM ->
<br>>> > Jabber just fine, but not in the opposite direction! I'm attaching
the
<br>>> > config below (as well as some errors I see in the logs while sending
<br>>> > messages). I would greatly appreciate your help with this.
<br>>> >
<br>>> > You guys are doing an amazing job,
<br>>> > Igor
<br>>> >
<br>>> >
<br>>> > error log while sending messages Jabber -> WM:
<br>>> >
<br>>> > 0(9428) XJAB:xj_worker:9441: something is coming
<br>>> > 0(9428) XJAB:xj_worker:9441: checking socket <8> ...
<br>>> > 0(9428) XJAB:xj_worker:9441: received: 174bytes Err:0/EA:11
<br>>> > 0(9428) XJAB: xj_jcon_update [sip:igorb@piias12.ms.com]
200
<br>>> > 0(9428) XJAB:xj_worker: JMSG START ----------
<br>>> > <message to='igorb@sait661/serXjab' from='igorb@jamny1/Office'
id='5'
<br>>> > type='chat'><body>%%composing reply</body><x
<br>>> > xmlns='jabber:x:event'><id>0</id><composing/></x></message>
<br>>> > JABBER: JMSGL:174 END ----------
<br>>> > 0(9428) XJAB:xj_parse_jab: XODE ret:0 pos:174
<br>>> > 0(9428) XJAB:xj_manage_jab: jabber [message] received
<br>>> > 0(9428) XJAB:xj_address_translation:9441: - checking aliases
<br>>> > 0(9428) XJAB:xj_address_translation:9441: - domain is [jamny1/Office]
<br>>> > 0(9428) XJAB:xj_address_translation:9441: - doing address
correction
<br>>> > 0(9428) XJAB:xj_manage_jab: ERROR SIP MESSAGE was not sent
...
<br>>> > 0(9428) XJAB:xj_worker:9441: msgs from socket <8> parsed
...
<br>>> >
<br>>> > 0(9428) XJAB:xj_worker:9441: something is coming
<br>>> > 0(9428) XJAB:xj_worker:9441: checking socket <8> ...
<br>>> > 0(9428) XJAB:xj_worker:9441: received: 107bytes Err:0/EA:11
<br>>> > 0(9428) XJAB: xj_jcon_update [sip:igorb@piias12.ms.com]
200
<br>>> > 0(9428) XJAB:xj_worker: JMSG START ----------
<br>>> > <message to='igorb@sait661/serXjab' from='igorb@jamny1/Office'
id='6'
<br>>> > type='chat'><body>df</body></message>
<br>>> > JABBER: JMSGL:107 END ----------
<br>>> > 0(9428) XJAB:xj_parse_jab: XODE ret:0 pos:107
<br>>> > 0(9428) XJAB:xj_manage_jab: jabber [message] received
<br>>> > 0(9428) XJAB:xj_address_translation:9441: - checking aliases
<br>>> > 0(9428) XJAB:xj_address_translation:9441: - domain is [jamny1/Office]
<br>>> > 0(9428) XJAB:xj_address_translation:9441: - doing address
correction
<br>>> > 0(9428) XJAB:xj_manage_jab: ERROR SIP MESSAGE was not sent
...
<br>>> > 0(9428) XJAB:xj_worker:9441: msgs from socket <8> parsed
...
<br>>> >
<br>>> >
<br>>> >
<br>>> >
<br>>> > Daniel-Constantin Mierla wrote:
<br>>> >
<br>>> >> Hello,
<br>>> >> do you still have the problem with the latest CVS?
<br>>> >>
<br>>> >> Best regards,
<br>>> >> Daniel
<br>>> >>
<br>>> >> Daniel-Constantin Mierla wrote:
<br>>> >>
<br>>> >> > Hello,
<br>>> >> > please take the last CVS version (stable branch) and try again.
<br>>> I am
<br>>> >> > traveling now, I will be back in office next week and I will
check
<br>>> >> > carefully your problem. We have been reported about this problem
<br>>> and
<br>>> >> > the CVS version should fix it. If not, please tell us.
<br>>> >> >
<br>>> >> > Best regards,
<br>>> >> > Daniel
<br>>> >> >
<br>>> >> >
<br>>> >> > Igor Boguslavsky wrote:
<br>>> >> >
<br>>> >> >> All,
<br>>> >> >>
<br>>> >> >> I've been playing with jabber module
and having problems
<br>>> someone
<br>>> >> >> had mentioned here earlier: first, the number of ser
processes
<br>>> >> >> increases constantly . This is due to the fact that XJAB
<br>>> threads seem
<br>>> >> >> to be dying (or so waitpid() code thinks in jabber.c), and
keeps
<br>>> >> >> spawning more threads. The proble is that ser threads are
still
<br>>> >> >> around when that happens, contributing to a number of processes.
<br>>> >> >>
<br>>> >> >> Second, and most troubling, is that
jabber module doesn't even
<br>>> >> >> try to connect to jabber server (conformed by running ngrep
and
<br>>> >> >> tcpdump on a jabber box, which runs on a separate box). This
<br>>> may or
<br>>> >> >> may not be due to the error described above (any chance that
<br>>> jabber
<br>>> >> >> threads that are supposed to connect are not around anymore?).
<br>>> I even
<br>>> >> >> tried disabling TCP and recompiling (commented -DUSE_TCP in
<br>>> >> >> Makefile.def)
<br>>> >> >>
<br>>> >> >> The rest of ser functionality is fine.
I can log in tp the
<br>>> server
<br>>> >> >> easily, mysql gets updated acorrdingly, etc.
<br>>> >> >>
<br>>> >> >> The setup: ser-0.8.11pre29 on Linux
2.4.9 (host name piias12),
<br>>> >> >> compiled with gcc 3.2.2. Jabber runs on a server "sait661".
<br>>> >> >>
<br>>> >> >> The jusers looks like this:
<br>>> >> >>
<br>>> >> >> mysql> select * from jusers;
<br>>> >> >> +------+--------+------------+----------------------+------+
<br>>> >> >> | juid | jab_id | jab_passwd | sip_id
| type |
<br>>> >> >> +------+--------+------------+----------------------+------+
<br>>> >> >> | 1 | igorb | ***
| igorb@piias12.ms.com | 0 |
<br>>> >> >> +------+--------+------------+----------------------+------+
<br>>> >> >> 1 row in set (0.00 sec)
<br>>> >> >>
<br>>> >> >>
<br>>> >> >> =================== ser.conf: (Experimental; just to illustrate
<br>>> >> >> Jabber login)
<br>>> ======================================================
<br>>> >> >> #
<br>>> >> >> # $Id: ser.cfg,v 1.20 2003/05/31 21:12:19 jiri Exp $
<br>>> >> >> #
<br>>> >> >> # simple quick-start config script
<br>>> >> >> #
<br>>> >> >>
<br>>> >> >> # ----------- global configuration parameters
<br>>> >> ------------------------
<br>>> >> >>
<br>>> >> >>
<br>>> >> >> debug=3 #
debug level (cmd line: -dddddddddd)
<br>>> >> >> fork=yes
<br>>> >> >> log_stderror=no # (cmd line: -E)
<br>>> >> >>
<br>>> >> >> # Uncomment these lines to enter debugging mode
<br>>> >> >> /*
<br>>> >> >> debug=7
<br>>> >> >> fork=no
<br>>> >> >> log_stderror=yes
<br>>> >> >> */
<br>>> >> >>
<br>>> >> >> check_via=no # (cmd. line: -v)
<br>>> >> >> dns=no
# (cmd. line: -r)
<br>>> >> >> rev_dns=no # (cmd. line: -R)
<br>>> >> >> port=5060
<br>>> >> >> children=4
<br>>> >> >> fifo="/tmp/ser_fifo"
<br>>> >> >>
<br>>> >> >> # ------------------ module loading
<br>>> >> ----------------------------------
<br>>> >> >>
<br>>> >> >> # Uncomment this if you want to use SQL database
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/mysql.so"
<br>>> >> >>
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/sl.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/tm.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/rr.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/maxfwd.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/usrloc.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/registrar.so"
<br>>> >> >>
<br>>> >> >> # Uncomment this if you want digest authentication
<br>>> >> >> # mysql.so must be loaded !
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/auth.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/auth_db.so"
<br>>> >> >>
<br>>> >> >> ######## JABBER <-> SIMPLE
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/print.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/textops.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/jabber.so"
<br>>> >> >> loadmodule "/var/ser/lib/ser/modules/pa.so"
<br>>> >> >>
<br>>> >> >> modparam("jabber","db_url","sql://ser:heslo@127.0.0.1/sip_jab")
<br>>> >> >> modparam("jabber","jaddress","sait661.ms.com")
<br>>> >> >> modparam("jabber","jport",5222)
<br>>> >> >> modparam("jabber","workers",2)
<br>>> >> >> modparam("jabber","max_jobs",2)
<br>>> >> >> modparam("jabber","aliases","1;yahoo.sait661;")
<br>>> >> >> modparam("jabber","jdomain","sait661")
<br>>> >> >> modparam("jabber","delay_time",5)
<br>>> >> >> modparam("jabber","cache_time",200)
<br>>> >> >> modparam("jabber","sleep_time",60)
<br>>> >> >> modparam("jabber","check_time",60)
<br>>> >> >> ################
<br>>> >> >> # ----------------- setting module-specific parameters
<br>>> >> ---------------
<br>>> >> >>
<br>>> >> >> # -- usrloc params --
<br>>> >> >>
<br>>> >> >> # modparam("usrloc", "db_mode", 0)
<br>>> >> >>
<br>>> >> >> # Uncomment this if you want to use SQL database
<br>>> >> >> # for persistent storage and comment the previous line
<br>>> >> >> modparam("usrloc", "db_mode", 2)
<br>>> >> >>
<br>>> >> >> # -- auth params --
<br>>> >> >> # Uncomment if you are using auth module
<br>>> >> >> #
<br>>> >> >> modparam("auth_db", "calculate_ha1", yes)
<br>>> >> >> #
<br>>> >> >> # If you set "calculate_ha1" parameter to yes (which true
in this
<br>>> >> >> config),
<br>>> >> >> # uncomment also the following parameter)
<br>>> >> >> #
<br>>> >> >> modparam("auth_db", "password_column", "password")
<br>>> >> >>
<br>>> >> >> # ------------------------- request routing logic
<br>>> >> -------------------
<br>>> >> >> alias="ms.com"
<br>>> >> >> alias="piias12.ms.com"
<br>>> >> >>
<br>>> >> >> # main routing logic
<br>>> >> >>
<br>>> >> >> route{
<br>>> >> >>
<br>>> >> >> # initial
sanity checks -- messages with
<br>>> >> >> # max_forwards==0,
or excessively long requests
<br>>> >> >> if (!mf_process_maxfwd_header("10"))
{
<br>>> >> >>
sl_send_reply("483","Too Many Hops");
<br>>> >> >>
break;
<br>>> >> >> };
<br>>> >> >> if (len_gt(
max_len )) {
<br>>> >> >>
sl_send_reply("513", "Message too big");
<br>>> >> >>
break;
<br>>> >> >> };
<br>>> >> >>
<br>>> >> >> # we record-route
all messages -- to make sure that
<br>>> >> >> # subsequent
messages will go through our proxy; that's
<br>>> >> >> # particularly
good if upstream and downstream entities
<br>>> >> >> # use different
transport protocol
<br>>> >> >> record_route();
<br>>> >> >> # loose-route
processing
<br>>> >> >> if (loose_route())
{
<br>>> >> >>
t_relay();
<br>>> >> >>
break;
<br>>> >> >> };
<br>>> >> >>
<br>>> >> >> # if the request
is for other domain use UsrLoc
<br>>> >> >> # (in case,
it does not work, use the following command
<br>>> >> >> # with proper
names and addresses in it)
<br>>> >> >> if (uri==myself)
{
<br>>> >> >>
<br>>> >> >>
if (method=="REGISTER") {
<br>>> >> >>
<br>>> >> >>
if (!www_authorize("piias12.ms.com",
<br>>> >> "subscriber")) {
<br>>> >> >>
www_challenge("piias12.ms.com", "0");
<br>>> >> >>
break;
<br>>> >> >>
};
<br>>> >> >>
<br>>> >> >>
save("location");
<br>>> >> >>
<br>>> >> >>
log (1, "Are we registering?");
<br>>> >> >>
if(search("egistration")) {
<br>>> >> >>
<br>>> >> >>
log (1, "XJAB: Going ONline in Jabber
<br>>> >> >> network!!!\n");
<br>>> >> >>
<br>>> >> >>
if (jab_go_online()) {
<br>>> >> >>
sl_send_reply("200", "Accepted");
<br>>> >> >>
}
<br>>> >> >>
else {
<br>>> >> >>
sl_send_reply("404","Not found");
<br>>> >> >>
};
<br>>> >> >>
};
<br>>> >> >>
<br>>> >> >>
break;
<br>>> >> >>
};
<br>>> >> >>
<br>>> >> >>
<br>>> >> >>
# native SIP destinations are handled using our
<br>>> >> >> USRLOC DB
<br>>> >> >>
if (!lookup("location")) {
<br>>> >> >>
sl_send_reply("404", "Not Found");
<br>>> >> >>
break;
<br>>> >> >>
};
<br>>> >> >> };
<br>>> >> >> # forward
to current uri now; use stateful forwarding;
<br>>> that
<br>>> >> >> # works reliably
even if we forward from TCP to UDP
<br>>> >> >> if (!t_relay())
{
<br>>> >> >>
sl_reply_error();
<br>>> >> >> };
<br>>> >> >>
<br>>> >> >> }
<br>>> >> >>
<br>>> >> >> ========== Relevant portions of daemon.log
<br>>> >> >> ===============================================================
<br>>> >> >> Jul 9 15:20:11 piias12 ./ser[23832]: XJAB:xjab_check_workers:
<br>>> >> >> worker[0][pid=23965] has exited - status=0 err=-1 errno=10
<br>>> >> >> Jul 9 15:20:11 piias12 ./ser[23832]: XJAB:xjab_check_workers:
<br>>> >> >> worker[1][pid=23966] has exited - status=0 err=-1 errno=10
<br>>> >> >> Jul 9 15:20:11 piias12 ./ser[23851]: XJAB:xjab_check_workers:
<br>>> >> >> worker[0][pid=23975] has exited - status=0 err=-1 errno=10
<br>>> >> >> Jul 9 15:20:11 piias12 ./ser[23851]: XJAB:xjab_check_workers:
<br>>> >> >> worker[1][pid=23976] has exited - status=0 err=-1 errno=10
<br>>> >> >> Jul 9 15:20:51 piias12 ./ser[23829]: Are we registering?
<br>>> >> >> Jul 9 15:20:51 piias12 ./ser[23829]: XJAB: Going ONline
in Jabber
<br>>> >> >> network!!!
<br>>> >> >> Jul 9 15:21:11 piias12 ./ser[23832]: XJAB:xjab_check_workers:
<br>>> >> >> worker[0][pid=23977] has exited - status=0 err=-1 errno=10
<br>>> >> >>
<br>>> >> >>
<br>>> >> >>
<br>>> >> >>
<br>>> >> >> --
<br>>> >> >> NOTICE: If received in error, please destroy and notify sender.
<br>>> >> >> Sender does not waive confidentiality or privilege, and use
is
<br>>> >> >> prohibited.
<br>>> >> >>
<br>>> >> >>
<br>>> >> >>
<br>>> >> >>
<br>>> >>
<br>>> ------------------------------------------------------------------------
<br>>> >> >>
<br>>> >> >> _______________________________________________
<br>>> >> >> Serusers mailing list
<br>>> >> >> serusers@lists.iptel.org
<br>>> >> >> <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
<br>>> >> >>
<br>>> >> >>
<br>>> >> >
<br>>> >> > _______________________________________________
<br>>> >> > Serusers mailing list
<br>>> >> > serusers@lists.iptel.org
<br>>> >> > <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
<br>>> >> >
<br>>> >>
<br>>> > --
<br>>> > NOTICE: If received in error, please destroy and notify sender.
<br>>> > Sender does not waive confidentiality or privilege, and use is
<br>>> > prohibited.
<br>>> >
<br>>> >
<br>>> >------------------------------------------------------------------------
<br>>>
<br>>> >
<br>>> >_______________________________________________
<br>>> >Serusers mailing list
<br>>> >serusers@lists.iptel.org
<br>>> ><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
<br>>> >
<br>>> >
<br>>>
<br>> --
<br>> NOTICE: If received in error, please destroy and notify sender.
<br>> Sender does not waive confidentiality or privilege, and use is
<br>> prohibited.
<br>>
<br>>
<br>>------------------------------------------------------------------------
<br>>
<br>>_______________________________________________
<br>>Serusers mailing list
<br>>serusers@lists.iptel.org
<br>><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a>
<br>>
<br>></blockquote>
<p>--
<br>NOTICE: If received in error, please destroy and notify sender.
Sender does not waive confidentiality or privilege, and use is prohibited.
<br> </html>