On Mon, May 26, 2008 at 8:08 PM, C?sar Davi <cesargxn at gmail.com> wrote: > Hi All, > > I have the next scenario: 2 endpoints, "A" cisco IP Phone, "B" "PJSIP IP > Phone". When "A" calls "B", at "B", a Timeout timer event occurs. > Does anyone knows what is happening? > That timeout event is for destroying transaction, and not the call. The call itself should be left in confirmed state. Cheers Benny > > Below, you can see the output of the terminal : > > > 00:36:53.573 sip_endpoint.c Processing incoming message: Request msg > INVITE/cseq=1 (r) > > 00:36:53.578 tsx0x11a5e4 Transaction created for Request msg > INVITE/cseq=1 (rdata0) > > 00:36:53.579 tsx0x11a5e4 Incoming Request msg INVITE/cseq=1 > (rdata0xc2fb4) in statl > 00:36:53.579 tsx0x11a5e4 State changed from Null to Trying, event=RX_MSG > > 00:36:53.580 dlg0x119ddc Transaction tsx0x11a5e4 state changed to Trying > 00:36:53.581 dlg0x119ddc UAS dialog created > 00:36:53.583 dlg0x119ddc Module mod-invite added as dialog usage, > data=0x11a3c0 > 00:36:53.584 dlg0x119ddc Session count inc to 2 by mod-invite > 00:36:53.585 inv0x119ddc UAS invite session created for dialog > dlg0x119ddc > 00:36:53.586 endpoint Response msg 100/INVITE/cseq=1 (tdta0x11c5c8) > created > 00:36:53.587 dlg0x119ddc Initial answer Response msg 100/INVITE/cseq=1 > (tdta0x11c5) > 00:36:53.587 inv0x119ddc Sending Response msg 100/INVITE/cseq=1 > (tdta0x11c5c8) > 00:36:53.587 dlg0x119ddc Sending Response msg 100/INVITE/cseq=1 > (tdta0x11c5c8) > 00:36:53.588 tsx0x11a5e4 Sending Response msg 100/INVITE/cseq=1 > (tdta0x11c5c8) in g > 00:36:53.589 sip_resolve.c Target '192.168.1.3:5060' type=UDP resolved to > '192.168.1P > 00:36:53.591 tsx0x11a5e4 State changed from Trying to Proceeding, > event=TX_MSG > 00:36:53.591 dlg0x119ddc Transaction tsx0x11a5e4 state changed to > Proceeding > 00:36:53.594 inv0x119ddc SDP negotiation done, status=0 > 00:36:53.598 inv0x119ddc Sending Response msg 200/INVITE/cseq=1 > (tdta0x11c5c8) > 00:36:53.598 dlg0x119ddc Sending Response msg 200/INVITE/cseq=1 > (tdta0x11c5c8) > 00:36:53.599 tsx0x11a5e4 Sending Response msg 200/INVITE/cseq=1 > (tdta0x11c5c8) in g > 00:36:53.600 tsx0x11a5e4 State changed from Proceeding to Completed, > event=TX_MSG > 00:36:53.601 dlg0x119ddc Transaction tsx0x11a5e4 state changed to > Completed > 00:36:53.603 inv0x119ddc Sending Response msg 200/INVITE/cseq=1 > (tdta0x11c5c8) > 00:36:53.603 dlg0x119ddc Sending Response msg 200/INVITE/cseq=1 > (tdta0x11c5c8) > 00:36:53.604 tsx0x11a5e4 Sending Response msg 200/INVITE/cseq=1 > (tdta0x11c5c8) in d > 00:36:54.083 sip_endpoint.c Processing incoming message: Request msg > ACK/cseq=1 (rdat) > 00:36:54.083 tsx0x11a5e4 Incoming Request msg ACK/cseq=1 (rdata0xc2fb4) > in state Cd > > 00:36:54.084 tsx0x11a5e4 State changed from Completed to Confirmed, > event=RX_MSG > > 00:36:54.084 dlg0x119ddc Transaction tsx0x11a5e4 state changed to > Confirmed > > 00:36:54.590 tsx0x11a5e4 Timeout timer event > > 00:36:54.591 tsx0x11a5e4 State changed from Confirmed to Terminated, > event=TIMER > 00:36:54.591 dlg0x119ddc Transaction tsx0x11a5e4 state changed to > Terminated > 00:36:55.100 tsx0x11a5e4 Timeout timer event > 00:36:55.101 tsx0x11a5e4 State changed from Terminated to Destroyed, > event=TIMER > 00:36:55.101 tdta0x11c5c8 Destroying txdata Response msg > 200/INVITE/cseq=1 (tdta0x1) > 00:36:55.102 tsx0x11a5e4 Transaction destroyed! > > Thanks in advance > > C?sar >