[Serusers] Remote Party ID
Alan Litster
alitster at telcoelectronics.co.uk
Tue Jul 13 11:30:54 CEST 2004
I believe so as by default remote-party-id is enabled. It only appears in
the config when you use the no form of the command.
As I said previously, the SIPUA may be inserting it's own Remote-Party-ID.
SER will not overwrite this, I think it appends it to the header but the
gateway will only use the first one it comes across - the incorrect one. It
may be the case of having SER remove the Remote-Party-ID header before
appending your own. Have you tried running a trace on the call?
Remote-Party-ID: "0123456789"
<sip:0123456789 at sip.mydomain.com>;party=calling;id-type=subscriber;screen=ye
s
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122
t/122t13/ftsipext.htm
Regards,
Alan
-----Original Message-----
From: Charles Galea [mailto:charles.galea at maltacom.com]
Sent: 13 July 2004 10:00
To: Alan Litster; SER Mailing List
Subject: Re: [Serusers] Remote Party ID
Thanks once again Alan.
Yes that's exactly what I did, but still cannot get it to work. One thing
that I noted is that although I am enabling the remote-party-id under
sip-ua, this does not show in the config file. Is this normal?
Regards,
Charles
----- Original Message -----
From: "Alan Litster" <alitster at telcoelectronics.co.uk>
To: "SER Mailing List" <serusers at lists.iptel.org>
Cc: "Charles Galea" <charles.galea at maltacom.com>
Sent: Tuesday, July 13, 2004 10:52
Subject: RE: [Serusers] Remote Party ID
> If I understand you correctly you want the 3600 to handle the remote party
> id field?
>
> I'm not familiar with the 3600 but I assume it is identical to a AS5300.
On
> that to enable processing of the remote party ID field, under the sip-ua
> configuration mode you simply have to set 'remote-party-id'.
>
> Regards,
>
> Alan
>
> -----Original Message-----
> From: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org]On
> Behalf Of Charles Galea
> Sent: 13 July 2004 06:49
> To: iancu at fokus.fraunhofer.de
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] Remote Party ID
>
>
> Thanks a lot,
>
> i have included an authentication check before append_rpid_hf() and now it
> is working fine. Now I am trying to figure out why my 3600 gateway is
still
> not sending the calling party field in the setup message.
>
> Regards,
>
> Charles
>
>
> ----- Original Message -----
> From: "Bogdan-Andrei IANCU" <iancu at fokus.fraunhofer.de>
> To: "Charles Galea" <charles.galea at maltacom.com>
> Cc: <serusers at lists.iptel.org>; "'Andrew Caruana'" <andrew.caruana at maltacom.com>
> Sent: Monday, July 12, 2004 13:58
> Subject: Re: [Serusers] Remote Party ID
>
>
> > rpid is fetched from db during an authentication check. so, if you don't
> > have any authentication before append_rpid_hf(), we will not have any
> rpid.
> >
> > bogdan
> >
> >
> > Charles Galea wrote:
> >
> > >
> > > We have downloaded the latest ser software from cvs in order to
> > > support appending of remote party id while using mysql as the ser
> > > database.
> > > After compiling and installing the ser software we included the auth
> > > and auth_db parameters and also the append_rpid_hf() function in our
> > > ser.cfg file as shown below.
> > >
> > > SER server starts and registration is successfull however when
> > > forwarding to the pstn gateway, ser will not append the remote party
> > > id header, even if the rpid and uri columns in mysql database are
> > > populated accordingly using the serctl add rpid command. Calls are
> > > also successfull however the gateway will not include the calling
> > > party number in the setup message because the rpid header is missing.
> > >
> > >
> > > Any ideas please?
> > >
> > > Thanks
> > >
> > > Charles and Andrew
> > >
> > >
> > >
> > > # ----------- 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 ----------------------------------
> > >
> > > loadmodule "/our_downloads/sip_router/modules/mysql/mysql.so"
> > > #loadmodule "//lib/ser/modules/mysql.so"
> > >
> > > loadmodule "//lib/ser/modules/sl.so"
> > > loadmodule "//lib/ser/modules/tm.so"
> > > loadmodule "//lib/ser/modules/rr.so"
> > > loadmodule "//lib/ser/modules/maxfwd.so"
> > > loadmodule "//lib/ser/modules/usrloc.so"
> > > loadmodule "//lib/ser/modules/registrar.so"
> > > loadmodule "//lib/ser/modules/textops.so"
> > >
> > > # Uncomment this if you want digest authentication
> > > # mysql.so must be loaded !
> > > loadmodule "//lib/ser/modules/auth.so"
> > > loadmodule "//lib/ser/modules/auth_db.so"
> > >
> > >
> > > #loadmodule "//lib/ser/modules/acc.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", 1)
> > >
> > >
> > >
> > > # -- auth params --
> > >
> > >
> > > modparam("auth_db", "use_rpid", 1)
> > > modparam("auth_db", "rpid_column", "rpid")
> > > modparam("auth", "rpid_prefix", "<sip:")
> > > modparam("auth", "rpid_suffix",
> > > "@testphone.com>:party=calling;screen=no;privacy=off")
> > >
> > >
> > >
> > >
> > > # 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 (uri=~"testphone.com") {
> > > lookup("aliases");
> > > if (method=="REGISTER") {
> > >
> > > #Uncomment this if you want to use digest authentication
> > > if (!www_authorize("testphone.com", "subscriber")) {
> > > www_challenge("testphone.com", "0");
> > > append_rpid_hf();
> > > break;
> > > };
> > >
> > >
> > >
> > > save("location");
> > > break;
> > > };
> > >
> > >
> > >
> > > if (uri=~"^sip:21") {
> > > append_rpid_hf();
> > > forward(a valid ip address for the gateway was
> > > inserted here);
> > > break;
> > > }
> > >
> > > if (uri=~"^sip:123") {
> > > forward(a valid ip address for the gareway was
> > > inserted here);
> > > 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();
> > > };
> > >
> > >
> > > }
> > >
> > >
> > >
> >
>------------------------------------------------------------------------
> > >
> > >_______________________________________________
> > >Serusers mailing list
> > >serusers at lists.iptel.org
> > >http://lists.iptel.org/mailman/listinfo/serusers
> > >
> > >
> >
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
> --------------------------------------------------------------------------
-----------------------------
> This email, and any files transmitted with it, is copyright and may
contain confidential information.
> The contents are intended for the use of the addressee(s) only.
> Unauthorized use may be unlawful.
> If you receive this email by mistake, please advise sender immediately.
> The views of the author may not necessarily constitute the views of Telco
Electronics Limited.
> Nothing in this mail shall bind Telco Electronics Limited in any contract
or obligation.
>
> Telco Electronics Limited
> 6-8 Oxford Court
> Brackley
> Northants
> NN13 7XY
>
> Tel 07000 701999
> Fax 07000 701777
-------------------------------------------------------------------------------------------------------
This email, and any files transmitted with it, is copyright and may contain confidential information.
The contents are intended for the use of the addressee(s) only.
Unauthorized use may be unlawful.
If you receive this email by mistake, please advise sender immediately.
The views of the author may not necessarily constitute the views of Telco Electronics Limited.
Nothing in this mail shall bind Telco Electronics Limited in any contract or obligation.
Telco Electronics Limited
6-8 Oxford Court
Brackley
Northants
NN13 7XY
Tel 07000 701999
Fax 07000 701777
More information about the sr-users
mailing list