Hi guys,
I've been experiencing some troubles with carrier's that are using
Nextone (www.nextone.com).
I could place calls through Nextone but no longer then 1 minute, between 48 and
53 seconds the call is dropped with a BYE sent by Nextone.
I've been using another carriers using Cisco and Quintum without problems.
Does some one experimenting this problem?
I'm using SER 0.8.14.
Thanks in advance.
--
============================================
Rodrigo P. Telles <telles(a)devel.it>
IVOZ # 1009
Project Manager
Devel-IT - http://www.devel.it
Bestcom Group
============================================
Hi all,
I've extended Juha's LCR module to support prefixes for gateways.
We use it for prefix-based setting of the bearer capability on our gateways.
Note that the attached patch is against Juha's backport for rel_0_9_0 at
http://tutpro.com/tmp/lcr-0.9.0.tgz because we've no CVS-HEAD running here.
It works as follows:
In the new table gw_cap you can define capabilities and their
corresponding prefix, like:
mysql root@ser> select * from gw_cap;
+--------+-----------+------------+----------------------+
| cap_id | cap_value | cap_prefix | cap_description |
+--------+-----------+------------+----------------------+
| 1 | 1 | | default phone trunk |
| 2 | 1 | 01 | prefixed phone trunk |
| 3 | 2 | 02 | prefixed fax trunk |
+--------+-----------+------------+----------------------+
3 rows in set (0.00 sec)
In this case the cap_value of "1" means phone-capabilites, "2" means
fax-capabilities.
The table gw_grp is extended with an additional column cap_id.
mysql root@ser> select * from gw_grp;
+--------+-------------------------+--------+
| grp_id | grp_name | cap_id |
+--------+-------------------------+--------+
| 1 | priority_1_phone | 1 |
| 2 | priority_1_phone_prefix | 2 |
| 3 | priority_1_fax_prefix | 3 |
| 4 | priority_2_phone | 1 |
| 5 | priority_2_phone_prefix | 2 |
| 6 | priority_3_phone_prefix | 2 |
+--------+-------------------------+--------+
6 rows in set (0.00 sec)
In ser.cfg you can then load the gateways for example like this if you
use different gateways/trunks for phone and fax:
if( /* phone call */)
{
if(!load_gws("1"))
{
sl_send_reply("500",
"Internal server error, unable to load phone gateways");
break;
}
}
else /* fax call */
{
if(!load_gws("2"))
{
sl_send_reply("500",
"Internal server error, unable to load fax gateways");
break;
}
}
The usage of next_gw() is as usual.
Also note that the gateway selection algorithm changes when you use
load_gws("x") instead of load_gws(): The latter always selects the
gateways with highest priority first. The new one uses the priority
value as weight, so also gateways with lower priority are chosen. Hit
ratio for 5000 rounds is as follows:
priority-1-gw-1: 35%
priority-2-gw-1: 14%
priority-2-gw-3: 14%
priority-2-gw-2: 14%
priority-2-gw-4: 14%
priority-3-gw-1: 9%
Looking forward for comments/fixes/improvements,
Andy
-----Original Message-----
From: jimmy [mailto:jimmy_huang@uni.com.tw]
Sent: Tuesday, March 15, 2005 10:01 AM
To: 'rrisco(a)millicom.net.pe'
Subject: RE: [Serusers] calls between UA´s behind same NAT using
nathelper/rtpproxy
Hi Rafael:
It seems has two way to meet your requirement
(1)use external script
http://lists.iptel.org/pipermail/serusers/2005-February/015477.html
(2)use avpops module
http://www.voice-system.ro/docs/avpops/
Hope it's useful ...
Jimmy
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On
Behalf Of Rafael J. Risco G.V.
Sent: Tuesday, March 15, 2005 2:22 AM
To: serusers(a)lists.iptel.org
Subject: [Serusers] calls between UA´s behind same NAT using
nathelper/rtpproxy
Hi
I would like to know if its possible to comunicate SIP Clients betwen
them when they are behind the same nat, I am using
Nathelper/RTPProxy...
thanks
Rafael
--
rrgv
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Hi,
I'm using eyebeam and xten lite with a Fedora core 3 and ser-0.9.1 from
csv...
The ser server in main office serving branch offices connected with
frame relay 64kb.
It's working fine (not yet tested conference) and presence is working
only when I instruct eyebeam to use peer-to-peer presence. When I try to
use Presence Agent mode presence does not work, can someone help me...?
My ser.cfg
#
# $Id: ser.cfg,v 1.25 2004/11/30 16:28:24 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
alias=192.168.130.209
listen=192.168.130.209
fifo="/tmp/ser_fifo" fifo_db_url="mysql://ser:heslo@localhost/ser"
# ------------------ 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/pa.so"
loadmodule "/usr/local/lib/ser/modules/uri.so"
loadmodule "/usr/local/lib/ser/modules/uri_db.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)
modparam("usrloc", "db_url", "mysql://ser:heslo@localhost/ser")
modparam("usrloc", "use_domain", 1)
modparam("usrloc", "desc_time_order", 1)
# -- 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)
# -- pa params
modparam("pa", "db_url", "mysql:ser:heslo@localhost/ser")
modparam("pa", "default_expires",50)
modparam("pa", "pa_domain", "192.168.130.209")
# -- registrar params --
modparam("registrar", "use_domain", 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
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("192.168.130.209", "subscriber")) {
www_challenge("192.168.130.209", "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();
};
}
DidierH.
> -----Original Message-----
> From: Jamey Hicks [mailto:jamey.hicks@hp.com]
> Sent: Tue 1/11/2005 11:41 PM
> To: Helge Waastad
> Cc: serusers(a)lists.iptel.org
> Subject: Re: [Serusers] ser-0.9.0 and PA clients
Helge Waastad wrote:
>> Hello,
>> I've started to use the 0.9.0 release and to me it seems to work as a
>> charm :-)
>>
>> However does anybody know which SIP clients which is compliant for
the PA?
>> I'm using kphone and it works fine, but I would like to try out some
>> for use on Microsoft?
>> Messenger 5.0 does not work.
> Eyebeam from xten.com seems to be the farthest along in terms of
> implementing SIMPLE presence support, according to their website. I
> know Xten was testing against the SER PA this fall. That being said,
> testing Eyebeam against SER 0.9 is on my todo list for this week. I
> just need to set up a SER 0.9 PA on the same side of the HP firewall
as
> my Windows box.
>> Jamey
This mail has been scanned for known virus like activity on behalf of GALANA DISTRIBUTION PETROLIERE S.A. This E-mail is privileged, confidential and intended solely for the addressee(s).Any unauthorised dissemination or copying of this E-mail, and any use or disclosure of any information contained in it, is strictly prohibited and may be illegal. If you have received this E-mail in error please notify the sender immediately and delete it from your system. GALANA DISTRIBUTION PETROLIERE S.A. does not accept any liability for any errors, omissions, interceptions, corrupted mail, lost communications or late delivery which may arise as a result of this E-mail or for any virus that may be contained in it. Any views or opinions expressed in this E-mail are solely those of the author and do not necessarily reflect those of GALANA DISTRIBUTION PETROLIERE S.A.
Ce courriel a fait l'objet, par GALANA DISTRIBUTION PETROLIERE S.A. de verifications le protegeant des virus connus. Ce courriel est personnel, confidentiel et adresse exclusivement a son ou ses destinataire(s). Toute diffusion ou copie non autorisee ainsi que l'usage partiel ou total de son contenu est strictement interdit et peut-etre illegal. Si vous avez recu ce courriel par erreur, merci d'en informer son emetteur et de l'effacer de votre ordinateur. GALANA DISTRIBUTION PETROLIERE S.A. refuse toutes responsabilites liees aux erreurs, omissions, interceptions, deformations, communications perdues, ou retards de transmissions dont ce courriel pourrait etre l'objet ou a l'origine ainsi que des virus qu'il pourrait contenir. Les avis ou opinions exprimes dans ce courriel refletent exclusivement ceux de son auteur et non ceux de GALANA DISTRIBUTION PETROLIERE S.A.
Hi all,
I use ser 0.10.99-dev5 (i386/linux) with the latest
Ser web from cvs.
according to mysql log r_uri is not set in table silo
?!
Ser don't return error and message is stored in table
silo.
I need help to fix that problem
Harry
050322 11:48:07 114 Connect ser@localhost on
114 Init DB ser
114 Query select val from
active_sessions where sid =
'fd33d3dd6e4783743b30428e0942f0b4' and name =
'phplib_Session'
114 Query select val from
active_sessions where sid =
'fd33d3dd6e4783743b30428e0942f0b4' and name =
'phplib_Session'
88 Query insert into silo
(dst_addr,src_addr,username,domain,body,exp_time,inc_time
) values ('sip:alice@home.net','sip:alice@home.net','alice','home.net','helo\r\n',1111747687,1111488487)
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
Hi,
I don't know if anyone has experienced this. The ser stops getting any
packets, ser log shows no activity. When I do "netstat -an", I got this,
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 261580 0 80.1.2.3:5060 0.0.0.0:*
udp 85224 0 0.0.0.0:35940 0.0.0.0:*
udp 0 0 0.0.0.0:35941 0.0.0.0:*
udp 47704 0 0.0.0.0:35942 0.0.0.0:*
udp 0 0 0.0.0.0:35943 0.0.0.0:*
I restarted ser several times, didn't help. So I restarted rtpproxy. Ser
started processing packets and the recv-q drops to 0. I wonder what could
cause recv-Q accumulating packets. Everything was running fine without any
problem for a long time. I haven't made any change to either ser or rtpproxy
recently.
Any suggestions?
Thanks,
Richard
Hi, All
Does any one use video conference in SER+rtpproxy.
I use Windows Messenger and It's ok without rtpproxy.
But, when my UA behide NAT, Video can not work.
Should I do something in vedio package??
Best Regards,
Nilus
Has anyone ever user SER with Oracle or developed an Oracle plugin for use with SER?
Doug
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
Thanks for the reponse, I gathered that much. My question is how long
before the contact gets "removed"? It's late morning now and it's still
there :-)
-----Original Message-----
From: Marian Dumitru [mailto:marian.dumitru@voice-sistem.ro]
Sent: Saturday, March 26, 2005 5:37 AM
To: Matt Schulte
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] usrloc and replication
Hi Matt,
After expiration an before being removed, the contact are still kept in
ZOMBIE state - you can see the state in DB changes.
Best regards,
Marian
Matt Schulte wrote:
> Ok, I'm using usrloc db_mode 2, I understand the timer checks every 60
> seconds default to see who should be expired and all. What I don't
> understand is why I keep getting these messages:
>
> Keeping binding '+13142664004','sip:s@69.29.57.253:3105' for
> replication
>
> This contact expired nonetheless and should be removed, is there
> something I'm missing?
>
> +--------------+--------------------------------------+---------------
> +--------------+--------------------------------------+--
> ----+
> | username | contact | expires
> |
> +--------------+--------------------------------------+---------------
> +--------------+--------------------------------------+--
> ----+
> | +13142664004 | sip:s@69.29.57.253:3105 | 2005-03-26
> 00:42:35 |
> | +13142664004 | sip:s@69.29.57.253:3118 | 2005-03-26
> 01:24:58 |
> +--------------+--------------------------------------+---------------
> +--------------+--------------------------------------+--
> ----+
--
Voice System
http://www.voice-system.ro
Hello list.
I have a question about reliability in SER. Suppose that for
certain reason, the process "ser" fails, and therefore the SIP Server is
down. Is there a way to keep trace of the "ser" process status?? and if the
process is not running start a script to restart the process. I know that
maybe the "crond" command could be useful for this purpose. Does someone
have any clue about this? Or maybe SER has his own "crond" module or
something.?
I really need and advice about this issue.
Thanks in advance
Regards,
Ricardo Martinez Ogalde.-
