[Serusers] Re: SER 0.9.0. Presence KPhone

Aisling ashling.odriscoll at cit.ie
Wed Jul 6 15:11:29 CEST 2005


Hi,
 
Just an update. I manually created the presence tables in the SER
database according to the following link:
 
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/pa/pa.s
ql?rev=1.7
<http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/pa/pa.
sql?rev=1.7&content-type=text/vnd.viewcvs-markup>
&content-type=text/vnd.viewcvs-markup
 
That has gotten rid of the errors in the below email. However errors
still exist when the clients sent their subscribe messages
 
handle_subscription() entered
get_pres_uri: _puri=sip:2093 at xxx.xxx.xxx.xxx
update_presentity() found watcher
handle_subscription about to return 1: w->event_package=1 w->accept=0
p->flags=4 w=>flags=1 w=0X407c1da0
ERROR: get_hdr_field: bad to header
ERROR: bad header field
ERROR:maxfwd:is_maxfwd_present : parsing MAX_FORWARD header failed!
ERROR: get_hdr_field: bad to header
ERROR: bad header field
ERROR:parse_from_header: bad msg or missing FROM header
Insert_RR(): From parsing failed
record_route(): Error while inserting Record-Route line
ERROR: get_hdr_field: bad to header
ERROR: bad header field
find_first_route: Error while parsing headers
ERROR: get_hdr_field: bad to header
ERROR: bad header field
ERROR: t_newtran: parse_headers failed
ERROR: get_hdr_field: bad to header
ERROR: bad header field
ERROR: t_newtran: parse_headers failed
ERROR: get_hdr_field: bad to header
ERROR: bad header field
ERROR: get_hdr_field: bad to header
ERROR: bad header field
ERROR: build_res_buf_from_sip_req: alas, parse_headers failed
ERROR: sl_reply_error used: I'm terribly sorry, server error occurred
(1/SL)
 
 
Has anybody experienced these errors? Is it a problem with the
compatibility of  SER and KPhone?
 
Many Thanks,
Aisling.
 
 
-----Original Message-----
From: Aisling [mailto:ashling.odriscoll at cit.ie] 
Sent: 06 July 2005 10:15
To: 'serusers at lists.iptel.org'
Subject: SER 0.9.0. Presence KPhone
 
Hi all,
 
I was just wondering if SER 0.9.0 is working for presence with KPhone? I
have two KPhone clients and I am trying to get presence working -
However when the SUBSCRIBE message is sent the following errors appear
in SER:
 
handle_subscription() entered
get_pres_uri: _puri=sip:2093 at xxx.xxx.xxx.xxx
submit_query(): Table 'ser.presentity' doesn't exist
submit_query(): Error while submitting query
pdomain_load_presentities: Error while querying presentity
submit_query(): Table 'ser.presentity' doesn't exist
submit_query(): Error while submitting query
new_presentity: Error while querying presentity
create_presentity(): Error while creating presentity
handle_subscription(): Error while creating new presentity
handle_subscription about to return -1
 
The relevant part of the ser.cfg:
 
loadmodule "/opt/ser/lib/ser/modules/pa.so"
 
modparam ("pa", "default_expires", 3600)
modparam ("pa", "pa_domain", xxx.xxx.xxx.xxx)
modparam ("pa", "use_db", 1)
modparam ("pa", "db_url", "mysql://username:password@localhost/ser")
 
if (uri==myself){
 
if (method=="SUBSCRIBE"){
  if (t_newtran()){
    handle_subscription("registrar");
    break;
 };
};
 
Any ideas?
Many thanks,
Aisling.
 


-------------------Legal  Disclaimer---------------------------------------

The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050706/44035419/attachment.htm>


More information about the sr-users mailing list