hello, using my fritzbox fon with an account from Carpo, ser 0.10.99, to call a cisco 7960 behind the same fritzbox fon, that uses as well an Carpo account, an hang up, the called cisco 7960 continues ringing for a minute.
(fritzbox - ser - (same) fritzbox - 7960)
Vice versa the same. (7960 - fritzbox - ser - fritzbox)
Not so when I use the 7960 with a sipgate account (7960 - sipgate - telefonica gateway - Carpo ser - fritzbox) to call the fritzbox.
Is this a ser problem? Perhaps a problem, when the call-phone and the called-phone use the same IP? Or is this a configuration problem of ser? What can I debug to find where the problem is?
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Hi!
I observed the following errors reported by ser during normal runtime are they critical?:
Feb 8 12:47:24 rd ser[12172]: ERROR: parse_uri: bad uri, state 0 parsed: <tzl@> (4) / tzl@voip.touk.pl (16)
Feb 8 12:47:24 rd ser[12172]: ERROR: avp_db.c:187: Error while parsing URI 'tzl@voip.touk.pl'
When I compiled ser I received the following errors: unixsock_server.c: In function ‘init_unixsock_children’: unixsock_server.c:274: error: ‘last_process’ undeclared (first use in this function) unixsock_server.c:274: error: (Each undeclared identifier is reported only once unixsock_server.c:274: error: for each function it appears in.) unixsock_server.c:256: warning: unused variable ‘sockfd’ unixsock_server.c:253: warning: unused variable ‘backup’ make[1]: *** [unixsock_server.o] Błąd 1 checks.c: In function ‘generate_avps’: checks.c:89: error: ‘A_SER_ATTRS’ undeclared (first use in this function) checks.c:89: error: (Each undeclared identifier is reported only once checks.c:89: error: for each function it appears in.) checks.c: In function ‘radius_does_uri_exist’: checks.c:146: error: ‘V_CALL_CHECK’ undeclared (first use in this function) make[1]: *** [checks.o] Błąd 1
Bests -tomasz
On Thu, 2007-02-08 at 12:42 +0100, tzieleniewski wrote:
Hi!
I observed the following errors reported by ser during normal runtime are they critical?: Feb 8 12:47:24 rd ser[12172]: ERROR: parse_uri: bad uri, state 0 parsed: <tzl@> (4) / tzl@voip.touk.pl (16) Feb 8 12:47:24 rd ser[12172]: ERROR: avp_db.c:187: Error while parsing URI 'tzl@voip.touk.pl'
The uri must start with sip: sips: or tel: Michal
On Thu, 2007-02-08 at 12:42 +0100, tzieleniewski wrote:
Hi!
I observed the following errors reported by ser during normal runtime are they critical?: Feb 8 12:47:24 rd ser[12172]: ERROR: parse_uri: bad uri, state 0 parsed: <tzl@> (4) / tzl@voip.touk.pl (16) Feb 8 12:47:24 rd ser[12172]: ERROR: avp_db.c:187: Error while parsing URI 'tzl@voip.touk.pl'
The uri must start with sip: sips: or tel: Michal
why this error occurs after I invoke the load_attrs("$tr", "$t.uid");
my ser.cfg: .... # load the preferences of the callee to have his timeout values loaded xlog("L_INFO", " route[INBOUND]: load_attrs($tu,$t.uid) \n"); load_attrs("$tu", "$t.uid"); xlog("L_INFO", " route[INBOUND]: load_attrs($tr,$t.uid) \n"); load_attrs("$tr", "$t.uid");
# native SIP destinations are handled using our USRLOC DB xlog("L_INFO", " route[INBOUND]: (lookup_contacts(location)) || else \n"); if (lookup_contacts("location")) { ....
log file: Feb 8 14:12:27 rd ser[27397]: route[INBOUND]: load_attrs($tr,$t.uid) Feb 8 14:12:27 rd ser[27397]: ERROR: parse_uri: bad uri, state 0 parsed: <hell> (4) / hellboy@voip.touk.pl (20) Feb 8 14:12:27 rd ser[27397]: ERROR: avp_db.c:187: Error while parsing URI 'hellboy@voip.touk.pl' Feb 8 14:12:27 rd ser[27397]: route[INBOUND]: (lookup_contacts(location)) || else Feb 8 14:12:27 rd ser[27397]: route[INBOUND]: append_hf(P-hint: usrloc applied)
On Thu, 2007-02-08 at 14:05 +0100, tzieleniewski wrote:
On Thu, 2007-02-08 at 12:42 +0100, tzieleniewski wrote:
Hi!
I observed the following errors reported by ser during normal runtime are they critical?: Feb 8 12:47:24 rd ser[12172]: ERROR: parse_uri: bad uri, state 0 parsed: <tzl@> (4) / tzl@voip.touk.pl (16) Feb 8 12:47:24 rd ser[12172]: ERROR: avp_db.c:187: Error while parsing URI 'tzl@voip.touk.pl'
The uri must start with sip: sips: or tel: Michal
why this error occurs after I invoke the load_attrs("$tr", "$t.uid");
my ser.cfg: .... # load the preferences of the callee to have his timeout values loaded xlog("L_INFO", " route[INBOUND]: load_attrs($tu,$t.uid) \n"); load_attrs("$tu", "$t.uid"); xlog("L_INFO", " route[INBOUND]: load_attrs($tr,$t.uid) \n"); load_attrs("$tr", "$t.uid");
load_attrs into the TO/URI track must have uri (request / to / called-party-id / whichever you want) as the second parameter.
use load_attrs("$tr","@ruri"); or load_attrs("$tr","@to.uri"); or e.g. load_attrs("$tr","@msg["X-my-own-header"].nameaddr.uri");
the uid is used to load just the TO/USER attributes.
Michal
At 14:05 08/02/2007, tzieleniewski wrote:
On Thu, 2007-02-08 at 12:42 +0100, tzieleniewski wrote:
Hi!
I observed the following errors reported by ser during normal runtime are they critical?: Feb 8 12:47:24 rd ser[12172]: ERROR: parse_uri: bad uri, state 0 parsed: <tzl@> (4) / tzl@voip.touk.pl (16) Feb 8 12:47:24 rd ser[12172]: ERROR: avp_db.c:187: Error while parsing URI 'tzl@voip.touk.pl'
The uri must start with sip: sips: or tel: Michal
SER is using technique known as "lazy parsing", which means it doesn't touch a syntactical element unless needed. Supposingly, in previous parts of the script there was no need to use the To header field. Lazy parsing is done for better performance as it significantly improves overall performance.
-jiri
why this error occurs after I invoke the load_attrs("$tr", "$t.uid");
my ser.cfg: .... # load the preferences of the callee to have his timeout values loaded xlog("L_INFO", " route[INBOUND]: load_attrs($tu,$t.uid) \n"); load_attrs("$tu", "$t.uid"); xlog("L_INFO", " route[INBOUND]: load_attrs($tr,$t.uid) \n"); load_attrs("$tr", "$t.uid");
# native SIP destinations are handled using our USRLOC DB xlog("L_INFO", " route[INBOUND]: (lookup_contacts(location)) || else \n"); if (lookup_contacts("location")) { ....log file: Feb 8 14:12:27 rd ser[27397]: route[INBOUND]: load_attrs($tr,$t.uid) Feb 8 14:12:27 rd ser[27397]: ERROR: parse_uri: bad uri, state 0 parsed: <hell> (4) / hellboy@voip.touk.pl (20) Feb 8 14:12:27 rd ser[27397]: ERROR: avp_db.c:187: Error while parsing URI 'hellboy@voip.touk.pl' Feb 8 14:12:27 rd ser[27397]: route[INBOUND]: (lookup_contacts(location)) || else Feb 8 14:12:27 rd ser[27397]: route[INBOUND]: append_hf(P-hint: usrloc applied)
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
tzieleniewski wrote:
Hi!
I observed the following errors reported by ser during normal runtime are they critical?:
Feb 8 12:47:24 rd ser[12172]: ERROR: parse_uri: bad uri, state 0 parsed: <tzl@> (4) / tzl@voip.touk.pl (16)
Feb 8 12:47:24 rd ser[12172]: ERROR: avp_db.c:187: Error while parsing URI 'tzl@voip.touk.pl'
today I got the exact same error and was quite puzzled for a while..
I found that my config was wrong, in this line:
if (lookup_user("$tu","@ruri.user")) {
after I changed the line to:
if (lookup_user("$tu","@ruri")) {
I did not get any more parse errors..
I think you can also do:
if (lookup_user("To")) {
but I am not sure what the difference is..
hope this helps.
/alfred
-
Alfred E. Heggestad -
Jiri Kuthan -
Michal Matyska -
Theodor Meier -
tzieleniewski