hello,
I must make some change to ser code and recompile it.
So, I'm searching to make some changes to pa module. i'm trying then
to send an email to one client to be notified of presence of some
contacts.
I'm trying with ser_08.12.tar.gz
can I think in other persistant changes or continue with my idea.
In bith case what can I do that.
I'm debutant on Ser.
Can you help me.
thanks in advance.
Refka
On 5/25/06, serusers-request(a)lists.iptel.org
<serusers-request(a)lists.iptel.org> wrote:
> Send Serusers mailing list submissions to
> serusers(a)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(a)lists.iptel.org
>
> You can reach the person managing the list at
> serusers-owner(a)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. Re: Mediaproxy gets confused (rusl)
> 2. Re: Hell Sir please help in SER (Andrey Kouprianov)
> 3. How to enable Authentication (Aniruddha Vaidya)
> 4. Re: How to enable Authentication (Andrey Kouprianov)
> 5. Re: How to enable Authentication (Andrey Kouprianov)
> 6. Re: How to enable Authentication (Andrey Kouprianov)
> 7. Re: How to enable Authentication (Andrey Kouprianov)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 25 May 2006 08:14:41 +0000
> From: rusl <rusl(a)jpfortune.org>
> Subject: Re: [Serusers] Mediaproxy gets confused
> To: serusers(a)lists.iptel.org
> Message-ID: <200605250814.41731.rusl(a)jpfortune.org>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hi, just to let everyone know, I found the problem.. In mediaproxy 1.4.2,
> they
> added a new "feature" which allows the called user to change his media
> stream
> with a 183, 200 status w/ SDP. But the thing is that usually it's the caller
> that initiates a mediachange, so when the caller sent a 200 or 183 for media
> change, mediaproxy thought it was the called that had a media change, and
> basically connected the caller to itself by saying that the caller was the
> called.
>
> I fixed it by "reversing" the functionality in mediaproxy.
>
> On Wednesday 24. May 2006 22:04, rusl wrote:
> > Hi, I was wondering whether anyone has seen this strange error before. It
> > happens intermittently, where mediaproxy gets confused as to who the
> > "called" IP is, it thinks the caller is the called and switches back and
> > forth.
> >
> > Any ideas?
> >
> > rusl..
> >
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
> > May 24 21:58:08 voice mediaproxy[15520]: session
> > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
> > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
> > _______________________________________________
> > Serusers mailing list
> > Serusers(a)lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 25 May 2006 16:22:01 +0700
> From: "Andrey Kouprianov" <andrey.kouprianov(a)gmail.com>
> Subject: [Serusers] Re: Hell Sir please help in SER
> To: serusers(a)iptel.org
> Message-ID:
> <ab5f5bda0605250222wc43a773ifb9103de26a1b6d5(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi,
>
> proxyIP takes only one IP address. You cannot say
>
> proxyIP = 81.21.33.35,127.0.0.1
>
> Instead try
>
> proxyIP = 81.21.33.35
>
> Then mail me if you have problem. Your ser.cfg seems like the one from
> getting started document. It should work just fine.
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 25 May 2006 16:03:33 +0530
> From: "Aniruddha Vaidya" <anir123(a)gmail.com>
> Subject: [Serusers] How to enable Authentication
> To: Serusers(a)lists.iptel.org
> Message-ID:
> <7759a74d0605250333x5ae6196ekc780dc3d8d7ff064(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello All,
> I'm trying to enable the authentication feature in SER. But its not accepted
> by the server.
> This is my ser.cfg file.
>
> Can you tell me whats wrong ?
>
> #
> # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $
> #
> # simple quick-start config script
> #
>
> # ----------- global configuration parameters ------------------------
>
> #debug=3 # debug level (cmd line: -dddddddddd)
> #fork=yes
> #log_stderror=no # (cmd line: -E)
>
> # Uncomment these lines to enter debugging mode
> #fork=no
> #log_stderror=yes
> #
>
> check_via=no # (cmd. line: -v)
> dns=no # (cmd. line: -r)
> rev_dns=no # (cmd. line: -R)
> port=5060
> children=4
> fifo="/tmp/ser_fifo"
>
> # ------------------ module loading ----------------------------------
>
> # Uncomment this if you want to use SQL database
> loadmodule "/usr/local/lib/ser/modules/mysql.so"
>
> loadmodule "/usr/local/lib/ser/modules/sl.so"
> loadmodule "/usr/local/lib/ser/modules/tm.so"
> loadmodule "/usr/local/lib/ser/modules/rr.so"
> loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
> loadmodule "/usr/local/lib/ser/modules/usrloc.so"
> loadmodule "/usr/local/lib/ser/modules/registrar.so"
> loadmodule "/usr/local/lib/ser/modules/textops.so"
>
> # Uncomment this if you want digest authentication
> # mysql.so must be loaded !
> #loadmodule "/usr/local/lib/ser/modules/auth.so"
> #loadmodule "/usr/local/lib/ser/modules/auth_db.so"
>
> # ----------------- setting module-specific parameters ---------------
>
> # -- usrloc params --
>
> #modparam("usrloc", "db_mode", 0)
>
> # Uncomment this if you want to use SQL database
> # for persistent storage and comment the previous line
> modparam("usrloc", "db_mode", 2)
>
> # -- auth params --
> # Uncomment if you are using auth module
> #
> modparam("auth_db", "calculate_ha1", yes)
> #
> # If you set "calculate_ha1" parameter to yes (which true in this config),
> # uncomment also the following parameter)
> #
> modparam("auth_db", "password_column", "password")
>
> # -- rr params --
> # add value to ;lr param to make some broken UAs happy
> modparam("rr", "enable_full_lr", 1)
>
> # ------------------------- request routing logic -------------------
>
> # main routing logic
>
> route{
>
> # initial sanity checks -- messages with
> # max_forwards==0, or excessively long requests
> if (!mf_process_maxfwd_header("10")) {
> sl_send_reply("483","Too Many Hops");
> break;
> };
> if (msg:len >= 2048 ) {
> sl_send_reply("513", "Message too big");
> break;
> };
>
>
> # we record-route all messages -- to make sure that
> # subsequent messages will go through our proxy; that's
> # particularly good if upstream and downstream entities
> # use different transport protocol
> if (!method=="REGISTER") record_route();
>
> # subsequent messages withing a dialog should take the
> # path determined by record-routing
> if (loose_route()) {
> # mark routing logic in request
> append_hf("P-hint: rr-enforced\r\n");
> route(1);
> break;
> };
>
> if (!uri==myself) {
> # mark routing logic in request
> append_hf("P-hint: outbound\r\n");
> route(1);
> break;
> };
>
> # if the request is for other domain use UsrLoc
> # (in case, it does not work, use the following command
> # with proper names and addresses in it)
> if (uri==myself) {
>
> if (method=="REGISTER") {
>
> # Uncomment this if you want to use digest authentication
> if (!www_authorize("<InternalSER>", "subscriber")) {
> www_challenge("<InternalSER>", "0");
> break;
> };
>
> save("location");
> break;
> };
>
> lookup("aliases");
> if (!uri==myself) {
> append_hf("P-hint: outbound alias\r\n");
> route(1);
> break;
> };
>
> # native SIP destinations are handled using our USRLOC DB
> if (!lookup("location")) {
> sl_send_reply("404", "Not Found");
> break;
> };
> };
> append_hf("P-hint: usrloc applied\r\n");
> route(1);
> }
>
> route[1]
> {
> # send it out now; use stateful forwarding as it works reliably
> # even for UDP2TCP
> if (!t_relay()) {
> sl_reply_error();
> };
> }
>
>
> Thanks,
> Aniruddha
>
Hello,
I must make some change to ser code and recompile it.
So, I'm searching to make some changes to pa module. i'm trying then
to send an email to one client to be notified of presence of some
contacts.
I'm trying with ser_08.12.tar.gz
can I think in other persistant changes or continue with my idea.
In bith case what can I do that.
I'm debutant on Ser.
Can you help me.
thanks in advance.
Refka
Hi,
Please, just call me Andrey.
So, you are using X-lite. Try setting Send Internal IP to "Always".
Your contact header fields must contain the NATed IP addressed (that's
what that setting will do), but now they are your proxy's. I think, I
had this kind of problem before...
On 5/25/06, ravi reddy <mravikreddy(a)gmail.com> wrote:
> Hello Mr.Andrey Kouprianov
>
> I made some changes in my mediaproxy and it starts with no errors
> in that even i saw in log messages it is perfetly say mediaproxy server is
> on and socked is /var/run/mediaproxy.sock
>
>
> and i registerd three users and even now when iam calling there is no
> sound in both ways at first i get succsess for only one call and i saw in
> sessions.py every thing is o.k but after one hour again i tried but i dont
> know what is happening here
>
> here are some messages i found in ngrep port 5060
>
>
> 213.149.178.204:5060 -> 81.21.33.35:5060
> SIP/2.0 200 Ok..Via: SIP/2.0/UDP
> 81.21.33.35;branch=z9hG4bK471b.a07c0605.0..Via: SIP/2.0/UDP
> 81.21.34.34:5060;rport=5060
> ;branch=z9hG4bKC2A7F34D7D1D49139D47222CE36B2163..From:
> 32331000 <sip:32331000@81.21.33.35>;tag=630051386..To: <sip:32331
> 002(a)81.21.33.35>;tag=1982025997..Contact:
> <sip:32331002@213.149.178.204:5060>..Call-ID:
> 9602F577-35D2-4596-BB54-5A28F865
> 6802@192.168.0.77..CSeq: 24309 BYE..Server: X-Lite release
> 1105x..Content-Length: 0....
> #
> U 81.21.33.35:5060 -> 81.21.34.34:5060
> SIP/2.0 200 Ok..Via: SIP/2.0/UDP
> 81.21.34.34:5060;rport=5060;branch=z9hG4bKC2A7F34D7D1D49139D47222CE36B2163..From:
> 32331
> 000 <sip:32331000@81.21.33.35>;tag=630051386..To:
> <sip:32331002@81.21.33.35>;tag=1982025997..Contact: <sip:32331002@213.
> 149.178.204:5060>..Call-ID:
> 9602F577-35D2-4596-BB54-5A28F8656802@192.168.0.77..CSeq:
> 24309 BYE..Server: X-Lite release 1
> 105x..Content-Length: 0....
> #
> U 81.21.34.34:5060 -> 81.21.33.35:5060
>
> the phone is connecting fine and when connects i dont hear any sounds
>
>
> Sir, i need your help and iam very desperate to make this sucessfull global
> calls i hope you will solve my problem thanks
>
> kindly regards
> Ravi.
>
>
>
>
Hi Vaclav,
I want to install and run Ser on an identical linux setup with you to overcome the notification sending issue (thus presence)
That's why I need the library versions that you use.
Also I need to know which version of Debian Sarge you are using.
And your ser snapshot version.
Can you supply me these information please ?
Thanks,
ilker
________________________________
From: İlker Aktuna (Koç.net)
Sent: Tuesday, May 23, 2006 5:44 PM
To: 'samuel'
Cc: Vaclav Kubart; serusers(a)iptel.org
Subject: RE: PA error sending notifies
So you are not able to use presence but other traffic (IM, voice etc.) is fine ?
Do you know the xml parser library that your system has installed ?
Vaclav, which library version do you use ?
Thanks,
ilker
-----Original Message-----
From: samuel [mailto:samu60@gmail.com]
Sent: Tuesday, May 23, 2006 5:05 PM
To: İlker Aktuna (Koç.net)
Cc: Vaclav Kubart; serusers(a)iptel.org
Subject: Re: PA error sending notifies
Unfortunately I had no more time to look into it, so I have no more progress..I just saw that the contact header was not properly parsed and there were problems when selecting the local socket where to send the notifies from...I hope in the following weeks I find some more time to spend on it.
Samuel.
2006/5/23, İlker Aktuna (Koç. net ) <ilkera(a)koc.net>:
>
>
>
>
> Hi Samuel,
>
> Did you solve the issue where sending notifies would fail with error
> code -7 ?
>
> "Can't send watcherinfo notification (-7)"
>
> If you solved it can you tell me how ?
>
> I believe the problem is occuring while creating the headers. Because
> in "notify.c" I see that -7 is returned only while creating headers.
>
> Regards,
> ilker
>
<http://387555.sigclick.mailinfo.com/sigclick/010C0504/0C074F07/040D4E03/024…>
_____________________________________________________________________________________________________________________________________________
Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez.
This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence.
_____________________________________________________________________________________________________________________________________________
Hello All,
I'm trying to enable the authentication feature in SER. But its not accepted
by the server.
This is my ser.cfg file.
Can you tell me whats wrong ?
#
# $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $
#
# simple quick-start config script
#
# ----------- global configuration parameters ------------------------
#debug=3 # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no # (cmd line: -E)
# Uncomment these lines to enter debugging mode
#fork=no
#log_stderror=yes
#
check_via=no # (cmd. line: -v)
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
port=5060
children=4
fifo="/tmp/ser_fifo"
# ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database
loadmodule "/usr/local/lib/ser/modules/mysql.so"
loadmodule "/usr/local/lib/ser/modules/sl.so"
loadmodule "/usr/local/lib/ser/modules/tm.so"
loadmodule "/usr/local/lib/ser/modules/rr.so"
loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
loadmodule "/usr/local/lib/ser/modules/usrloc.so"
loadmodule "/usr/local/lib/ser/modules/registrar.so"
loadmodule "/usr/local/lib/ser/modules/textops.so"
# Uncomment this if you want digest authentication
# mysql.so must be loaded !
#loadmodule "/usr/local/lib/ser/modules/auth.so"
#loadmodule "/usr/local/lib/ser/modules/auth_db.so"
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
#modparam("usrloc", "db_mode", 0)
# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
modparam("usrloc", "db_mode", 2)
# -- auth params --
# Uncomment if you are using auth module
#
modparam("auth_db", "calculate_ha1", yes)
#
# If you set "calculate_ha1" parameter to yes (which true in this config),
# uncomment also the following parameter)
#
modparam("auth_db", "password_column", "password")
# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# initial sanity checks -- messages with
# max_forwards==0, or excessively long requests
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
break;
};
if (msg:len >= 2048 ) {
sl_send_reply("513", "Message too big");
break;
};
# we record-route all messages -- to make sure that
# subsequent messages will go through our proxy; that's
# particularly good if upstream and downstream entities
# use different transport protocol
if (!method=="REGISTER") record_route();
# subsequent messages withing a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
append_hf("P-hint: rr-enforced\r\n");
route(1);
break;
};
if (!uri==myself) {
# mark routing logic in request
append_hf("P-hint: outbound\r\n");
route(1);
break;
};
# if the request is for other domain use UsrLoc
# (in case, it does not work, use the following command
# with proper names and addresses in it)
if (uri==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use digest authentication
if (!www_authorize("<InternalSER>", "subscriber")) {
www_challenge("<InternalSER>", "0");
break;
};
save("location");
break;
};
lookup("aliases");
if (!uri==myself) {
append_hf("P-hint: outbound alias\r\n");
route(1);
break;
};
# native SIP destinations are handled using our USRLOC DB
if (!lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
};
append_hf("P-hint: usrloc applied\r\n");
route(1);
}
route[1]
{
# send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
};
}
Thanks,
Aniruddha
Hi,
proxyIP takes only one IP address. You cannot say
proxyIP = 81.21.33.35,127.0.0.1
Instead try
proxyIP = 81.21.33.35
Then mail me if you have problem. Your ser.cfg seems like the one from
getting started document. It should work just fine.
Hi, I was wondering whether anyone has seen this strange error before. It
happens intermittently, where mediaproxy gets confused as to who the "called"
IP is, it thinks the caller is the called and switches back and forth.
Any ideas?
rusl..
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820)
May 24 21:58:08 voice mediaproxy[15520]: session
7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from
10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622)
