[Users] presence inferamation
venkid
venkatesh.d at pyronetworks.com
Sat Dec 2 06:48:50 CET 2006
Hi,
i am new to openser.i am using openser1.1.0.tls . i am getting
problem with PA module while try to get presence information.i am using
windows messenger as sip client . while am calling
handle_subscription("registrar") 8(32566) ERROR: parse_uri: bad uri,
state 0 parsed: <> (4) / <> (135224384) error is appears on openser
screen .
please help me on this .i am attaching openser.cfg also
8(32566) SIP Request:
8(32566) method: <SUBSCRIBE>
8(32566) uri: <sip:ramesh.b at 192.168.0.56>
8(32566) version: <SIP/2.0>
8(32566) parse_headers: flags=2
8(32566) end of header reached, state=5
8(32566) parse_headers: Via found, flags=2
8(32566) parse_headers: this is the first via
8(32566) After parse_msg...
8(32566) preparing to run routing scripts...
8(32566) parse_headers: flags=100
8(32566) DEBUG:maxfwd:is_maxfwd_present: value = 70
8(32566) parse_headers: flags=10
8(32566) DEBUG: add_param: tag=4728ca770b8542babb6c8be2e07558d1
8(32566) DEBUG: add_param: epid=7abbed3e7b
8(32566) DEBUG:parse_to:end of header reached, state=29
8(32566) DBUG:parse_to: display={"ramesh.b at 192.168.0.56"},
ruri={sip:ramesh.b at 192.168.0.56}
8(32566) parse_headers: flags=200
8(32566) DEBUG:parse_to:end of header reached, state=10
8(32566) DBUG:parse_to: display={}, ruri={sip:ramesh.b at 192.168.0.56}
8(32566) DEBUG: get_hdr_field: <To> [29]; uri=[sip:ramesh.b at 192.168.0.56]
8(32566) DEBUG: to body [<sip:ramesh.b at 192.168.0.56>
]
8(32566) get_hdr_field: cseq <CSeq>: <1> <SUBSCRIBE>
8(32566) DEBUG: get_hdr_body : content_length=0
8(32566) found end of header
8(32566) find_first_route: No Route headers found
8(32566) loose_route: There is no Route HF
8(32566) grep_sock_info - checking if host==us: 12==9 && [192.168.0.56]
== [127.0.0.1]
8(32566) grep_sock_info - checking if port 5060 matches port 5060
8(32566) grep_sock_info - checking if host==us: 12==12 &&
[192.168.0.56] == [192.168.0.56]
8(32566) grep_sock_info - checking if port 5060 matches port 5060
8(32566) grep_sock_info - checking if host==us: 12==9 && [192.168.0.56]
== [127.0.0.1]
8(32566) grep_sock_info - checking if port 5060 matches port 5060
8(32566) grep_sock_info - checking if host==us: 12==12 &&
[192.168.0.56] == [192.168.0.56]
8(32566) grep_sock_info - checking if port 5060 matches port 5060
8(32566) DEBUG: t_newtran: msg id=5 , global msg id=2 , T on
entrance=0xffffffff
8(32566) parse_headers: flags=ffffffffffffffff
8(32566) parse_headers: flags=78
8(32566) t_lookup_request: start searching: hash=20651, isACK=0
8(32566) DEBUG: proceeding to pre-RFC3261 transaction matching
8(32566) DEBUG: t_lookup_request: no transaction found
8(32566) handle_subscription() entered
8(32566) parse_headers: flags=608010
8(32566) check_message -0- _m=0x812fec8
8(32566) check_message -1- 8(32566) check_message -2- accepts_mimes=(nil)
8(32566) check_message -3-
*8(32566) check_message -4- parsed_event=(nil)
8(32566) check_message -5-
8(32566) get_pres_uri: _puri=
8(32566) ERROR: parse_uri: bad uri, state 0 parsed: <> (4) / <>
(135224384)
8(32566) extract_plain_uri(): Error while parsing URI
6(32559) SIP Request:*
6(32559) method: <SUBSCRIBE>
6(32559) uri: <sip:mahesh at 192.168.0.56>
6(32559) version: <SIP/2.0>
6(32559) parse_headers: flags=2
6(32559) end of header reached, state=5
6(32559) 7(32560) SIP Request:
7(32560) method: <SUBSCRIBE>
7(32560) uri: <sip:ramesh.b at 192.168.0.56>
7(32560) version: <SIP/2.0>
7(32560) parse_headers: flags=2
7(32560) end of header reached, state=5
7(32560) parse_headers: Via found, flags=2
7(32560) parse_headers: this is the first via
7(32560) After parse_msg...
7(32560) preparing to run routing scripts...
7(32560) parse_headers: flags=100
7(32560) DEBUG:maxfwd:is_maxfwd_present: value = 70
7(32560) parse_headers: flags=10
Thanks and Regards
venkatesh.d
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: presence.cfg
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20061202/bbb6e8e6/attachment.asc>
More information about the sr-users
mailing list