Hi,
I am trying to configure openser + freeradius for authentication &
accounting.
I have my freeradius configured with openldap and it's working successfully.
tested with
radclient -f digest 127.0.0.1:1812 auth testing123
results are successfull.
However I cannot get it to work with openser. I see nothing happening in my
"/usr/sbin/radius -X" output coming from openser when i try to register.
My enviroment was tested on Fedora 8 and Fedora 9 both with rpm's and same
results.
auth_radius:radius_authorize_sterman: rc_auth failed
no output is seen in my /usr/sbin/radius -X
Below please find my openser.cfg & radiusclient.conf & servers
######## radiusclient.conf
# General settings
# specify which authentication comes first respectively which
# authentication is used. possible values are: "radius" and "local".
# if you specify "radius,local" then the RADIUS server is asked
# first then the local one. if only one keyword is specified only
# this server is asked.
auth_order radius,local
# maximum login tries a user has
login_tries 4
# timeout for all login tries
# if this time is exceeded the user is kicked out
login_timeout 60
# name of the nologin file which when it exists disables logins.
# it may be extended by the ttyname which will result in
# a terminal specific lock (e.g. /etc/nologin.ttyS2 will disable
# logins on /dev/ttyS2)
nologin /etc/nologin
# name of the issue file. it's only display when no username is passed
# on the radlogin command line
issue /etc/radiusclient-ng/issue
# RADIUS settings
# RADIUS server to use for authentication requests. this config
# item can appear more then one time. if multiple servers are
# defined they are tried in a round robin fashion if one
# server is not answering.
# optionally you can specify a the port number on which is remote
# RADIUS listens separated by a colon from the hostname. if
# no port is specified /etc/services is consulted of the radius
# service. if this fails also a compiled in default is used.
authserver 127.0.0.1
authserver 10.0.0.10
authserver localhost
# RADIUS server to use for accouting requests. All that I
# said for authserver applies, too.
#
acctserver 127.0.0.1:1813
# file holding shared secrets used for the communication
# between the RADIUS client and server
servers /etc/radiusclient-ng/servers
# dictionary of allowed attributes and values
# just like in the normal RADIUS distributions
#dictionary /usr/share/radiusclient-ng/dictionary
dictionary /etc/radiusclient-ng/dictionary.openser
# program to call for a RADIUS authenticated login
login_radius /usr/sbin/login.radius
# file which holds sequence number for communication with the
# RADIUS server
seqfile /var/run/radius.seq
# file which specifies mapping between ttyname and NAS-Port attribute
mapfile /etc/radiusclient-ng/port-id-map
# default authentication realm to append to all usernames if no
# realm was explicitly specified by the user
# the radiusd directly form Livingston doesnt use any realms, so leave
# it blank then
default_realm
# time to wait for a reply from the RADIUS server
radius_timeout 10
# resend request this many times before trying the next server
radius_retries 3
# local address from which radius packets have to be sent
bindaddr *
# LOCAL settings
# program to execute for local login
# it must support the -f flag for preauthenticated login
login_local /bin/login
########################################################
#/etc/radiusclient-ng/servers
#Server Name or Client/Server pair Key
#---------------- ---------------
#portmaster.elemental.net hardlyasecret
#portmaster2.elemental.net donttellanyone
localhost testing123
127.0.0.1 testing123
10.0.0.10 testing123
#######################################################
##########openser.cfg
# -- rr params --
debug=3
log_stderror=yes
log_facility=LOG_LOCAL0
fork=yes
children=4
port=5060
# ------------------ module loading ----------------------------------
mpath="/usr/lib/openser/modules/"
loadmodule "mysql.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "avpops.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "xlog.so"
loadmodule "uri.so"
loadmodule "auth.so"
loadmodule "auth_radius.so"
loadmodule "mi_fifo.so"
modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
# ----------------- setting module-specific parameters ---------------
# -- usrloc params --
modparam("usrloc","db_url","mysql://openser:openser@localhost/openser")
modparam("usrloc", "db_mode", 2)
# -- acc params --
modparam("auth_radius","radius_config","/etc/radiusclient-ng/radiusclient.conf")
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)
# ------------------------- request routing logic -------------------
# main routing logic
route{
# authenticate registers
if (method=="REGISTER") {
if (!radius_www_authorize("")) {
www_challenge("", "0");
exit;
};
save("location");
exit;
};
route(1);
}
# generic forward
route[1] {
# send it out now; use stateful forwarding as it works reliably
# even for UDP2TCP
if (!t_relay()) {
sl_reply_error();
};
exit;
}
#
Thanks for your help
SJX
Like i already took this as a benefit of doubt.
They used G711u for a California calls and it was successful and used G711u NSE to the NewYork and the call failed with 484.
so i asked them to use the G711u for NewYork and not G711u NSE still the call failed with G711u (excluding NSE).
I enquired with the provider already that they support G711u but not G711u NSE.
but still with G711u they failed and that too with 484.
thats really wierd and i am stuck up in the middle.
KC
LetMeKnow <sunkara.raviprakash.feb14(a)gmail.com> wrote: Hi Chris,
This Problem is happened to me,
when i used EyeBeam---> OpenSER--> Asterisk as PSTN Gateway, Asterisk is seems to send 484, this is due to the imcompartable of the Codecs in Eyebean and Asterisk gateway...........................................
Check out.... logs from these
customer signaling ip-addr - 23.21.76.23
customer media ip-addr - 231.43.25.1
supplier media ip-addr - 43.25.32.85
supplier signaling ip-addr - 13.45.213.245
my signaling ip-addr - 123.123.1.234
supplier have producing this
t SIP headers and found no issues. Also, when i use the same called number and make the calls through the same provider it works from my end with 200 OK. its really interesting and seems to be some issues with the headers.
I am using openser and following are the logs. sorry - its too long, but i need someones help to figure out whats going on really.
Also, following is the definition for the ips and telephone numbers.
FROM number - 17592034561
TO number - 19846572302
customer signaling ip-addr - 23.21.76.23
customer media ip-addr - 231.43.25.1
supplier media ip-addr - 43.25.32.85
supplier signaling ip-addr - 13.45.213.245
my signaling ip-addr - 123.123.1.234
---------------------------------------------------------------------
logs as below;
Y#HE& _ d E pl@ 7 ! @ V)ÇèNÃ Ä Ä |MàINVITE sip:+17592034561@123.123.1.234 SIP/2.0
Record-Route: <sip:23.21.76.23;lr;ftag=5d411c09;did=3b7.c57bab42>
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Contact: <sip:+19846572302@43.25.32.85:8394>
Max-Forwards: 69
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 3007n stamp 17816
Authorization: Digest username="19846572302",realm="23.21.76.23",nonce="48235aef53d38bbdccb25be97f6ac3599ce752eb",uri="sip:+17592034561@23.21.76.23",response="2993367e31be586485909086d44a328d",algorithm=MD5
Content-Length: 270
v=0
o=- 10556151 10556316 IN IP4 43.25.32.85
s=eyeBeam
c=IN IP4 231.43.25.1
t=0 0
m=audio 54864 RTP/AVP 18 101
a=alt:1 1 : 7DBA1F5A 00000092 10.0.0.1 8360
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active
a=nortpproxy:yes
ÄY#H¯' ¨ ¨ 0H% E èÌ@ @ £ ÇèNÃ@ V) Ä Ä ¯ SIP/2.0 100 Trying
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Server: OpenSER (1.2.2-notls (i386/linux))
Content-Length: 0
ÄY#H ; ® ® 0H% E èÍ@ @ ¢ÿÇèNÃ@ V) Ä Ä ¯
SIP/2.0 100 Giving a try
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Server: OpenSER (1.2.2-notls (i386/linux))
Content-Length: 0
ÄY#H; M M 0H% E =èÎ@ @ G;ÇèNÃ@®N Ä Ä )
ÑINVITE sip:17592034561@13.45.213.245 SIP/2.0
Record-Route: <sip:123.123.1.234;lr=on;ftag=5d411c09;osp-o=t5198095097179410177_s23.21.76.23_a1210276292_c1>
Record-Route: <sip:23.21.76.23;lr;ftag=5d411c09;did=3b7.c57bab42>
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Contact: <sip:+19846572302@43.25.32.85:8394>
Max-Forwards: 68
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 3007n stamp 17816
Authorization: Digest username="19846572302",realm="23.21.76.23",nonce="48235aef53d38bbdccb25be97f6ac3599ce752eb",uri="sip:+17592034561@23.21.76.23",response="2993367e31be586485909086d44a328d",algorithm=MD5
Content-Length: 270
v=0
o=- 10556151 10556316 IN IP4 43.25.32.85
s=eyeBeam
c=IN IP4 231.43.25.1
t=0 0
m=audio 54864 RTP/AVP 18 101
a=alt:1 1 : 7DBA1F5A 00000092 10.0.0.1 8360
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active
a=nortpproxy:yes
ÄY#HÖº Ê Ê _ d E º** 2 Ws@®NÇèNÃ Ä Ä ¦ SIP/2.0 100 Trying
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
To: <sip:+17592034561@23.21.76.23>;tag=gK0cf56d6a
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Content-Length: 0
ÄY#HY
Ö Ö _ d E Æ+ 2 V@®NÇèNÃ Ä Ä ² SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
To: <sip:+17592034561@23.21.76.23>;tag=gK0cf56d6a
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Content-Length: 0
ÄY#H
v v 0H% E fè×@ @ K ÇèNÃ@®N Ä Ä R úACK sip:17592034561@13.45.213.245 SIP/2.0
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Call-ID: 5d1bb15abd63917a
To: <sip:+17592034561@23.21.76.23>;tag=gK0cf56d6a
CSeq: 2 ACK
User-Agent: OpenSER (1.2.2-notls (i386/linux))
Content-Length: 0
---------------------------------
Download prohibited? No problem. CHAT from any browser, without download.
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
--
Thanks &Regards
Ravi Prakash Sunkara
VoIP Development Tech Lead
91-9999882776
---------------------------------
Check out the all-new face of Yahoo! India. Click here.
---------------------------------
Check out the all-new face of Yahoo! India. Click here.
Hi, I've implemented a system to control international destinations
(allow/deny) using "PDT" module (based on prefix).
In OpenSer 1.4 there will be a new module "userblacklist" which can handle
this issue in a more ellegant way, but for OpenSer 1.3.X we can use "pdt"
module (with a little patch to pdt.c) to implement it.
I've submitted the patch and the how-to:
https://sourceforge.net/tracker/index.php?func=detail&aid=1965211&group_id=…
Hope it could be useful. Regards.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
Please, check the updated instructions to install at:
www.sermyadmin.org
Flavio
----- Mensagem original ----
De: whudson05 <whudson05(a)gmail.com>
Para: users(a)lists.openser.org
Enviadas: Quarta-feira, 14 de Maio de 2008 11:29:26
Assunto: Re: [OpenSER-Users] sermyadmin almost works
I'm also at the same stage. I've looked at the mySQL queries and they appear
to be correct. Have you added the user admin to subscriber?
Lucas Catranis wrote:
>
> Anyone Get this setup correctly? I've been at it for a while and after
> getting it to insert new users I cannot login as an admin. I'm not sure
> where the problem is but Any help would be appreciated.
>
--
View this message in context: http://www.nabble.com/sermyadmin-almost-works-tp17219053p17232461.html
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hello,
I am having the following problem. please help me to figure out the issue.
I have my client calling me and getting 484 Address incomplete.
I checked all the SIP headers and found no issues. Also, when i use the same called number and make the calls through the same provider it works from my end with 200 OK. its really interesting and seems to be some issues with the headers.
I am using openser and following are the logs. sorry - its too long, but i need someones help to figure out whats going on really.
Also, following is the definition for the ips and telephone numbers.
FROM number - 17592034561
TO number - 19846572302
customer signaling ip-addr - 23.21.76.23
customer media ip-addr - 231.43.25.1
supplier media ip-addr - 43.25.32.85
supplier signaling ip-addr - 13.45.213.245
my signaling ip-addr - 123.123.1.234
---------------------------------------------------------------------
logs as below;
Y#HE& _d E pl@ 7!@V)ÇèNÃÄÄ|MàINVITE sip:+17592034561@123.123.1.234 SIP/2.0
Record-Route: <sip:23.21.76.23;lr;ftag=5d411c09;did=3b7.c57bab42>
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Contact: <sip:+19846572302@43.25.32.85:8394>
Max-Forwards: 69
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 3007n stamp 17816
Authorization: Digest username="19846572302",realm="23.21.76.23",nonce="48235aef53d38bbdccb25be97f6ac3599ce752eb",uri="sip:+17592034561@23.21.76.23",response="2993367e31be586485909086d44a328d",algorithm=MD5
Content-Length: 270
v=0
o=- 10556151 10556316 IN IP4 43.25.32.85
s=eyeBeam
c=IN IP4 231.43.25.1
t=0 0
m=audio 54864 RTP/AVP 18 101
a=alt:1 1 : 7DBA1F5A 00000092 10.0.0.1 8360
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active
a=nortpproxy:yes
ÄY#H¯' ¨ ¨ 0H% EèÌ@ @£ÇèNÃ@V)ÄįSIP/2.0 100 Trying
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Server: OpenSER (1.2.2-notls (i386/linux))
Content-Length: 0
ÄY#H; ® ® 0H% EèÍ@ @¢ÿÇèNÃ@V)Äį
SIP/2.0 100 Giving a try
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Server: OpenSER (1.2.2-notls (i386/linux))
Content-Length: 0
ÄY#H; M M 0H% E=èÎ@ @G;ÇèNÃ@®NÄÄ)
ÑINVITE sip:17592034561@13.45.213.245 SIP/2.0
Record-Route: <sip:123.123.1.234;lr=on;ftag=5d411c09;osp-o=t5198095097179410177_s23.21.76.23_a1210276292_c1>
Record-Route: <sip:23.21.76.23;lr;ftag=5d411c09;did=3b7.c57bab42>
To: <sip:+17592034561@23.21.76.23>
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Contact: <sip:+19846572302@43.25.32.85:8394>
Max-Forwards: 68
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: eyeBeam release 3007n stamp 17816
Authorization: Digest username="19846572302",realm="23.21.76.23",nonce="48235aef53d38bbdccb25be97f6ac3599ce752eb",uri="sip:+17592034561@23.21.76.23",response="2993367e31be586485909086d44a328d",algorithm=MD5
Content-Length: 270
v=0
o=- 10556151 10556316 IN IP4 43.25.32.85
s=eyeBeam
c=IN IP4 231.43.25.1
t=0 0
m=audio 54864 RTP/AVP 18 101
a=alt:1 1 : 7DBA1F5A 00000092 10.0.0.1 8360
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=direction:active
a=nortpproxy:yes
ÄY#HÖº Ê Ê _d E º** 2Ws@®NÇèNÃÄĦ SIP/2.0 100 Trying
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
To: <sip:+17592034561@23.21.76.23>;tag=gK0cf56d6a
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Content-Length: 0
ÄY#HY
Ö Ö _d E Æ+ 2V@®NÇèNÃÄIJ SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
Via: SIP/2.0/UDP 23.21.76.23;branch=z9hG4bKa52d.81f76261.0
Via: SIP/2.0/UDP 43.25.32.85:50006;branch=z9hG4bK-d87543-918910683-1--d87543-;rport=8394
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
To: <sip:+17592034561@23.21.76.23>;tag=gK0cf56d6a
Call-ID: 5d1bb15abd63917a
CSeq: 2 INVITE
Content-Length: 0
ÄY#H
v v 0H% Efè×@ @K ÇèNÃ@®NÄÄRúACK sip:17592034561@13.45.213.245 SIP/2.0
Via: SIP/2.0/UDP 123.123.1.234;branch=z9hG4bKa52d.b2b867d1.0
From: 19846572302<sip:+19846572302@23.21.76.23>;tag=5d411c09
Call-ID: 5d1bb15abd63917a
To: <sip:+17592034561@23.21.76.23>;tag=gK0cf56d6a
CSeq: 2 ACK
User-Agent: OpenSER (1.2.2-notls (i386/linux))
Content-Length: 0
---------------------------------
Download prohibited? No problem. CHAT from any browser, without download.
Hi,
I'm happy to announce that OpenSER 1.3.2 is out - after almost 6 months
from the first 1.3 release, 1.3.2 is available and it includes valuable
experiences and feedback from operating 1.3.x in live platform. This
means more stability, more reliability.
This is a minor release, so it includes only fixes. That means that
configuration and DB structure was not changes and it is fully
compatible with all the other releases from 1.3 branch.
A comprehensive compilation of fixes (thanks to Henning Westerholt) is
available via the Changelog - see
http://www.openser.org/pub/openser/1.3.2/ChangeLog
For more about how to download this version, see
http://www.openser.org/mos/view/News/NewsItem/OpenSER-1.3.2-is-released/
If people want to contribute with packages generated on different OS,
please let me know - I will be glad to upload them on the repository.
Regards,
Bogdan
Hi,
I would like to get your opinion/comments on some siptrace issue.
In 1.3, a new capability was added in siptrace - to trace the ACK
resulted from sending stateless replies.
The problem I discovered with this is that it cannot be controlled by
selecting the messages or transactions to be be traced. Usually you use
siptrace to trace only certain transactions / messages - tracing all
traffic is usually not a realistic option.
So, with the stateless ACK, the siptrace module cannot apply the
selection from script and trace them all, with no filtering at all. So,
if you want to trace a traffic for a single user, all ACK going through
the platform will be traced.
This reduces the usability of the module and you get a lot of garbage
tracing.
My suggestion will be to disable stateless ACK tracing until a way to
control/filter it is found. I'm asking this considering the upcoming
1.3.2 release from tomorrow.
Regards,
Bogdan
Hi Norman,
yup, that is exactly my problem - I use it only for doing siptrace per
user and on platform with high traffic, the stateless ACK tracing
produces a lot of residual data in DB.
Regards,
Bogdan
Norman Brandinger wrote:
> This change would be good. We have reduced our use of siptrace for
> this very reason.
>
> Norm
>
> Bogdan-Andrei Iancu wrote:
>> Hi,
>>
>> I would like to get your opinion/comments on some siptrace issue.
>>
>> In 1.3, a new capability was added in siptrace - to trace the ACK
>> resulted from sending stateless replies.
>>
>> The problem I discovered with this is that it cannot be controlled by
>> selecting the messages or transactions to be be traced. Usually you
>> use siptrace to trace only certain transactions / messages - tracing
>> all traffic is usually not a realistic option.
>>
>> So, with the stateless ACK, the siptrace module cannot apply the
>> selection from script and trace them all, with no filtering at all.
>> So, if you want to trace a traffic for a single user, all ACK going
>> through the platform will be traced.
>>
>> This reduces the usability of the module and you get a lot of garbage
>> tracing.
>>
>> My suggestion will be to disable stateless ACK tracing until a way to
>> control/filter it is found. I'm asking this considering the upcoming
>> 1.3.2 release from tomorrow.
>>
>> Regards,
>> Bogdan
>>
>> _______________________________________________
>> Devel mailing list
>> Devel(a)lists.openser.org
>> http://lists.openser.org/cgi-bin/mailman/listinfo/devel
>>
>>
>>
>
>
Dear All:
I have found there are some devices can't process two 180 ringing after use OPENSER to do parallel forking, so, i have a idea that is used OPENSER to delete To tag in the To header before relay it , and it works well with eyebeam.
But i can't find any spec to support my idea because it is against "early dialog" prograss and my question is
how does UE(eyebeam or some client) to create dialog if there is no any To tag in 180 ringing but 200 OK has in the latter ? i think the UA will generate local ring tone but no any dialog after receives 180 ringing with no To tag? is it right ? thanks,
allan
DISCLAIMER:
Sample Disclaimer added in a VBScript.