I want do this:
uaA (invite 9200001@B) ---->proxy A (invite 200001@B )--->proxyB
so in proxyA's ser.cfg:
---------------------------
if (uri=~"^sip:9[0-9]*@B") {
strip(1);
t_relay_to_udp( "B", "5060");
break;
};
----------------------------
but proxyB received "sip:9200001" not "sip:200001".
please help me how can I do!
thanks.
Hi All,
I could now configure SER 0.8.14 with FreeRadius and
authentication process goes smoothly for REGISTRATION.
But when i call from one sip UA to other, I don't see
any radius accounting generated.
My Configuration file is as follows:
#
# $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=9 # debug level (cmd line: -dddddddddd)
#fork=no
#log_stderror=yes # (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/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/acc.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_radius.so"
loadmodule "/usr/local/lib/ser/modules/uri_radius.so"
loadmodule
"/usr/local/lib/ser/modules/group_radius.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)
# ------------------------- RADIS AUTHENTICTON
ACCOUNTING RELATED --------------------
modparam("auth_radius", "radius_config",
"/etc/radiusclient/radiusclient.conf")
modparam("acc", "radius_config",
"/etc/radiusclient/radiusclient.conf")
modparam("acc", "radius_flag", 1)
modparam("acc", "radius_missed_flag", 2)
modparam("uri_radius", "radius_config",
"/etc/radiusclient/radiusclient.conf")
modparam("uri_radius", "service_type", 11)
modparam("group_radius", "radius_config",
"/etc/radiusclient/radiusclient.conf")
# ------------------------- 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 (uri==myself) {
if (method=="REGISTER") {
# Uncomment this if you want to use digest
authentication
if (!radius_www_authorize("test1")) {
www_challenge("test1", "0");
break;
};
save("location");
break;
};
# native SIP destinations are handled using our
USRLOC DB
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();
};
}
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Hi,
Is there any possibility that SER requests radius
server to check if a user should be allowed to call a
specific user.
I mean as SER requsts radius upon REGISTRATION, can it
send similar radius request upon INVITE?
I configured SER with the simplest configuration as
explained in Radius How-To.
Probably I need to do something in extra to support
this functionality.
Thanks for your help.
jawad
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
Hello,
I installed serweb and I am having a hard time in having 'add new
contact' to work for adding more destination numbers to direct a call
to.
When I use 'ngrep' to see, I get this:
SIP/2.0 500 FQDN in SDP Media cannot be resolved
Please, help me know what I am doing wrong in adding new contacts.
Thanks in advance.
Regards,
Gilbert
Thanks a lot for your help!
I want really to use strict-routing because I have a UA in rfc3261, and when
he make a call, he put the tag "LR" in the route fields of the ACK, and then
the call is cut after 20s.
Probably because my gateway Cisco (to PSTN) is only according to use RFC
2543.
Thats why I want the UA capably to work with IPTEL in strict routing.
I have the same problem with an ATA Cisco, but I have put an old firmware,
and that's work very good. (CODE 3.1.1 (LR) >> CODE 3.1.0 (NO LR)).
I have take the module rr_mod.c and after, how can I compile the module
rr???
Best Regards,
Nicolas RUIZ.
-----Message d'origine-----
De : Franz Edler [mailto:franz.edler@utanet.at]
Envoyé : jeudi 9 septembre 2004 06:09
À : 'Martin Koenig [toplink-plannet GmbH]'; 'RUIZ Nicolas'
Cc : serusers(a)lists.iptel.org
Objet : RE: [Serusers] Please help : how to disable losse routing ???
From: Martin Koenig [toplink-plannet GmbH] Sent: Wednesday, September 08,
> this is not an SER problem. Loose routing is basically done in the end
> devices. All you can control on the server is whether the server should be
> in the signalling proxy chain (record_route()) and whether you want to
> process route-header-fields (loose_route()) or forward to the final
> destinanation directly (t_relay() without loose_route()).
Sorry, this is not correct. The routing mechanism (loose or strict) has to
be followed by SIP proxies. Look at RFC 3261 para 16.6 step 6 where the
strict routing behavior is defined:
"If the copy contains a Route header field, the proxy MUST inspect the URI
in its first value. If that URI does not contain an lr parameter, the proxy
MUST ..."
But I expect that this behaviour is implemented in SER. In previous versions
of SER there was the possibility to force SER to do only strict routing.
This has been disabled now and in my previous comment I looked into the
documentation which is not updated accordingly and still mentions the
function strict_route(). But looking into the code of rr_mod.c you can read
as a comment:
"I do not want people to use strict routing so it is disabled by default,
you should always use loose routing, if you really need strict routing then
you can replace the last zeroes with REQUEST_ROUTE to enable strict_route
and record_route_strict. Don't do that unless you know what you are really
doing!"
> As loose routing is the standard routing procedure as defined in RFC3261,
> strict routing is obsolete.
To be precise: strict routing is deprecated. If you have a strict router in
a SIP router chain the proxy forwarding to a strict router has to be aware
of this fact as mentioned above.
From: RUIZ Nicolas Sent: Wednesday, September 08, 2004 9:10 PM
> When I put strict_route at the place of loose_route, I have an error.
> (Module missing). Ser version is : 0.8.12.
> What can I modify to apply strict routing only?
Sorry I did not check that this previous function has been eliminated. But
following the comment in rr_mod.c there is a possibility to force SER into
strict routing (see above) behavior. Look into the code. Than you also have
to use "record_route_strict" instead of "record_route".
But I have heavy doubts that this will help your problems. Do you really
know why you want to fall back to a deprecated routing behavior?
Franz
Hello Nicolas,
another mail from me, one more thing you should verify. Here you have ngrep
from my proxy1 that is directly connected to the Cisco 7960. I stripped
everything unimportant from this to enhance readability:
#
U 2004/09/16 18:57:34.088150 proxy1:5060 -> cisco7960:5070
SIP/2.0 200 OK.
Contact: <sip:07154802860@gw1;user=phone>.
Record-Route: <sip:+497154802860@proxy3:5070;lr>,
<sip:+497154802860@proxy2:5070;lr>,
<sip:07154802860@proxy1;lr>.
The Cisco 7960 receives the OK message from proxy1. It contains the Contact
field and the Record Route Fields for the proxy chain to the gateway. Note
that all Record Route Fields contain the ;lr parameter (or ;lr=on in your
case).
The next step is the ACK from the Cisco 7960.
#
U 2004/09/16 18:57:34.298054 cisco7960:5070 -> proxy1:5060
ACK sip:07154802860@proxy1:5060;lr SIP/2.0.
Route: <sip:+497154802860@proxy2:5070;lr>,
<sip:+497154802860@proxy3:5070;lr>,
<sip:07154802860@gw1:5060;user=phone>.
.
As you can see, it does not follow the Loose Route definitions. The ACK
Request-URI does not equal the Contact from the preceeding 200 OK. Instead
it contains the first hop (thus the last entry) of the Record Route Field
from the 200 OK. As you can also see, it added the Contact Field from 200 OK
at the End of the Route Field, without the ;lr parameter! This is absolutely
fine behaviour. Now watch what happens when the proxy processes this message
with loose_route():
#
U 2004/09/16 18:57:34.301417 proxy1:5060 -> proxy2:5070
ACK sip:+497154802860@gw1:5060;user=phone SIP/2.0.
Route: <sip:+497154802860@proxy2:5070;lr>,
<sip:+497154802860@proxy3:5070;lr>.
.
The proxy detects that the last entry of the Route Field does not contain
the ;lr parameter, so it sets this last entry as Request-URI for the ACK
message to the next proxy and removes this from the Route Field. From now on
we have perfectly fine Loose Routing, even though the Cisco does not care
about it. It should not matter for the further processing of the request in
the proxy chain.
You have to debug your messaging chain at all devices to find out what is
going wrong. I really can't see the Cause of the error. Maybe it's related
to the NAT-traversal you are performing.
Regards,
Martin
> -----Original Message-----
> From: Nicolas RUIZ [mailto:nruiz@vivaction.com]
> Sent: Thursday, September 16, 2004 5:05 PM
> To: 'Martin Koenig'
> Cc: jan(a)iptel.org
> Subject: RE: [Serusers] Please help : how to disable losse routing ???
>
> thanks for your help,
>
> 80.118.128.1 : GATEWAY CISCO AS5300
> 80.118.128.5 : SER IPTEL
> 192.168.254.7 : IP@ PRIVATE AUDICODES UA
> 192.168.254.12 : IP@ PRIVATE CISCO IPPHONE UA
>
>
>
> -----Message d'origine-----
> De : Martin Koenig [mailto:martin.koenig@toplink-plannet.de]
> Envoyé : jeudi 16 septembre 2004 16:59
> À : nruiz(a)vivaction.com
> Objet : RE: [Serusers] Please help : how to disable losse routing ???
>
>
> Hi Nicolas,
>
> Ah, please give me again the specs of which IP is which device.
>
> Thanks,
> Martin
>
> > -----Original Message-----
> > From: Nicolas RUIZ [mailto:nruiz@vivaction.com]
> > Sent: Thursday, September 16, 2004 4:50 PM
> > To: 'Martin Koenig'
> > Cc: jan(a)iptel.org
> > Subject: RE: [Serusers] Please help : how to disable losse
> routing ???
> >
> > No i dont think so.
> > I join ETHEREAL DUMP, look at the line : 8, if is possible.
> >
> > thanks a lot
> >
> > -----Message d'origine-----
> > De : Martin Koenig [mailto:martin.koenig@toplink-plannet.de]
> > Envoyé : jeudi 16 septembre 2004 16:41
> > À : nruiz(a)vivaction.com
> > Objet : RE: [Serusers] Please help : how to disable losse
> routing ???
> >
> >
> > Are you doing any transformation of the userpart of the sip
> > uri (the part in
> > front of the @) at the proxy server? For me this was the
> > problem. Right now,
> > i really can't figure out the problem.
> >
> > > -----Original Message-----
> > > From: Nicolas RUIZ [mailto:nruiz@vivaction.com]
> > > Sent: Thursday, September 16, 2004 2:47 PM
> > > To: 'Jan Janak'; 'Martin Koenig'
> > > Cc: serusers(a)lists.iptel.org
> > > Subject: RE: [Serusers] Please help : how to disable losse
> > routing ???
> > >
> > > If I have a Cisco Ip phone 7940 with the last code (Loose
> > > routing : RFC
> > > 3261), a proxy registar Linux IPTEL ser (RFC 3261) and a
> > > Gateway Cisco
> > > AS5300 (IOS Code 12.3(6a)).
> > > And I have see that the IOS code of my gateway AS5300 is not
> > > according to
> > > RFC3261.
> > >
> > > And my problem, is :
> > >
> > > My cisco IPPHONE with Loose routing mode, send the invite to
> > > the proxy, and
> > > the proxy send the invite to the gateway.
> > > But when the IPPHONE send the ACK, he send with this
> request line :
> > > REQUEST-LINE : ACK sip:0675313859@80.118.128.1:5060 SIP/2.0
> > >
> > > And the IP@ is my gateway cisco, and i think, with my AS, i
> > > cannot USE SIP
> > > RFC 3261??? YES OR NOT???
> > >
> > > And that, i want to set iptel to do only strict routing.
> > >
> > > thanks a lot for your help.
> > >
> > > Nicolas RUIZ
> > >
> > > CONF IPTEL SER:
> > >
> > > #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;
> > > };
> > >
> > >
> > > -----Message d'origine-----
> > > De : Jan Janak [mailto:jan@iptel.org]
> > > Envoyé : jeudi 16 septembre 2004 11:03
> > > A : Martin Koenig
> > > Cc : nruiz(a)vivaction.com; serusers(a)lists.iptel.org
> > > Objet : Re: [Serusers] Please help : how to disable losse
> > routing ???
> > >
> > >
> > > I am using 7960 myself and do not have any problems, please
> > send ngrep
> > > dumps.
> > >
> > > Jan.
> > >
> > > On 16-09 10:48, Martin Koenig wrote:
> > > > I'm seeing some strange loose routing behaviour with my
> > > testing Cisco 7960
> > > > phone. I'm trying to put ngreps on the list as soon as i
> > > have the time.
> > > > Maybe this is a cisco-specific problem?
> > > >
> > > > Regards,
> > > > Martin
> > > >
> > > > > -----Original Message-----
> > > > > From: Nicolas RUIZ [mailto:nruiz@vivaction.com]
> > > > > Sent: Tuesday, September 14, 2004 12:03 PM
> > > > > To: 'Jan Janak'
> > > > > Cc: 'Jiri Kuthan'; franz.edler(a)utanet.at; 'Martin Koenig
> > > > > [toplink-plannet GmbH]'; serusers(a)lists.iptel.org
> > > > > Subject: RE: [Serusers] Please help : how to disable
> > > losse routing ???
> > > > >
> > > > > OK,
> > > > >
> > > > > Thanks a lot for your support
> > > > >
> > > > > Best regards
> > > > >
> > > > > Nicolas RUIZ
> > > > > VIVACTION
> > > > > FRANCE, PARIS
> > > > >
> > > > > -----Message d'origine-----
> > > > > De : Jan Janak [mailto:jan@iptel.org]
> > > > > Envoyé : mardi 14 septembre 2004 11:44
> > > > > A : Nicolas RUIZ
> > > > > Cc : 'Jiri Kuthan'; franz.edler(a)utanet.at; 'Martin Koenig
> > > > > [toplink-plannet
> > > > > GmbH]'; serusers(a)lists.iptel.org
> > > > > Objet : Re: [Serusers] Please help : how to disable losse
> > > routing ???
> > > > >
> > > > >
> > > > > On 13-09 16:41, Nicolas RUIZ wrote:
> > > > > > Thanks for your help,
> > > > > >
> > > > > > That's right, My gateway cisco is not according to RFC
> > > > > 3261, and that's
> > > > > why
> > > > > > , I want to use only strict-routing.
> > > > >
> > > > > Loose routing is backwards compatible, it should work
> > > even if the
> > > > > gateway does not support loose routing. The problem must be
> > > > > somewhere
> > > > > else, presumably one of the end-points is broken.
> > > > >
> > > > > > And if I want to use "record_route_strict", I have to
> > > > > rebuild the module
> > > > > rr
> > > > > > or not?
> > > > >
> > > > > Yes.
> > > > >
> > > > > Jan.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > Serusers mailing list
> > > > serusers(a)lists.iptel.org
> > > > http://lists.iptel.org/mailman/listinfo/serusers
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
>
>
Cisco will have for this autumn 2621XM the first platform to support
this translation, check Cisco TAC for updates.
Otherwise try asterisk, it currently has still an audio bug in H323
code (no audio at all) but the CVS from 28-th of May works fine for
H323/SIP. There are some missing features in Q931 stack like Nature of
address but you can tweak the missing parts in the h323 channel.
Another option that I know of is SIPQuest which supports only G711.
Regards,
Adrian
>>>>>>>>>>>>>>
13704 Research Blvd. Building O-Suite 4
Austin, TX 78750
Tel: 512-257-2274 Ex: 115
Hi,
Anybody has any idea where I can find sip to h323 converter?
Will cisco 5300 do?
Thanks
CM
Which version of PHP did you use?
-----Original Message-----
From: Razvan Nemesiu [mailto:forum@netconnect.ro]
Sent: 16 September 2004 16:49
To: serusers(a)lists.iptel.org
Subject: [Serusers] Serweb
Hi..I hust installed sereweb..everything is fine..i can connect to the
admin page but it seems that it needs a username and a password ...the
problem is that I don't know the username and password to login..how can I
find them ?
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
**************************************************************************
Disclaimer
This email transmission is confidential and intended solely for the person
or organisation to whom it is addressed. If you are not the intended
recipient, you must not copy, distribute or disseminate the information, or
take any action in reliance of it. Any views expressed in this message are
those of the individual sender, except where the sender specifically states
them to be the views of any organisation or employer. If you have received
this message in error, do not open any attachment but please notify the
sender (above) and delete this message from your system. Please rely on your
own virus check. Although all outbound mail is checked for viruses, no
responsibility is taken by the sender for any damage rising out of any bug
or virus infection.
**************************************************************************