After doing a cvs update on a FreeBSD 4.9/SER 0.8.12 system I
can no longer build the server. Issuing any of the documented "make"
commands results in the following error. Is this a known issue? If so
what is the cause?
Thanks,Steve
"Makefile.sources", line 17: Missing dependency operator
"Makefile.sources", line 19: Need an operator
"Makefile", line 52: Missing dependency operator
Error expanding embedded variable.
--
After installing radius client and doing necessary
changes in modules/acc/Makefile ,
[root@sip ser-0.8.12]# locate radiusclient.h
/usr/local/include/radiusclient.h
[root@sip ser-0.8.12]#make exclude_modules="" modules
and then
[root@sip ser-0.8.12]#make prefix=/usr/local install
But the following modules still did not install.
group_radius.so
uri_radius.so
auth_radius.so
mysql.so
any clue on the same.
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
Hello Jan:
Iptel.org has a prepaid system in the top of SER, but I would like to have a quotation to incorporate this into the services of Free
IP Call. Perhaps you could let me know the information that you require, in order to achieve this.
With Kind Regards
________________________
Martin Parr
Director of Development
AM Global Network Limited
SIP | 131-229-1010(a)sip.freeipcall.com
Free IP Call - www.freeipcall.com
The Home to Free IP Call
Internet Telephony Service & Consultancy
SIP and VoIP Networks Provider
<http://www.freeipcall.com/>
-----------------------------------------------------
Ce message et les pièces jointes sont confidentiels et établis à
l'attention exclusive de ses destinataires. Tout message électronique
est susceptible d'altération. Si vous n'êtes pas destinataire de ce
message, merci de le détruire et d'avertir immédiatement l'expéditeur.
This message and any attachments are confidential and intended solely
for the addressees. E-Mails are susceptible to alteration. If you are not
the intended recipient of the message, please delete it and notify the
sender immediately.
-----------------------------------------------------
1. You can replicate REGISTER messages, than every proxy has a complete
view of all registered proxy.
2. You could also use a special dial planes and user names: e.g. all
clients registered at SER start with 1, e.g. 12345. clients that
register at ser 2 begin with 2 in their usernames, e.g. 22345.
If SER1 receives a request for 2xxxx, it forwards the request to proxy 2.
btw: please always cc: to the list! (reply all)
regards,
Klaus
simple wrote:
> Ok, maybe I did not express my question very clearly, what I want is like this:
>
> ------ registered ---------
> | C1 |-----in---->| SER1 |\
> ------ --------- \ -----------
> / | Internet |
> ------ registered ---------/ -----------
> | C2 |-----in---->| SER2 |
> ------ ---------
>
> SER1 and SER2 are in different places, now, I want C1 can call C2. Do I need a exclusive public server to store user information database, and act like a redirect server, then, SER1 can forward C1's INVITE to SER2.
>
> Do you think there are other better solutions to support my demand? Thanks for your help.
>
> Regards!
>
> Simple Li
>
> ----- Original Message -----
> From: "Klaus Darilion" <klaus.mailinglists(a)pernau.at>
> To: "simple" <simple(a)vlichina.com>; "Serusers" <serusers(a)lists.iptel.org>
> Sent: Tuesday, February 10, 2004 3:34 PM
> Subject: Re: [Serusers] about distributed SER
>
>
>
>>Details: ser caches user lcoations, that means, if it lookup() a user,
>>ser does not query the database as the user lcoations are stored in RAM.
>>New REGISTER are stored by save(). The writeback into the database can
>>be done immediately (safe, but slower) or delayed (not so safe, but
>>faster). more info on this can be found in the README of the userloc module.
>>
>>So, now you know the basics to build up your system, e.g:
>>- 2 proxies + data bases
>>
>>--------------+ replicated REGISTER +------------+
>>| active proxy| -------------------------> |backup proxy|
>>--------------+ +------------+
>> | |
>> | |
>> | |
>> |data |data
>> |base |base
>> |write |write
>> |through |through
>> | |
>> V V
>>----------------+ +---------------+
>>|active database| |backup database|
>>----------------+ +---------------+
>>
>>if the active proxy or database fails, you have to switch over to the
>>bakup combination (manually or autmatically).
>>
>>You could also use only one database, but than only the active proxy is
>>allowed to save() to the database.
>>
>>You could also make the database failover transparent to the SIP proxy:
>>2 databases with replication enabled, and if the main one fails, the
>>backup db takes the IP address of the failed one.
>>
>>
>>So, these are some theoretical solutions. I hope the guys which uses ser
>>in production environments have some comments on this.
>>
>>regards,
>>Klaus
>>
>>PS: always CC to the list
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>simple wrote:
>>
>>>Thanks for your so quick reply, I still have a question, can you give a detail of the synchronization of several proxies? thanks!
>>>
>>>Simple Li
>>>
>>>
>>>----- Original Message -----
>>>From: "Klaus Darilion" <klaus.mailinglists(a)pernau.at>
>>>To: "simple" <simple(a)vlichina.com>
>>>Cc: <serusers(a)lists.iptel.org>
>>>Sent: Monday, February 09, 2004 6:30 PM
>>>Subject: Re: [Serusers] about distributed SER
>>>
>>>
>>>
>>>
>>>>Hi can use the several proxies and every proxy uses its own database for
>>>>uerlocation. The keep the userlocation consistent, you can use the
>>>>register() function to synchronize the several proxies.
>>>>
>>>>klaus
>>>>
>>>>simple wrote:
>>>>
>>>>
>>>>>Dear sir,
>>>>> I have an idea to use SER as SIP proxy in many different places,
>>>>>different clients register in defferent SER, there may be a centralized
>>>>>user information of all these clients, may be not, and all these clients
>>>>>can make a call to each other. So, my question is if there has
>>>>>an example used like this, otherwise, how can we make some changes to
>>>>>make this happen.
>>>>>
>>>>>Thanks!
>>>>>
>>>>>Simple Li
>>>>>
>>>>>
>>>>>
>>>>>------------------------------------------------------------------------
>>>>>
>>>>>_______________________________________________
>>>>>Serusers mailing list
>>>>>serusers(a)lists.iptel.org
>>>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>
>>>>
i hope phone is the problem...now i am trying cisco ata 186
Regards
Dhawan K
---------- Original Message -----------
From: "Madan" <madan.r(a)net4india.net>
To: "abhati" <abhati(a)primus-direct.com>
Cc: <kdhawan(a)primus-direct.com>
Sent: Tue, 10 Feb 2004 09:19:58 +0530
Subject: Re: [Serusers] Cancel call Problem
> what is the UA you guys are using? is it a soft phone or ATAs..?
>
> there could be prob with the UA you are using, use ngrep of ethreal to
> diagnose the sip headers/messages
>
> regards,
> Madan
> ----- Original Message -----
> From: "abhati" <abhati(a)primus-direct.com>
> To: <serusers(a)lists.iptel.org>
> Sent: Monday, February 09, 2004 7:19 PM
> Subject: [Serusers] Cancel call Problem
>
> > Hi All
> >
> > My problem is...i have got two phones set 111 and 222. if i make call from
> > 111 and don't pick up 222 and cancel the call, this all is fine. but my
> phone
> > gets hanged...both 111 and 222....what shud be done to properly handle
> cancel
> > requests.
> >
> > i am attaching my ser.cfg file.
> >
> > #
> > # $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 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
> > debug=7
> > 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/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"
> >
> > # 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"
> >
> > loadmodule "/usr/local/lib/ser/modules/domain.so"
> > loadmodule "/usr/local/lib/ser/modules/call.so"
> >
> > modparam("domain", "db_url", "sql://root:root@localhost/ser")
> > modparam("domain", "db_mode", 1) # Use chaching
> > modparam("domain", "domain_table", "domain")
> > modparam("domain", "domain_col", "domain")
> >
> > modparam("tm", "fr_inv_timer", 30 )
> > modparam("registrar", "default_expires", 60)
> > # ----------------- 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 > max_len ) {
> > 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
> > record_route();
> > # loose-route processing
> > if (loose_route()) {
> > t_relay();
> > 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 (is_from_local()) {
> >
> > if (method=="REGISTER") {
> >
> > # Uncomment this if you want to use digest authentication
> > if (!www_authorize("", "subscriber")) {
> > www_challenge("", "0");
> > break;
> > };
> > save("location");
> > break;
> > };
> >
> > # native SIP destinations are handled using our USRLOC DB
> >
> >
> > if (method=="INVITE") {
> > if(call()){ //written one module for few things works fine
> > if (!lookup("location")) {
> > sl_send_reply("404", "Not Found");
> > break;
> > };
> > };
> > };
> >
> > };
> > # forward to current uri now; use stateful forwarding; that
> > # works reliably even if we forward from TCP to UDP
> > if (!t_relay()) {
> > sl_reply_error();
> > };
> > }
> >
> >
> >
> > .
> >
> >
> >
> >
> >
> >
> >
> > Disclaimer
> > --------------------------------------------------------------------------
> > This email and any files transmitted with it are confidential
> > and intended solely for the use of the individual or entity
> > to whom they are addressed. If you have received this email
> > in error please notify the system manager. Recipients must
> > check this email and any attachments for the presence of
> > viruses before downloading them. Direct Internet /
> > Primus India accepts no liability for any damage caused by
> > any virus transmitted by this email.
> >
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers(a)lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
> >
------- End of Original Message -------
.
Disclaimer
--------------------------------------------------------------------------
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email
in error please notify the system manager. Recipients must
check this email and any attachments for the presence of
viruses before downloading them. Direct Internet /
Primus India accepts no liability for any damage caused by
any virus transmitted by this email.
http://203.196.128.126/output/
Regards
Dhawan K
.
Disclaimer
--------------------------------------------------------------------------
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email
in error please notify the system manager. Recipients must
check this email and any attachments for the presence of
viruses before downloading them. Direct Internet /
Primus India accepts no liability for any damage caused by
any virus transmitted by this email.
Details: ser caches user lcoations, that means, if it lookup() a user,
ser does not query the database as the user lcoations are stored in RAM.
New REGISTER are stored by save(). The writeback into the database can
be done immediately (safe, but slower) or delayed (not so safe, but
faster). more info on this can be found in the README of the userloc module.
So, now you know the basics to build up your system, e.g:
- 2 proxies + data bases
--------------+ replicated REGISTER +------------+
| active proxy| -------------------------> |backup proxy|
--------------+ +------------+
| |
| |
| |
|data |data
|base |base
|write |write
|through |through
| |
V V
----------------+ +---------------+
|active database| |backup database|
----------------+ +---------------+
if the active proxy or database fails, you have to switch over to the
bakup combination (manually or autmatically).
You could also use only one database, but than only the active proxy is
allowed to save() to the database.
You could also make the database failover transparent to the SIP proxy:
2 databases with replication enabled, and if the main one fails, the
backup db takes the IP address of the failed one.
So, these are some theoretical solutions. I hope the guys which uses ser
in production environments have some comments on this.
regards,
Klaus
PS: always CC to the list
simple wrote:
> Thanks for your so quick reply, I still have a question, can you give a detail of the synchronization of several proxies? thanks!
>
> Simple Li
>
>
> ----- Original Message -----
> From: "Klaus Darilion" <klaus.mailinglists(a)pernau.at>
> To: "simple" <simple(a)vlichina.com>
> Cc: <serusers(a)lists.iptel.org>
> Sent: Monday, February 09, 2004 6:30 PM
> Subject: Re: [Serusers] about distributed SER
>
>
>
>>Hi can use the several proxies and every proxy uses its own database for
>>uerlocation. The keep the userlocation consistent, you can use the
>>register() function to synchronize the several proxies.
>>
>>klaus
>>
>>simple wrote:
>>
>>>Dear sir,
>>> I have an idea to use SER as SIP proxy in many different places,
>>>different clients register in defferent SER, there may be a centralized
>>>user information of all these clients, may be not, and all these clients
>>>can make a call to each other. So, my question is if there has
>>>an example used like this, otherwise, how can we make some changes to
>>>make this happen.
>>>
>>>Thanks!
>>>
>>>Simple Li
>>>
>>>
>>>
>>>------------------------------------------------------------------------
>>>
>>>_______________________________________________
>>>Serusers mailing list
>>>serusers(a)lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serusers
>>
I can't see any problem in the config file. Which clients do you use?
Put log(1,"...."); messages into your config and watch the logging
messages in /var/log/messages during the CANCEL processing to find out
where the CANCEL request is beeing lost.
Klaus
Kapil Dhawan wrote:
> o its not happening...when first phone cancels the call....that CANCEL is not
> forwarded to callee phone
>
> Regards
>
> Dhawan K
>
> ---------- Original Message -----------
> From: Klaus Darilion <klaus.mailinglists(a)pernau.at>
> To: abhati <abhati(a)primus-direct.com>
> Cc: serusers(a)lists.iptel.org
> Sent: Mon, 09 Feb 2004 16:22:34 +0100
> Subject: Re: [Serusers] Cancel call Problem
>
>
>>What do mean by "gets hanged"?
>>Watch the SIP call flow using ethereal: Are the CANCEL requests that
>>arive at the proxy forwarded to the other SIP phone?
>>
>>klaus
>>
>>abhati wrote:
>>
>>>Hi All
>>>
>>>My problem is...i have got two phones set 111 and 222. if i make call
>
> from
>
>>>111 and don't pick up 222 and cancel the call, this all is fine. but my
>
> phone
>
>>>gets hanged...both 111 and 222....what shud be done to properly handle
>
> cancel
>
>>>requests.
>>>
>>>i am attaching my ser.cfg file.
>>>
>>>#
>>># $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 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
>>>debug=7
>>>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/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"
>>>
>>># 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"
>>>
>>>loadmodule "/usr/local/lib/ser/modules/domain.so"
>>>loadmodule "/usr/local/lib/ser/modules/call.so"
>>>
>>>modparam("domain", "db_url", "sql://root:root@localhost/ser")
>>>modparam("domain", "db_mode", 1) # Use chaching
>>>modparam("domain", "domain_table", "domain")
>>>modparam("domain", "domain_col", "domain")
>>>
>>>modparam("tm", "fr_inv_timer", 30 )
>>>modparam("registrar", "default_expires", 60)
>>># ----------------- 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 > max_len ) {
>>> 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
>>> record_route();
>>> # loose-route processing
>>> if (loose_route()) {
>>> t_relay();
>>> 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 (is_from_local()) {
>>>
>>> if (method=="REGISTER") {
>>>
>>># Uncomment this if you want to use digest authentication
>>> if (!www_authorize("", "subscriber")) {
>>> www_challenge("", "0");
>>> break;
>>> };
>>> save("location");
>>> break;
>>> };
>>>
>>> # native SIP destinations are handled using our USRLOC DB
>>>
>>>
>>> if (method=="INVITE") {
>>> if(call()){ //written one module for few things works fine
>>> if (!lookup("location")) {
>>> sl_send_reply("404", "Not Found");
>>> break;
>>> };
>>> };
>>> };
>>>
>>> };
>>> # forward to current uri now; use stateful forwarding; that
>>> # works reliably even if we forward from TCP to UDP
>>> if (!t_relay()) {
>>> sl_reply_error();
>>> };
>>>}
>>>
>>>
>>>
>>>.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>Disclaimer
>>>--------------------------------------------------------------------------
>>>This email and any files transmitted with it are confidential
>>>and intended solely for the use of the individual or entity
>>>to whom they are addressed. If you have received this email
>>>in error please notify the system manager. Recipients must
>>>check this email and any attachments for the presence of
>>>viruses before downloading them. Direct Internet /
>>>Primus India accepts no liability for any damage caused by
>>>any virus transmitted by this email.
>>>
>>>
>>>_______________________________________________
>>>Serusers mailing list
>>>serusers(a)lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>
>>>
>>
>>_______________________________________________
>>Serusers mailing list
>>serusers(a)lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>
> ------- End of Original Message -------
>
>
> .
>
>
>
>
>
>
>
> Disclaimer
> --------------------------------------------------------------------------
> This email and any files transmitted with it are confidential
> and intended solely for the use of the individual or entity
> to whom they are addressed. If you have received this email
> in error please notify the system manager. Recipients must
> check this email and any attachments for the presence of
> viruses before downloading them. Direct Internet /
> Primus India accepts no liability for any damage caused by
> any virus transmitted by this email.
>
>
>
Hi all,
My SER server use mysql for auth. These days I find a question.
If an user have a accounts in mysql datebase of SER server, he can avoid system accounting.
For a example, an user have ID: 123456 and he has the password.
When he make a call, he send INVTE like this(just a sample):
INVITE: sip:111111@iptel.org:5060 SIP/2.0
From: "654321"<sip:654321@iptel.org>;tag=xxxxxxx
To: <sip:111111@iptel.org>
............
The Ser server reply 407 (authentication request)
Then user reply: ack and send INVITE with authentication like
INVITE: sip:111111@iptel.org:5060 SIP/2.0
From: "654321"<sip:654321@iptel.org>;tag=xxxxxxx
To: <sip:111111@iptel.org>
Proxy-Authorization: Digest username="123456", realm="iptel.org",nonce="....",uri="123456(a)iptel.org",reponse="............"
(or Proxy-Authorization: Digest username="123456", realm="iptel.org",nonce="....",uri="333333(a)iptel.org",reponse="............" )
............
Then the user pass the authentication using his ID, and he make call using other ID
When register to Ser server, he can use same way to help 401 auth.
I try it on my Ser server and it passed! How to avoid it?
Jimmy
2/9/04
I'm getting this error while starting ser. Can someone plzz tell me what
does this mean? I have downloaded libc.so.6 from the web and installed.
0(19436) ERROR: load_module: could not open module
</usr/lib/ser/modules/mysql.so>: /usr/lib/libmysqlclient.so.10: symbol
errno, version GLIBC_2.0 not defined in file libc.so.6 with link time
reference
-S
