24 Jun
2004
24 Jun
'04
3:22 a.m.
I think serweb use neither TCP or UDP but FIFO. So, you won't be able to
sniff the packets, not that I know. The TCP traffic you see may well be HTTP
request.
If you want to see what the FIFO request transforms to, use the xlog
function in ser to print it out. The latest CVS release lets you print the
whole message.
If you want to see how serweb construct the FIFO request and do something
similar, look into the code.
Zeus
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] On Behalf Of Gala, Dipen
Sent: Thursday, 24 June 2004 3:54 AM
To: serusers(a)lists.iptel.org
Subject: [Serusers] SERWEB packets
Guys I have my serweb running and I am trying to sniff the
sip packets through ethereal sniffer s/w
But to my shock there is no sip traffic.
I guess serweb uses TCP instead of UDP bcoz I am seeing tons
of TCP traffic.
Has any one encountered such thing.
Can I change the serweb setting so that I can have UDP
instead of TCP. Also if its working on TCP how can I see my
sip information..
Also does anyone knows how the hell can I use serweb to make a call
I have added users in my phone book
But they always show offline, even though they have logged in.
If anybody can share his ser.cfg with me for this it will be
very nice
Thanks
Dipen K Gala
Fidelity Investments System Company - Telecom
Phone: (617) 563-2729
Email: Dipen.Gala(a)FMR.com