SipProvider-5076: Date: 18:42:33.936 Thu 12 Feb 2009 SipProvider-5076: SipStack: mjsip stack 1.6 SipProvider-5076: new SipProvider(): 5076/udp/tcp SipProvider-5076: udp is up SipProvider-5076: tcp is up ExtendedInviteDialog#14: changed dialog state: D_INIT ExtendedInviteDialog#14: changed dialog state: D_WAITING TransactionServer#260: id: INVITE TransactionServer#260: created TransactionServer#260: start TransactionServer#260: changed transaction state: T_Waiting SipProvider-5076: adding SipProviderListener: INVITE SipProvider-5076: 1 listeners: INVITE, TransactionClient#261: id: 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244 TransactionClient#261: created TransactionClient#261: start TransactionClient#261: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:42:33.945 Thu 12 Feb 2009, 10.102.40.107:5060/udp (466 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:42:33.947 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244 TransactionClient#261: changed transaction state: T_Proceeding 18:42:33.948 Thu 12 Feb 2009, 10.102.40.107:5060/udp (522 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244 TransactionClient#261: changed transaction state: T_Completed TransactionClient#262: id: 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245 TransactionClient#262: created TransactionClient#262: start TransactionClient#262: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244, 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:42:33.951 Thu 12 Feb 2009, 10.102.40.107:5060/udp (656 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:42:33.952 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245 TransactionClient#262: changed transaction state: T_Proceeding 18:42:33.958 Thu 12 Feb 2009, 10.102.40.107:5060/udp (495 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245 TransactionClient#262: changed transaction state: T_Completed TransactionClient#261: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-1-REGISTER-10.102.250.200:5076-z9hG4bK46270244 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245, TransactionClient#261: changed transaction state: T_Terminated TransactionClient#262: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-2-REGISTER-10.102.250.200:5076-z9hG4bK66152245 SipProvider-5076: 1 listeners: INVITE, TransactionClient#262: changed transaction state: T_Terminated TransactionClient#263: id: 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246 TransactionClient#263: created TransactionClient#263: start TransactionClient#263: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:43:03.951 Thu 12 Feb 2009, 10.102.40.107:5060/udp (466 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:43:03.952 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246 TransactionClient#263: changed transaction state: T_Proceeding 18:43:03.953 Thu 12 Feb 2009, 10.102.40.107:5060/udp (522 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246 TransactionClient#263: changed transaction state: T_Completed TransactionClient#264: id: 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247 TransactionClient#264: created TransactionClient#264: start TransactionClient#264: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247, 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:43:03.956 Thu 12 Feb 2009, 10.102.40.107:5060/udp (656 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:43:03.957 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247 TransactionClient#264: changed transaction state: T_Proceeding 18:43:03.964 Thu 12 Feb 2009, 10.102.40.107:5060/udp (495 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247 TransactionClient#264: changed transaction state: T_Completed TransactionClient#263: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-3-REGISTER-10.102.250.200:5076-z9hG4bK42660246 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247, TransactionClient#263: changed transaction state: T_Terminated TransactionClient#264: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-4-REGISTER-10.102.250.200:5076-z9hG4bK93208247 SipProvider-5076: 1 listeners: INVITE, TransactionClient#264: changed transaction state: T_Terminated TransactionClient#265: id: 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248 TransactionClient#265: created TransactionClient#265: start TransactionClient#265: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:43:33.957 Thu 12 Feb 2009, 10.102.40.107:5060/udp (466 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:43:33.959 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248 TransactionClient#265: changed transaction state: T_Proceeding 18:43:33.960 Thu 12 Feb 2009, 10.102.40.107:5060/udp (522 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248 TransactionClient#265: changed transaction state: T_Completed TransactionClient#266: id: 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249 TransactionClient#266: created TransactionClient#266: start TransactionClient#266: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249, 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:43:33.963 Thu 12 Feb 2009, 10.102.40.107:5060/udp (656 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:43:33.964 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249 TransactionClient#266: changed transaction state: T_Proceeding 18:43:33.969 Thu 12 Feb 2009, 10.102.40.107:5060/udp (495 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249 TransactionClient#266: changed transaction state: T_Completed TransactionClient#265: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-5-REGISTER-10.102.250.200:5076-z9hG4bK61795248 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249, TransactionClient#265: changed transaction state: T_Terminated TransactionClient#266: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-6-REGISTER-10.102.250.200:5076-z9hG4bK16076249 SipProvider-5076: 1 listeners: INVITE, TransactionClient#266: changed transaction state: T_Terminated TransactionClient#267: id: 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250 TransactionClient#267: created TransactionClient#267: start TransactionClient#267: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:03.964 Thu 12 Feb 2009, 10.102.40.107:5060/udp (466 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:44:03.965 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250 TransactionClient#267: changed transaction state: T_Proceeding 18:44:03.966 Thu 12 Feb 2009, 10.102.40.107:5060/udp (522 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250 TransactionClient#267: changed transaction state: T_Completed TransactionClient#268: id: 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251 TransactionClient#268: created TransactionClient#268: start TransactionClient#268: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250, 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:03.982 Thu 12 Feb 2009, 10.102.40.107:5060/udp (656 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:44:03.983 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251 TransactionClient#268: changed transaction state: T_Proceeding 18:44:03.989 Thu 12 Feb 2009, 10.102.40.107:5060/udp (495 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251 TransactionClient#268: changed transaction state: T_Completed TransactionClient#267: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-7-REGISTER-10.102.250.200:5076-z9hG4bK53745250 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251, TransactionClient#267: changed transaction state: T_Terminated TransactionClient#268: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-8-REGISTER-10.102.250.200:5076-z9hG4bK49631251 SipProvider-5076: 1 listeners: INVITE, TransactionClient#268: changed transaction state: T_Terminated TransactionClient#269: id: 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252 TransactionClient#269: created TransactionClient#269: start TransactionClient#269: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:33.970 Thu 12 Feb 2009, 10.102.40.107:5060/udp (466 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:44:33.971 Thu 12 Feb 2009, 10.102.40.107:5060/udp (383 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252 TransactionClient#269: changed transaction state: T_Proceeding 18:44:33.973 Thu 12 Feb 2009, 10.102.40.107:5060/udp (522 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252 TransactionClient#269: changed transaction state: T_Completed TransactionClient#270: id: 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253 TransactionClient#270: created TransactionClient#270: start TransactionClient#270: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253, 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:33.976 Thu 12 Feb 2009, 10.102.40.107:5060/udp (657 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:44:33.977 Thu 12 Feb 2009, 10.102.40.107:5060/udp (384 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253 TransactionClient#270: changed transaction state: T_Proceeding 18:44:33.985 Thu 12 Feb 2009, 10.102.40.107:5060/udp (496 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253 TransactionClient#270: changed transaction state: T_Completed ExtendedInviteDialog#14: isWaiting - callState=1 ExtendedCall: calling ExtendedInviteDialog#15: changed dialog state: D_INIT ExtendedInviteDialog#15: inside invite(callee,caller,contact,sdp) ExtendedInviteDialog#15: inside invite(invite) ExtendedInviteDialog#15: changed dialog state: D_INVITING ExtendedInviteDialog#15: new dialog id: 673566785188@10.102.250.200-z9hG4bK97650672-null SipProvider-5076: adding SipProviderListener: 673566785188@10.102.250.200-z9hG4bK97650672-null SipProvider-5076: 4 listeners: 673566785188@10.102.250.200-z9hG4bK97650672-null, INVITE, 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253, 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252, TransactionClient#271: id: 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254 TransactionClient#271: created TransactionClient#271: start TransactionClient#271: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254 SipProvider-5076: 5 listeners: 673566785188@10.102.250.200-z9hG4bK97650672-null, INVITE, 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253, 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:36.378 Thu 12 Feb 2009, 10.102.40.107:5060/udp (629 bytes): INVITE sip:elisa.delpiano@csi.it SIP/2.0, sent 18:44:36.380 Thu 12 Feb 2009, 10.102.40.107:5060/udp (498 bytes): SIP/2.0 407 Proxy Authentication Required, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254 TransactionClient#271: changed transaction state: T_Completed ExtendedInviteDialog#15: onTransFailureResponse 1 ExtendedInviteDialog#15: inside onTransFailureResponse(673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254,msg) AckTransactionClient#272: id: 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK58939255 AckTransactionClient#272: created AckTransactionClient#272: start SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:36.383 Thu 12 Feb 2009, 10.102.40.107:5060/udp (432 bytes): ACK sip:elisa.delpiano@csi.it SIP/2.0, sent AckTransactionClient#272: changed transaction state: T_Terminated TransactionClient#273: id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 TransactionClient#273: created TransactionClient#273: start TransactionClient#273: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: 6 listeners: 673566785188@10.102.250.200-z9hG4bK97650672-null, INVITE, 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253, 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256, 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:36.386 Thu 12 Feb 2009, 10.102.40.107:5060/udp (840 bytes): INVITE sip:elisa.delpiano@csi.it SIP/2.0, sent SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:36.386 Thu 12 Feb 2009, 10.102.40.107:5060/udp (396 bytes): ACK sip:elisa.delpiano@csi.it SIP/2.0, sent 18:44:36.393 Thu 12 Feb 2009, 10.102.40.107:5060/udp (346 bytes): SIP/2.0 100 Giving a try, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 TransactionClient#273: changed transaction state: T_Proceeding ExtendedInviteDialog#15: inside onTransProvisionalResponse(tc,mdg) 18:44:36.509 Thu 12 Feb 2009, 10.102.40.107:5060/udp (469 bytes): SIP/2.0 180 Ringing, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 ExtendedInviteDialog#15: inside onTransProvisionalResponse(tc,mdg) TransactionClient#273: Retransmission timeout expired SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:44:36.888 Thu 12 Feb 2009, 10.102.40.107:5060/udp (840 bytes): INVITE sip:elisa.delpiano@csi.it SIP/2.0, sent 18:44:36.896 Thu 12 Feb 2009, 10.102.40.107:5060/udp (469 bytes): SIP/2.0 180 Ringing, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 ExtendedInviteDialog#15: inside onTransProvisionalResponse(tc,mdg) TransactionClient#269: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-9-REGISTER-10.102.250.200:5076-z9hG4bK53666252 SipProvider-5076: 5 listeners: 673566785188@10.102.250.200-z9hG4bK97650672-null, INVITE, 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253, 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, TransactionClient#269: changed transaction state: T_Terminated TransactionClient#270: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-10-REGISTER-10.102.250.200:5076-z9hG4bK63803253 SipProvider-5076: 4 listeners: 673566785188@10.102.250.200-z9hG4bK97650672-null, INVITE, 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, TransactionClient#270: changed transaction state: T_Terminated 18:44:40.267 Thu 12 Feb 2009, 10.102.40.107:5060/udp (422 bytes): SIP/2.0 486 Busy Here, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 TransactionClient#273: changed transaction state: T_Completed ExtendedInviteDialog#15: onTransFailureResponse 1 ExtendedInviteDialog#15: inside onTransFailureResponse(673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256,msg) ExtendedInviteDialog#15: inside onTransFailureResponse(673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256,msg) ExtendedInviteDialog#15: changed dialog state: D_CLOSE SipProvider-5076: removing SipProviderListener: 673566785188@10.102.250.200-z9hG4bK97650672-null SipProvider-5076: 3 listeners: INVITE, 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, ExtendedInviteDialog#16: changed dialog state: D_INIT ExtendedInviteDialog#16: changed dialog state: D_WAITING TransactionServer#274: id: INVITE TransactionServer#274: created TransactionServer#274: start TransactionServer#274: changed transaction state: T_Waiting SipProvider-5076: adding SipProviderListener: INVITE SipProvider-5076: 3 listeners: INVITE, 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, 18:44:40.768 Thu 12 Feb 2009, 10.102.40.107:5060/udp (422 bytes): SIP/2.0 486 Busy Here, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 18:44:41.789 Thu 12 Feb 2009, 10.102.40.107:5060/udp (422 bytes): SIP/2.0 486 Busy Here, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 18:44:43.738 Thu 12 Feb 2009, 10.102.40.107:5060/udp (422 bytes): SIP/2.0 486 Busy Here, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: message passed to transaction: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 TransactionClient#273: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 673566785188@10.102.250.200-2-INVITE-10.102.250.200:5076-z9hG4bK11327256 SipProvider-5076: 2 listeners: INVITE, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, TransactionClient#273: changed transaction state: T_Terminated TransactionClient#275: id: 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257 TransactionClient#275: created TransactionClient#275: start TransactionClient#275: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:45:03.977 Thu 12 Feb 2009, 10.102.40.107:5060/udp (467 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:45:03.978 Thu 12 Feb 2009, 10.102.40.107:5060/udp (384 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257 TransactionClient#275: changed transaction state: T_Proceeding 18:45:03.979 Thu 12 Feb 2009, 10.102.40.107:5060/udp (523 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257 TransactionClient#275: changed transaction state: T_Completed TransactionClient#276: id: 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258 TransactionClient#276: created TransactionClient#276: start TransactionClient#276: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258 SipProvider-5076: 4 listeners: INVITE, 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257, 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258, 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:45:03.982 Thu 12 Feb 2009, 10.102.40.107:5060/udp (657 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:45:03.983 Thu 12 Feb 2009, 10.102.40.107:5060/udp (384 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258 TransactionClient#276: changed transaction state: T_Proceeding 18:45:03.988 Thu 12 Feb 2009, 10.102.40.107:5060/udp (496 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258 TransactionClient#276: changed transaction state: T_Completed TransactionClient#271: End timeout expired SipProvider-5076: removing SipProviderListener: 673566785188@10.102.250.200-1-INVITE-10.102.250.200:5076-z9hG4bK76125254 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257, 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258, TransactionClient#271: changed transaction state: T_Terminated TransactionClient#275: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-11-REGISTER-10.102.250.200:5076-z9hG4bK82664257 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258, TransactionClient#275: changed transaction state: T_Terminated TransactionClient#276: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-12-REGISTER-10.102.250.200:5076-z9hG4bK92553258 SipProvider-5076: 1 listeners: INVITE, TransactionClient#276: changed transaction state: T_Terminated TransactionClient#277: id: 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259 TransactionClient#277: created TransactionClient#277: start TransactionClient#277: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:45:33.983 Thu 12 Feb 2009, 10.102.40.107:5060/udp (467 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:45:33.984 Thu 12 Feb 2009, 10.102.40.107:5060/udp (384 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259 TransactionClient#277: changed transaction state: T_Proceeding 18:45:33.991 Thu 12 Feb 2009, 10.102.40.107:5060/udp (523 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259 TransactionClient#277: changed transaction state: T_Completed TransactionClient#278: id: 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260 TransactionClient#278: created TransactionClient#278: start TransactionClient#278: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259, 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:45:33.994 Thu 12 Feb 2009, 10.102.40.107:5060/udp (657 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:45:33.995 Thu 12 Feb 2009, 10.102.40.107:5060/udp (384 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260 TransactionClient#278: changed transaction state: T_Proceeding 18:45:34.001 Thu 12 Feb 2009, 10.102.40.107:5060/udp (496 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260 TransactionClient#278: changed transaction state: T_Completed TransactionClient#277: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-13-REGISTER-10.102.250.200:5076-z9hG4bK34337259 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260, TransactionClient#277: changed transaction state: T_Terminated TransactionClient#278: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-14-REGISTER-10.102.250.200:5076-z9hG4bK06736260 SipProvider-5076: 1 listeners: INVITE, TransactionClient#278: changed transaction state: T_Terminated TransactionClient#279: id: 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261 TransactionClient#279: created TransactionClient#279: start TransactionClient#279: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:45:47.135 Thu 12 Feb 2009, 10.102.40.107:5060/udp (466 bytes): REGISTER sip:csi.it SIP/2.0, sent ExtendedInviteDialog#16: isWaiting - callState=1 18:45:47.138 Thu 12 Feb 2009, 10.102.40.107:5060/udp (384 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261 TransactionClient#279: changed transaction state: T_Proceeding 18:45:47.139 Thu 12 Feb 2009, 10.102.40.107:5060/udp (523 bytes): SIP/2.0 401 Unauthorized, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261 TransactionClient#279: changed transaction state: T_Completed TransactionClient#280: id: 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262 TransactionClient#280: created TransactionClient#280: start TransactionClient#280: changed transaction state: T_Trying SipProvider-5076: adding SipProviderListener: 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262 SipProvider-5076: 3 listeners: INVITE, 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262, 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261, SipProvider-5076: using transport udp SipProvider-5076: Resolving host address '10.102.40.107' SipProvider-5076: Sending message to udp:10.102.40.107:5060 18:45:47.142 Thu 12 Feb 2009, 10.102.40.107:5060/udp (656 bytes): REGISTER sip:csi.it SIP/2.0, sent 18:45:47.143 Thu 12 Feb 2009, 10.102.40.107:5060/udp (384 bytes): SIP/2.0 100 Trying, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262 TransactionClient#280: changed transaction state: T_Proceeding 18:45:47.147 Thu 12 Feb 2009, 10.102.40.107:5060/udp (422 bytes): SIP/2.0 200 OK, received SipProvider-5076: received new SIP message SipProvider-5076: DEBUG: transaction-id: 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262 SipProvider-5076: message passed to transaction: 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262 TransactionClient#280: changed transaction state: T_Completed SipProvider-5076: halt: SipProvider is going down SipProvider-5076: transport udp:null:5076 terminated TransactionClient#279: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-15-REGISTER-10.102.250.200:5076-z9hG4bK85214261 SipProvider-5076: 2 listeners: INVITE, 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262, TransactionClient#279: changed transaction state: T_Terminated TransactionClient#280: Clearing timeout expired SipProvider-5076: removing SipProviderListener: 512678085930@10.102.250.200-16-REGISTER-10.102.250.200:5076-z9hG4bK32624262 SipProvider-5076: 1 listeners: INVITE, TransactionClient#280: changed transaction state: T_Terminated SipProvider-5076: tcp server null terminated