Hi Vaclav,
My intension is not to disturb you, but I didn't receive a reply from you for the following email.
Di you receive it ?
Have a nice day,
ilker
________________________________
From: İlker Aktuna (Koç.net)
Sent: Thursday, May 04, 2006 4:20 PM
To: 'Vaclav Kubart'
Cc: serusers(a)lists.iptel.org
Subject: RE: [Serusers] IM and presence problems
Hi Vaclav,
I've run with no NAT; ngrep output and ser log with debug=4 is attached.
You can see that Ser server can ping the contact address at the end of the ngrep output.
In the debug log I filtered the process ID 2905 for you. I hope it helps to figure out where the problem is.
Btw, xcap root does not have any index file. Eyebeam client does not receive xcap authorization request.
Presentity is not shown also.
Online IM messages are working but offline messages don't reach user (maybe it's related).
Today I returned back to the eyebeam 1.1 release and results are the same.
Thanks,
ilker
-----Original Message-----
From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent: Thursday, May 04, 2006 3:02 PM
To: İlker Aktuna (Koç.net)
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
Hi,
run it without NAT and debug=4 and send me ngrep dump again. In the log try to find debug messages containing next hop address like:
May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: DEBUG:tm:t_uac: next_hop=<sip:200000900568888888@192.168.2.17:26548;transport=udp>
May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free(0x8120e80, 0x81703b0), called from data_lump.c: free_lump_list(409) May 2 13:19:51 sesapp /root/ser/sbin/ser[19886]: qm_malloc(0x8120e80, 32) called from data_lump.c: insert_cond_lump_after(216) May 2 13:19:51 sesapp /root/ser/sbin/ser[19888]: qm_malloc(0x8120e80, 8) returns address 0x81706b8 frag. 0x81706a0 (size=8) on 1 -th hit May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free: freeing frag. 0x8170398 alloc'ed from data_lump.c: insert_new_lump_before(140)
In this sample is next_hop =
sip:200000900568888888@192.168.2.17:26548;transport=udp. The number of process has to be the same as in consequent error message "t_uac: socket not found". It is the number in [ ] - in this case 19887.
The address there has to be accessible from machine with SER (try to ping the IP).
The index file is not needed.
And are watchers authorized? (Do they see status of presentity?)
Vaclav
On Thu, May 04, 2006 at 02:52:39PM +0300, ?lker Aktuna (Koç.net) wrote:
> Hi Vaclav,
>
> I still couldn't succeed in presence over SER.
> Still getting following messages, no matter if I'm behid NAT or not.
> I tested on LAN many times but I still get same error messages.
>
> Btw, there is no index file in my xcap-root directory. Should I have something there ?
> I didn't receive any xcap authorization request after changing xcap
> authorization root to real hostname instead of 127.0.0.1
>
> May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: t_uac: no socket
> found May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: t_uac: no
> socket found May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: ERROR:
> notify.c:398: Can't send watcherinfo notification (-7) May 4 14:42:27
> sesapp /root/ser/sbin/ser[19996]: ERROR: notify.c:398: Can't send
> watcherinfo notification (-7) May 4 14:42:27 sesapp
> /root/ser/sbin/ser[19996]: send_winfo_notify returned -7 May 4
> 14:42:27 sesapp /root/ser/sbin/ser[19996]: send_winfo_notify returned
> -7
>
>
> Thanks,
> ilker
>
>
> -----Original Message-----
> From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
> Sent: Tuesday, May 02, 2006 5:50 PM
> To: ?lker Aktuna (Koç.net)
> Cc: serusers(a)lists.iptel.org
> Subject: Re: [Serusers] IM and presence problems
>
> Try to use nathelper module. I'm not familiar with it but there exists some documentation for it (in modules/nathelper/README).
>
> Vaclav
>
> On Tue, May 02, 2006 at 05:19:10PM +0300, ?lker Aktuna (Koç.net) wrote:
> > Hi Vaclav,
> >
> > The ngrep.out file was from Friday. And I realized that I'd changed Eyebeam client configuration after Friday.
> > Now it sends internal IP as contact. (as in the attached ngrep2.out
> > file)
> >
> > Now I don't know how to change the contact as public IP. But
> > presencce messages were not working Friday also
> >
> > Any idea how to change the contact as public IP ?
> >
> > Thanks,
> > ilker
> >
> >
> > -----Original Message-----
> > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
> > Sent: Tuesday, May 02, 2006 2:56 PM
> > To: ?lker Aktuna (Koç.net)
> > Cc: serusers(a)lists.iptel.org
> > Subject: Re: [Serusers] IM and presence problems
> >
> > > 192.168.2.17 is a NAT client behing 85.105.102.167 Could it be
> > > that the SER is sending the messages to the internal IP address of my Eyebeam client ?
> >
> > It seems so.
> >
> > > On eyebeam 1.5 I use the "use rport" option of the client if that matters.
> > >
> > > Any idea why I get so many "no socket found" errors ? (might it be
> > > because ser is trying to connect to the internal IP address ?)
> >
> > SER tries to connect to IP address which is not accessible for it. And it tries again and again...
> >
> > But I don't know how this IP address got to presence SER, because there was 85.xxx.xxx.xxx in Contact in SUBSCRIBE request in the network dump.
> >
> > Vaclav
> >
> > >
> > > Thanks,
> > > ilker
> > >
> > >
> > > -----Original Message-----
> > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
> > > Sent: Tuesday, May 02, 2006 1:34 PM
> > > To: ?lker Aktuna (Koç.net)
> > > Cc: serusers(a)lists.iptel.org
> > > Subject: Re: [Serusers] IM and presence problems
> > >
> > > I take a look into the log and it seems, that NOTIFY requests try to be sent to 192.168.2.17.
> > >
> > > But in the ngrep dump I see only some 85.105.102.167 addresses in Contacts in SUBSCRIBE requests. Are you sure, that these log and the flow belong to the same scenario?
> > >
> > > If yes, it means, that there is a bug in PA module.
> > >
> > > Be sure to catch messages on machine with presence server.
> > >
> > > Vaclav
> > >
> > > On Tue, May 02, 2006 at 01:14:37PM +0300, ?lker Aktuna (Koç.net) wrote:
> > > > Hi,
> > > >
> > > > I've captured debug logs by suggestion of Mr. Michal Matyska.
> > > > Attached I'm sending them to you. I hope it reaches you.
> > > > Please look for the "no socket found" and "Can't send watcherinfo notification " lines in the log as it's too long.
> > > >
> > > > Thanks,
> > > > ilker
> > > >
<http://387555.sigclick.mailinfo.com/sigclick/030A0701/07004E0D/090B4C06/902…>
_____________________________________________________________________________________________________________________________________________
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.
_____________________________________________________________________________________________________________________________________________
Hi,
I've checked the error messages again and the following error message indicates that watcherinfo notification can't be sent with reason -7
Then I looked at the notify.c in pa module. -7 is returned if there is a problem while adding headers.
I'm not sure what headers are being added but maybe this could be a clue to fix the problem.
there is an if block from notify.c below...
Any idea ?
ERROR: notify.c:398: Can't send watcherinfo notification (-7)
##### FROM notify.c :
if (create_headers(_w, &headers, &content_type) < 0) {
LOG(L_ERR, "send_presence_notify(): Error while adding headers\n");
str_free_content(&doc);
str_free_content(&content_type);
return -7;
}
Thanks,
ilker
________________________________
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net)
Sent: Monday, May 08, 2006 12:37 PM
To: Vaclav Kubart
Cc: serusers(a)lists.iptel.org
Subject: RE: [Serusers] IM and presence problems
Hi Vaclav,
My intension is not to disturb you, but I didn't receive a reply from you for the following email.
Di you receive it ?
Have a nice day,
ilker
________________________________
From: İlker Aktuna (Koç.net)
Sent: Thursday, May 04, 2006 4:20 PM
To: 'Vaclav Kubart'
Cc: serusers(a)lists.iptel.org
Subject: RE: [Serusers] IM and presence problems
Hi Vaclav,
I've run with no NAT; ngrep output and ser log with debug=4 is attached.
You can see that Ser server can ping the contact address at the end of the ngrep output.
In the debug log I filtered the process ID 2905 for you. I hope it helps to figure out where the problem is.
Btw, xcap root does not have any index file. Eyebeam client does not receive xcap authorization request.
Presentity is not shown also.
Online IM messages are working but offline messages don't reach user (maybe it's related).
Today I returned back to the eyebeam 1.1 release and results are the same.
Thanks,
ilker
-----Original Message-----
From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent: Thursday, May 04, 2006 3:02 PM
To: İlker Aktuna (Koç.net)
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
Hi,
run it without NAT and debug=4 and send me ngrep dump again. In the log try to find debug messages containing next hop address like:
May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: DEBUG:tm:t_uac: next_hop=<sip:200000900568888888@192.168.2.17:26548;transport=udp>
May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free(0x8120e80, 0x81703b0), called from data_lump.c: free_lump_list(409) May 2 13:19:51 sesapp /root/ser/sbin/ser[19886]: qm_malloc(0x8120e80, 32) called from data_lump.c: insert_cond_lump_after(216) May 2 13:19:51 sesapp /root/ser/sbin/ser[19888]: qm_malloc(0x8120e80, 8) returns address 0x81706b8 frag. 0x81706a0 (size=8) on 1 -th hit May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free: freeing frag. 0x8170398 alloc'ed from data_lump.c: insert_new_lump_before(140)
In this sample is next_hop =
sip:200000900568888888@192.168.2.17:26548;transport=udp. The number of process has to be the same as in consequent error message "t_uac: socket not found". It is the number in [ ] - in this case 19887.
The address there has to be accessible from machine with SER (try to ping the IP).
The index file is not needed.
And are watchers authorized? (Do they see status of presentity?)
Vaclav
On Thu, May 04, 2006 at 02:52:39PM +0300, ?lker Aktuna (Koç.net) wrote:
> Hi Vaclav,
>
> I still couldn't succeed in presence over SER.
> Still getting following messages, no matter if I'm behid NAT or not.
> I tested on LAN many times but I still get same error messages.
>
> Btw, there is no index file in my xcap-root directory. Should I have something there ?
> I didn't receive any xcap authorization request after changing xcap
> authorization root to real hostname instead of 127.0.0.1
>
> May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: t_uac: no socket
> found May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: t_uac: no
> socket found May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: ERROR:
> notify.c:398: Can't send watcherinfo notification (-7) May 4 14:42:27
> sesapp /root/ser/sbin/ser[19996]: ERROR: notify.c:398: Can't send
> watcherinfo notification (-7) May 4 14:42:27 sesapp
> /root/ser/sbin/ser[19996]: send_winfo_notify returned -7 May 4
> 14:42:27 sesapp /root/ser/sbin/ser[19996]: send_winfo_notify returned
> -7
>
>
> Thanks,
> ilker
>
>
> -----Original Message-----
> From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
> Sent: Tuesday, May 02, 2006 5:50 PM
> To: ?lker Aktuna (Koç.net)
> Cc: serusers(a)lists.iptel.org
> Subject: Re: [Serusers] IM and presence problems
>
> Try to use nathelper module. I'm not familiar with it but there exists some documentation for it (in modules/nathelper/README).
>
> Vaclav
>
> On Tue, May 02, 2006 at 05:19:10PM +0300, ?lker Aktuna (Koç.net) wrote:
> > Hi Vaclav,
> >
> > The ngrep.out file was from Friday. And I realized that I'd changed Eyebeam client configuration after Friday.
> > Now it sends internal IP as contact. (as in the attached ngrep2.out
> > file)
> >
> > Now I don't know how to change the contact as public IP. But
> > presencce messages were not working Friday also
> >
> > Any idea how to change the contact as public IP ?
> >
> > Thanks,
> > ilker
> >
> >
> > -----Original Message-----
> > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
> > Sent: Tuesday, May 02, 2006 2:56 PM
> > To: ?lker Aktuna (Koç.net)
> > Cc: serusers(a)lists.iptel.org
> > Subject: Re: [Serusers] IM and presence problems
> >
> > > 192.168.2.17 is a NAT client behing 85.105.102.167 Could it be
> > > that the SER is sending the messages to the internal IP address of my Eyebeam client ?
> >
> > It seems so.
> >
> > > On eyebeam 1.5 I use the "use rport" option of the client if that matters.
> > >
> > > Any idea why I get so many "no socket found" errors ? (might it be
> > > because ser is trying to connect to the internal IP address ?)
> >
> > SER tries to connect to IP address which is not accessible for it. And it tries again and again...
> >
> > But I don't know how this IP address got to presence SER, because there was 85.xxx.xxx.xxx in Contact in SUBSCRIBE request in the network dump.
> >
> > Vaclav
> >
> > >
> > > Thanks,
> > > ilker
> > >
> > >
<http://387555.sigclick.mailinfo.com/sigclick/07090503/04034D04/04034E04/141…>
_____________________________________________________________________________________________________________________________________________
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 find a solution to overcome the NAT issue using only the nathelper module.
(I've already successfully worked with 'STUN' & 'MediaProxy'
solutions but I'm trying also this).
1. OUTBOUND direction:
--- INVITE handler ---
...
# NAT Traversal mechanism for INVITEs
if (nat_uac_test("19")) {
setflag(7);
force_rport();
fix_nated_contact();
fix_nated_sdp("3");
};
#
...
The solution above works fine for OUTBOUND calls,
either on-net (a) or off-net (b). (For off-net calls I use a Cisco GW).
a/ SIP_UA_behind_NAT -------- SER ------- SIP_UA_on_public_IP
b/ SIP_UA_behind_NAT -------- SER ------- Cisco_PSTN_GW ------- PSTN
2. INBOUND direction:
route[1] {
# Default Message Handler
t_on_reply("1");
if (!t_relay()) {
log(1, " - Cannot RELAY !!!");
sl_reply_error();
};
}
onreply_route[1] {
if (nat_uac_test("19")) {
log(1, " - Response behind NAT...");
setflag(7);
force_rport();
fix_nated_contact();
fix_nated_sdp("3");
};
}
Although I have two-way audio between calling and called parties,
I get the following logging mesgs :
May 3 17:22:26 server ./ser[13705]: ERROR: extract_body: message body has length zero
May 3 17:22:26 server ./ser[13705]: ERROR: fix_nated_sdp: cannot extract body from msg!
May 3 17:22:26 server ./ser[13705]: ERROR: on_reply processing failed
My question is :
Is the above the correct way for NAT traversal of SIP Responses (200 OK) ?
Do I have to add something else somewhere in ser.cfg ?
Any idea on the log mesgs above ?
thanks in advance for any help,
Kostas
Still having some issues when trying to simulate a XCAP server with SER and
eyeBeam softphone.
I'm using presence snapshot «ser-0.10.99-dev35-pa-4» with the
ser.cfgprovided (some changes to adapt to my domain)
When I start SER I always get this warning:
WARNING: xl_mod_init: DIFFERENT hostname 'xxxxx' and gethostbyname
'localhost.localdomain'
Can't find any thread about this, don't think it is crucial...
I added the domain and users to SER's DB using serctl.
When I start eyeBeam, it registers fine on SER. (SER log: MSILO: offline
messages for sip:xxx@xxxxxx dumped)
But if I have configured XCAP on Server-side Storage (and Presence Mode
disabled) eyeBeam sends a «SUBSCRIBE sip:4004» to SER with header «Event:
sip-profile;profile-type=application;app-id=resource-lists» which SER
responds with «Status: 489 Unsupported event package».
SER log:
check_message(): Unsupported event package
ERROR: subscribe.c:856: Error while checking message
ERROR: subscribe.c:942: handle_subscription about to send_reply and
return -2
----
Then I configured the Presence Mode as Presence Agent and registered two
eyeBeam clients, sip:4002 and sip:4004.
User sip:4002 has sip:4004 on his buddy list and sip:4004 has allowed
sip:4002 to watch his presence status.
REGISTER is OK for both.
SER log:
MSILO: offline messages for sip:xxx@xxxxxx dumped
dumping stored winfo to sip:xxx@xxxxxx
sip:4002 sends «SUBSCRIBE sip:4002» (Event: presence.winfo) and SER respond
with 200 OK.
But then sip:4002 keeps sending reliable «SUBSCRIBE sip:4004» (Event:
presence) and «PUBLISH sip:4002» (Event: presence) and SER only responds
after aprox. 60 seconds with 202 Accepted to «SUBSCRIBE sip:4004» and 200 OK
to «PUBLISH sip:4002».
Client sip:4002 also receives from SER a «NOTIFY sip:4002» (From:
<sip:4004>, To: <sip:4002>, Event: presence, Subscription-State:
pending;expires=xxx) which sip:4002 responds with «Status: 481
Call/transaction Dos Not Exist»
I think SER is experiencing some kind of lock/delay when it receives
SUBSCRIBE (Event: presence.winfo) from more than one client.
SER log:
MSILO: offline messages for sip:4002@xxxxxx dumped
Warning: run_failure_handlers: no UAC support (0,0)
MSILO: offline messages for sip:4004@xxxxxx dumped
After some time, SER sends again to sip:4002 a «NOTIFY sip:4002» (From:
<sip:4004>, To: <sip:4002>, Event: presence) but this time with header
Subscription-State: terminated;reason=timeout, which sip:4002 responds with
«Status: 481 Call/transaction Dos Not Exist»
(SER log: Warning: run>failure_handlers: no UAC support (0,0) )
The SUBSCRIBE (Event: presence.winfo) keeps being renewed...
When I change presence status on sip:4002, it sends «PUBLISH sip:4002»
(Content-Type: application/pidf+xml; Event: presence) which SER responds
with 200 OK.
SER log:
MSILO: offline messages for sip:4002@xxxxx dumped
I'm lost here.
Server-side Storage with XCAP works fine for presence-rules and
resource-lists but the presence agent don't.
I will run some more tests but this time with SER not saving offline
messages.
Hi
I have installed 0.9.6 on my FC5 Server
iam able to compile there is no errors
when i try to start SER
ERROR; bad config file ( 6 errors)
iam getting this errors in message
May 7 20:35:05 crm ser: set_mod_param_regex: parameter <db_url> not found
in module <uri>
May 7 20:35:05 crm ser: parse error (69,4-5): Can't set module parameter
May 7 20:35:05 crm ser: set_mod_param_regex: parameter <db_flag> not found
in module <acc>
May 7 20:35:05 crm ser: parse error (89,20-21): Can't set module parameter
May 7 20:35:05 crm ser: set_mod_param_regex: parameter <db_missed_flag> not
found in module <acc>
May 7 20:35:05 crm ser: parse error (90,20-21): Can't set module parameter
May 7 20:35:05 crm ser: parse error (119,14-21): syntax error
May 7 20:35:05 crm ser: parse error (119,22-23): bad arguments
May 7 20:35:05 crm ser: parse error (413,24-25): unknown command, missing
loadmodule?
any help will be great
ram
hi,
I have used the SER "getting started" document and the quick start script
packaged in openser 1.0.1 to make my way thru authenticating a pair of UAs
and having them call each other.
I am now reading the "Handling NAT" section with the goal of using
mediaproxy to do the far-end NAT traversal.
Question: Is there a pre-made openser.cfg script using mediaproxy to do
far-end NAT traversal available for 1.0.1 If not does the one in the SER
"getting started" document work on Openser 1.0.1??
tnx
Hi,
Recently, I noticed there is an error from the log for a particular user.
May 8 12:34:08 o01 /usr/local/sbin/openser[25451]: error:
mediaproxy/getSDPMessage(): SDP message has zero length
May 8 12:34:08 o01 /usr/local/sbin/openser[25451]: error:
use_media_proxy(): failed to get the SDP message
It seems that mediaproxy can't get the SDP message and the user failed
to make/receive call in such error occurred. As the user is using
ipphone behine NAT, I wonder if it is related to the router problem.
Any suggestion for this error?
unplug
Hello to everybody,
I have openser 1.1 installed on a machine which has an ADSL internet connection.
My question is: as the ip address is a public IP (80.xxxx...),
do I need any module for nat tunneling? (mediaproxy or nathelper...)
I mean, if all the UAs are connected to internet via ADSL (different providers), do I need to set NAT modules?
Thanks
Alex
Just need confirmation for my thoughts and start digging into C code.
Is there some other option to reuse existing MySQL database with
usernames/passwords of my users - mysql module doesn't have any export
functions and extcmd seems to be abandoned.
Darko
Hello Everybody,
I'm new to openser and also to freeradius.
1)how to insert the users in freeradius server
2) When I test with radiusd - X its show somes errors .
The errors are mention below
/usr/local/etc/raddb/users[64]: Unexpected trailing comma in check item
list for entry test
Errors reading /usr/local/etc/raddb/users
radiusd.conf[1047]: files: Module instantiation failed.
radiusd.conf[1791] Unknown module "files".
radiusd.conf[1727] Failed to parse authorize section.
3) And also when tested the clients , by using "radclient -f digest
localhost auth <shared_secret>" . It shows the following error
radclient : no respones from server ID 134
4) And also when I tried with " radtest test test 192.168.2.55 5060
hyperion" its shows me below one
Sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
Re-sending Access-Request of id 233 to 192.168.2.55 port 1812
User-Name = "test"
radclient: no response from server for ID 233
5) when i also tried with "ps -aux | grep radiusd " it show a warning and
errors
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.3
/FAQ
root 13093 0.0 0.1 4276 696 pts/4 S+ 16:41 0:00 grep radiusd
Please help me in 5 issues which are mention above.
--
Thanks and Regards with cheers
Sunkara Ravi Prakash (Voip Developer)
Hyperion Technology
www.hyperion-tech.com
