A more complete debug ... 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [run, udp_trsp.cpp:209] DEBUG: recvd msg --++-- SIP/2. 0 200 OK Via: SIP/2.0/UDP 91.XXX.XXX.XXX;received=91.XXX.XXX.XXX;branch=z9hG4bKjGZBoa6U;rport=5060 From: <sip:[email protected] -virtual.com>;tag=164BE577-4C3EC7960006DF38-B6DDFB90 To: <sip:[email protected]>;tag=as59677a87 Call-ID: [email protected] CSeq: 11 INVITE User-Agent: CallWeaver Allow: INVITE, ACK, CANCEL, OPTIONS , BYE, REFER, SUBSCRIBE, NOTIFY Max-Forwards: 70 Contact: <sip:[email protected]> Content-Type: applica 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [parse_via_params, parse_via.cpp:523] DEBUG: parsed br anch: z9hG4bKjGZBoa6U 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [parse_via_params, parse_via.cpp:546] DEBUG: has_rport : 1 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [received_msg, trans_layer.cpp:1094] DEBUG: Reply matc hed an existing transaction 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [update_uac_reply, trans_layer.cpp:1137] DEBUG: reply code = 200 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [update_uac_reply, trans_layer.cpp:1197] DEBUG: Positi ve final reply to INVITE transaction (state=3) 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [reset_timer, sip_trans.cpp:155] DEBUG: New timer of t ype L at time=3397 (repeated=0) 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [handle_sip_reply, SipCtrlInterface.cpp:487] DEBUG: Re ceived reply: 200 OK 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [handle_sip_reply, SipCtrlInterface.cpp:488] DEBUG: re ply.callid = <[email protected]> 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [handle_sip_reply, SipCtrlInterface.cpp:489] DEBUG: re ply.local_tag = <164BE577-4C3EC7960006DF38-B6DDFB90> 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [handle_sip_reply, SipCtrlInterface.cpp:490] DEBUG: re ply.remote_tag = <as59677a87> 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [handle_sip_reply, SipCtrlInterface.cpp:491] DEBUG: cs eq = <11> 2010-07-15T10:32:34+02:00 <daemon.err> mg01 sems[27971]: [#b5cceb90] [handleSipMsg, AmSipDispatcher.cpp:50] ERROR: unhandled positive reply: INVITE [code:200;phrase: [OK];i:[email protected];cseq:11;cseq meth:INVITE;l-tag :164BE577-4C3EC7960006DF38-B6DDFB90;r-tag:as59677a87;m:<sip:[email protected]>,<sip:[email protected]>;hdr: [Use r-Agent: CallWeaver Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Max-Forwards: 70 ];c:application/sd p;body:[v=0 o=root 1857 1858 IN IP4 91.XXX.XXX.XXB s=session c=IN IP4 91.XXX.XXX.XXB t=0 0 m=audio 18348 RTP/AVP 18 8 0 96 a 2010-07-15T10:32:34+02:00 <daemon.debug> mg01 sems[27971]: [#b5cceb90] [~sip_msg, sip_parser.cpp:92] DEBUG: ~sip_msg()
What I don't undestand it's why SEMS fires an ERROR about "unhandled postive reply" ... when the reply it's OK! Any clue ? -- Raúl Alexis Betancor Santana Dimensión Virtual _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
