Return to LanScape's home page Go back a page...       Active TopicsActive Topics   Display List of Forum MembersMember List   Knowledge Base SearchSearch   HelpHelp  RegisterRegister  LoginLogin

LanScape VOIP Media Engine™ - Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Subject Topic: Outgoing calls fails - Premature termination Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: May 31 2007 at 1:59pm | IP Logged Quote juice
Hi,

we are facing following problem, after running media engine based application for not really long, let say (10-20) minutes the media engine comes to the state that starts acting weird for all new outgoing calls.

And it goes following.

INVITE > Trying > Ringing > 200 OK > ACK and then for unknown reason sends BYE see the logs below.

EVENTS LOG:

Code:

[SIP_MESSAGE]: SipOutgoingCallInitializing : 299 : 62
[SIP_MESSAGE]: SipOutgoingCallStart : 299 : 64
[SIP_MESSAGE]: SipDialTone : 299 : 65
[SIP_MESSAGE]: SipDialing : 299 : 66
[SIP_MESSAGE]: SipSendInvite : 299 : 67
[SIP_MESSAGE]: SipModifySipMessage : -1 : 153
[SIP_MESSAGE]: SipStartOutgoingRing : 299 : 68
[SIP_MESSAGE]: SipModifySipMessage : -1 : 153
[SIP_MESSAGE]: SipModifySipMessage : -1 : 153
[SIP_MESSAGE]: SipReceivedProvisionalResponse : 299 : 69
[SIP_MESSAGE]: SipReceived100Trying : 299 : 70
[SIP_MESSAGE]: SipWaitForInviteOk : 299 : 76
[SIP_MESSAGE]: SipReceived180Ringing : 299 : 71
[SIP_MESSAGE]: SipModifySipMessage : -1 : 153
[SIP_MESSAGE]: SipInviteOkReceived : 299 : 77
[SIP_MESSAGE]: SipSendInviteAck : 299 : 78
[SIP_MESSAGE]: SipModifySipMessage : -1 : 153
[SIP_MESSAGE]: SipOutgoingCallConnected : 299 : 79
[SIP_MESSAGE]: SipSendBye : 299 : 108
[SIP_MESSAGE]: SipModifySipMessage : -1 : 153
[SIP_MESSAGE]: SipModifySipMessage : -1 : 153
[SIP_MESSAGE]: SipReceivedByeAck : 299 : 109
[SIP_MESSAGE]: SipCallComplete : 299 : 111
[SIP_MESSAGE]: SipOnHook : 299 : 59



SIP LOG:

Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#29486, 41344 Ms, To: >>>> 88.88.88.104:5060) >>>>
INVITE sip:100510010241p#@88.88.88.104 SIP/2.0
Via: SIP/2.0/UDP 77.77.77.101:5060;rport;branch=z9hG4bK046c2be6
From: MediaEngine <sip:user_2@77.77.77.101>;tag=46c3e73
To: <sip:100510010241p#@88.88.88.104>
Contact: <sip:user_2@77.77.77.101:5060>
Call-Id: 0dc5f35c-3935-4097-abd1-5b5852ec286e-00001ae8@77.77.77.101
CSeq: 7101897 INVITE
Max-Forwards: 70
Organization: 7D55132C-B684-464A-A4F6-92A4B7DCBD94
Content-Length: 284
User-Agent: LanScape VOIP Media Engine/5.12.3.30 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=user_2 74191500 74191500 IN IP4 77.77.77.101
s=LanScape
c=IN IP4 77.77.77.101
t=0 0
m=audio 8344 RTP/AVP 0 8 124 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:124 PCM/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#38623, 41344 Ms, From: 88.88.88.104:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 77.77.77.101:5060;received=77.77.77.101;rport=5060;branch=z9 hG4bK046c2be6
From: MediaEngine <sip:user_2@77.77.77.101>;tag=46c3e73
To: <sip:100510010241p#@88.88.88.104>
Call-Id: 0dc5f35c-3935-4097-abd1-5b5852ec286e-00001ae8@77.77.77.101
CSeq: 7101897 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.30 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#38624, 15 Ms, From: 88.88.88.104:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 77.77.77.101:5060;received=77.77.77.101;rport=5060;branch=z9 hG4bK046c2be6
From: MediaEngine <sip:user_2@77.77.77.101>;tag=46c3e73
To: <sip:100510010241p#@88.88.88.104>;tag=16b22506
Call-Id: 0dc5f35c-3935-4097-abd1-5b5852ec286e-00001ae8@77.77.77.101
CSeq: 7101897 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.30 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#38625, 250 Ms, From: 88.88.88.104:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 77.77.77.101:5060;received=77.77.77.101;rport=5060;branch=z9 hG4bK046c2be6
From: MediaEngine <sip:user_2@77.77.77.101>;tag=46c3e73
To: <sip:100510010241p#@88.88.88.104>;tag=16b22506
Call-Id: 0dc5f35c-3935-4097-abd1-5b5852ec286e-00001ae8@77.77.77.101
CSeq: 7101897 INVITE
Contact: <sip:MediaEngine@88.88.88.104:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.30 (www.LanScapeCorp.com)
Content-Length: 177
Content-Type: application/sdp

v=0
o=LanScape 3389575519 3389575519 IN IP4 88.88.88.104
s=LanScape
c=IN IP4 88.88.88.104
t=0 0
m=audio 8418 RTP/AVP 0
a=rtpmap:0 PCMU/8000/1
a=sendrecv a=ptime:20



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#29487, 343 Ms, To: >>>> 88.88.88.104:5060) >>>>
ACK sip:100510010241p#@88.88.88.104 SIP/2.0
Via: SIP/2.0/UDP 77.77.77.101:5060;received=77.77.77.101;rport=5060;branch=z9 hG4bK046c2be6
From: MediaEngine <sip:user_2@77.77.77.101>;tag=46c3e73
To: <sip:100510010241p#@88.88.88.104>;tag=16b22506
Call-Id: 0dc5f35c-3935-4097-abd1-5b5852ec286e-00001ae8@77.77.77.101
CSeq: 7101897 ACK
Max-Forwards: 70
Route: <sip:MediaEngine@88.88.88.104>
User-Agent: LanScape VOIP Media Engine/5.12.3.30 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#29488, 16 Ms, To: >>>> 88.88.88.104:5060) >>>>
BYE sip:MediaEngine@88.88.88.104 SIP/2.0
Via: SIP/2.0/UDP 77.77.77.101:5060;rport;branch=z9hG4bK046c4985
From: MediaEngine <sip:user_2@77.77.77.101>;tag=46c3e73
To: <sip:100510010241p#@88.88.88.104>;tag=16b22506
Call-Id: 0dc5f35c-3935-4097-abd1-5b5852ec286e-00001ae8@77.77.77.101
CSeq: 7101898 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.30 (www.LanScapeCorp.com)
Content-Length: 0



Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: May 31 2007 at 2:32pm | IP Logged Quote juice
there also very similar issue we have noticed, the outgoing calls for unknown reason goes from SipDialing immediately to SipOnHook

17:48:11: [SIP_MESSAGE]: SipOutgoingCallInitializing : 179 : 62
17:48:11: [SIP_MESSAGE]: SipModifySipMessage : -1 : 153
17:48:11: [SIP_MESSAGE]: SipOutgoingCallStart : 179 : 64
17:48:11: [SIP_MESSAGE]: SipDialTone : 179 : 65
17:48:11: [SIP_MESSAGE]: SipDialing : 179 : 66
17:48:11: [SIP_MESSAGE]: SipOnHook : 179 : 59
Back to Top View juice's Profile Search for other posts by juice
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 04 2007 at 10:47am | IP Logged Quote support
Hi Andrew,

Thanks for waiting for this response.

We understand that your company will be starting an annual support contract with us. That is good. It will give us much more freedom to work together. We can tackle this issue as soon as we get the support contract started.

Support

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: June 04 2007 at 2:03pm | IP Logged Quote juice
Hi there,

Do I understand correctly that after buying the 512 line engine and finishing our development it can't be deployed since it's crashing. And the only way to fix your bug is to pay more? That's interesting. Will it get more expensive with every bug we discover? ;-)

Andrew
Back to Top View juice's Profile Search for other posts by juice
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 05 2007 at 10:33am | IP Logged Quote support
Hi Juice,

We deeply regret if you are experiencing any problems. We are ready to assist your team as soon as we can. We know of your application and want you to succeed. This is not the first time a customer has developed this type of application using the media engine. If there is an issue, it’s probably simple to get around or resolve. However, we hope you understand that this free support area must be serviced after we handle any/all paid customer support issues.

If you locate any bugs, try to find a workaround until we can assist. We can tell that you are a seasoned software developer and understand what you are doing. That is good. Make absolutely sure there are no bugs or “wild pointers” in your application code that may be affecting the behavior of the media engine. When in doubt, use Compuware DevPartner to analyze your code and to locate possible causes. Compuware DevPartner can be found at this URL:

http://www.compuware.com/products/devpartner/default.htm

Regarding your statement about “paying more”: Your company agreed to enter into a paid support contract with us at least 6 months ago and we have seen no activity regarding this. All the while we have been updating your company with software. We must be fair regarding our other paying customers. This is all we can state in this public support forum. For further information, we ask that you and your CTO please contact our support group so that we may assist you expeditiously.

Thank you,

Support

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 07 2007 at 10:58am | IP Logged Quote support
Hi Andrew,

You have another post that describes a crash situation you have been experiencing:

Internal Crash/Break inside DLL

This may be a side effect of what is causing the crash. Please see the bottom on the above post for more info.

Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 06 2007 at 12:37pm | IP Logged Quote juice
I know we posted in the other thread that the issue was resolved as far as we saw. However, it appears to have resurfaced. In our tests, with thousands of test calls completed, we did not see the issue. However, local tests do not easily recreate real world usage. We again our seeing errors with this related to the previous post. SipOutgoingCallConnected, immediately followed by SipSendBye. We are 100% positive we have not called terminate call with the time period of those two messages - which happen right after each other. However, something weird, is that it seems to be line related, where some lines still connect fine, and another fails. I.e lines 0-2 seem to connect, but line 3 generates the above error. This is with the absolute latest build.

Something which we've recently seen in the debugger output window, which may or may not be related (also, not sure if it showed up in the last build or not), is a strange looking exception happening within lanscape. This happens immediately after starting the engine, whenever an outgoing call is connected (even on successful connections):
First-chance exception at 0x77e4bee7 in Application_d.exe: 0x000006D9: There are no more endpoints available from the endpoint mapper.

Which happens right after these messages were received:
[SIP_MESSAGE]: SipModifySipMessage : -1 : 161 : 0
[SIP_MESSAGE]: SipInviteOkReceived : 309 : 81 : 2
[SIP_MESSAGE]: SipSendInviteAck : 309 : 82 : 2
[SIP_MESSAGE]: SipModifySipMessage : 309 : 161 : 0
[SIP_MESSAGE]: SipOutgoingCallConnected : 309 : 83 : 2

And, when catching the location where that exception is thrown:
kernel32.dll!77e4bee7()      
[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]     
kernel32.dll!77e4bee7()      
rpcrt4.dll!77c7f5d1()      
rpcrt4.dll!77c7f201()      
rpcrt4.dll!77c61e37()      
rpcrt4.dll!77c62042()      
rpcrt4.dll!77ce30e4()      
ntdll.dll!7c83dd74()      
ntdll.dll!7c83e76e()      
ntdll.dll!7c83e7f5()      
ntdll.dll!7c878c6b()      
ntdll.dll!7c83e7f5()      
ntdll.dll!7c878c6b()      
ntdll.dll!7c83e7f5()      
ntdll.dll!7c83e7f5()      
ntdll.dll!7c829f59()      
ntdll.dll!7c83dd74()      
ntdll.dll!7c83d97a()      
ntdll.dll!7c82a0fc()      
ntdll.dll!7c83e7f5()      
ntdll.dll!7c83e7f5()      
ntdll.dll!7c83e5d0()      
ntdll.dll!7c829f59()      
mswsock.dll!71b24c04()      
mswsock.dll!71b24c16()      
ntdll.dll!7c83d97a()      
wshtcpip.dll!71ae14fc()      
mswsock.dll!71b24fff()      
mswsock.dll!71b252ae()      
mswsock.dll!71b252e2()      
hnetcfg.dll!5f2a2fba()      
hnetcfg.dll!5f29c6a6()      
kernel32.dll!77e61d43()      
ntdll.dll!7c826fcb()      
mswsock.dll!71b21d8e()      
mswsock.dll!71b24fff()      
mswsock.dll!71b25846()      
ws2_32.dll!71c043db()      
LMEVoip.dll!10079c1b()      
LMEVoip.dll!10079baf()      
LMEVoip.dll!10079ad7()      
LMEVoip.dll!1001554b()      
LMEVoip.dll!100024b9()      
LMEVoip.dll!10021522()      
LMEVoip.dll!100e659c()      
LMEVoip.dll!10021b50()      
LMEVoip.dll!1002dbc7()      
kernel32.dll!77e5be5c()      
LMEVoip.dll!100dcbe8()      
LMEVoip.dll!1002db9d()      
LMEVoip.dll!1001e62e()      

Back to Top View juice's Profile Search for other posts by juice
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: August 08 2007 at 10:42am | IP Logged Quote support
Juice,

We have to get to the bottom of this. Working together we will. Let’s take the easy item first…

First chance exception:
First-chance exceptions are normal and do not necessarily indicate an error. The operating system can throw and catch its own exceptions internally as part of its normal operation. At this point in time, we have not seen this exception during our development and testing. We assume you are still running on Windows 2003 Server. We test for that OS but do not develop using it. We will look into it further as time permits. You may want to have one of your dev guys look at the following Microsoft doc:

How to troubleshoot RPC Endpoint Mapper errors:
http://support.microsoft.com/?id=839880

The "No more endpoints available" error message means the RPC Endpoint Mapper was not able to use a port greater than 1024 for a service that runs over RPC (RPC Endpoint Mapper itself runs on port 135). RPC can use ports up to 65535 but by default, all versions of Windows use only ports in the range of 1024-5000. If your VOIP application is using UDP ports in the range that RPC is using, that may be the problem.

If we Google for the phrase “There are no more endpoints available from the endpoint mapper”, we see many web and news group hits. This leads us to believe that it is probably a normal Windows RPC occurrence. The call stack also seems to indicate this seeing the first chance exception is not coming from the media engine directly but from deep within the host’s RPC runtime support.

Note: One thing we are working on for a future release is to have available crash dump support in the media engine. This way if any catastrophic exceptions occur, you will be able to send us a crash dump file and we will be able to load that info into a debugger with the release product image and see the exact line that blew up. This info will also allow us to take a stack trace like the one you posted and view the last call in the media engine that triggered the eventual first chance exception like the one you reported.


SipOutgoingCallConnected immediately followed by SipSendBye:
We will go back and look at this. We agree, something weird must be going on. We have hammer tested this release version in many new ways and have not seen the original problem after the last software updates. We tested over 2.5 million calls on each individual test server where we performed hammer testing. The key to successfully locating this issue will be to isolate a test scenario that allows us to reproduce the condition here in our lab. Obviously our current test scenarios have not uncovered all remnants of this issue.

If your team can quickly code up a C++ console app that exhibits the issue and represents the manner in which you are using the media engine API, that would give us the quickest route to a solution.

Question 1:
When you detect the “SipOutgoingCallConnected immediately followed by SipSendBye” condition, is your VOIP app only making outgoing calls? This is important.

Another useful aid in solving this is to use the undocumented API procs:

SetCallStateRecording()
GetNumRecordedCallStates()
GetRecordedCallStates()

To get all the call states a phone line transition through as a call is being processed. If your VOIP app determines that the outgoing call has immediately terminated, wait for the final On-hook state and then use the above three API procs to access the call state history for the phone line. Dump that call states for the phone line to a file and post that info. The recorded call state info may help us locate a possible call error with greater ease. We will send you via email an updated Developer’s Reference help file that documents these 3 APIs.

Question 2:
Is your VOIP app calling the MakeCall() APIs synchronously or asynchronously?


In the mean time, any further info you can forward would be beneficial.



Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 13 2007 at 2:53pm | IP Logged Quote juice
Hello, we would have responded sooner, but to prevent the issue, we periodically reset the system. However, we again saw the error this weekend. The following code block shows the complete line state of a stuck line. Note, this particular line failed with SipIncomingCallConnected followed by SipSendBye. Another line failed with the same, and one other line failed with SipOutgoingCallConnected. We also added some code to try to busy out a line when this condition was detected, however, it took two tries to get this first line to busy out.

Call State log 1:
Code:

[1186876304]: [LINE_HISTORY] : 1 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186876770]: [LINE_HISTORY] : 2 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186877038]: [LINE_HISTORY] : 3 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186877118]: [LINE_HISTORY] : 4 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186878363]: [LINE_HISTORY] : 5 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186878742]: [LINE_HISTORY] : 6 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186878855]: [LINE_HISTORY] : 7 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186878945]: [LINE_HISTORY] : 8 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipReceivedInviteAck SipOnHook
[1186879115]: [LINE_HISTORY] : 9 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186879916]: [LINE_HISTORY] : 10 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186879964]: [LINE_HISTORY] : 11 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186880148]: [LINE_HISTORY] : 12 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186880629]: [LINE_HISTORY] : 13 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186880922]: [LINE_HISTORY] : 15 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186880936]: [LINE_HISTORY] : 16 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186881081]: [LINE_HISTORY] : 17 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186881881]: [LINE_HISTORY] : 18 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186883152]: [LINE_HISTORY] : 19 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186883589]: [LINE_HISTORY] : 20 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186883740]: [LINE_HISTORY] : 21 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186885592]: [LINE_HISTORY] : 22 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186887653]: [LINE_HISTORY] : 23 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186888720]: [LINE_HISTORY] : 24 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186890187]: [LINE_HISTORY] : 25 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186892178]: [LINE_HISTORY] : 26 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186893134]: [LINE_HISTORY] : 27 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186893784]: [LINE_HISTORY] : 28 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186893885]: [LINE_HISTORY] : 29 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186894130]: [LINE_HISTORY] : 30 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186894332]: [LINE_HISTORY] : 31 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186894639]: [LINE_HISTORY] : 32 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186894654]: [LINE_HISTORY] : 33 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186894791]: [LINE_HISTORY] : 34 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186894853]: [LINE_HISTORY] : 35 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186895512]: [LINE_HISTORY] : 36 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186895783]: [LINE_HISTORY] : 37 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186895866]: [LINE_HISTORY] : 38 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186895932]: [LINE_HISTORY] : 39 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186898748]: [LINE_HISTORY] : 40 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186899230]: [LINE_HISTORY] : 41 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186899359]: [LINE_HISTORY] : 42 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186899530]: [LINE_HISTORY] : 43 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186900664]: [LINE_HISTORY] : 44 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186901074]: [LINE_HISTORY] : 45 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186901113]: [LINE_HISTORY] : 46 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186901173]: [LINE_HISTORY] : 47 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186901230]: [LINE_HISTORY] : 48 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186901270]: [LINE_HISTORY] : 49 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186901315]: [LINE_HISTORY] : 50 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186901436]: [LINE_HISTORY] : 51 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186901462]: [LINE_HISTORY] : 52 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186901494]: [LINE_HISTORY] : 53 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186902308]: [LINE_HISTORY] : 54 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186902478]: [LINE_HISTORY] : 55 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186903909]: [LINE_HISTORY] : 56 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186904017]: [LINE_HISTORY] : 57 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186904087]: [LINE_HISTORY] : 58 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnswerTimeout SipOnHook
[1186904165]: [LINE_HISTORY] : 59 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnswerTimeout SipOnHook
[1186904205]: [LINE_HISTORY] : 60 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipInviteAckNotReceived SipOnHook
[1186904215]: [LINE_HISTORY] : 61 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186904391]: [LINE_HISTORY] : 62 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186904453]: [LINE_HISTORY] : 63 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186904611]: [LINE_HISTORY] : 64 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186904623]: [LINE_HISTORY] : 65 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipInviteAckNotReceived SipOnHook
[1186904687]: [LINE_HISTORY] : 66 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186904770]: [LINE_HISTORY] : 67 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186904827]: [LINE_HISTORY] : 68 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186906861]: [LINE_HISTORY] : 69 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186906939]: [LINE_HISTORY] : 70 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186906997]: [LINE_HISTORY] : 71 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186907206]: [LINE_HISTORY] : 72 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907256]: [LINE_HISTORY] : 73 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907277]: [LINE_HISTORY] : 74 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907303]: [LINE_HISTORY] : 75 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907316]: [LINE_HISTORY] : 76 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook SipDialTone SipOffHook
[1186907369]: [LINE_HISTORY] : 77 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook SipDialTone SipOffHook SipOnHook
[1186907453]: [LINE_HISTORY] : 78 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186907479]: [LINE_HISTORY] : 79 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186907488]: [LINE_HISTORY] : 80 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186907512]: [LINE_HISTORY] : 81 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907523]: [LINE_HISTORY] : 82 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907542]: [LINE_HISTORY] : 83 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907558]: [LINE_HISTORY] : 84 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907569]: [LINE_HISTORY] : 85 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907668]: [LINE_HISTORY] : 86 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186907711]: [LINE_HISTORY] : 87 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipInviteAckNotReceived SipOnHook
[1186907790]: [LINE_HISTORY] : 88 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186907806]: [LINE_HISTORY] : 89 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186907824]: [LINE_HISTORY] : 90 Line#: 0 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook SipBusyOutOn SipBusyOut

Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 13 2007 at 2:57pm | IP Logged Quote juice
And, same log, a second line later showed this state:

Call State log 2:
Code:

[1186878507]: [LINE_HISTORY] : 1 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186884072]: [LINE_HISTORY] : 2 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186884571]: [LINE_HISTORY] : 3 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186884670]: [LINE_HISTORY] : 4 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186894114]: [LINE_HISTORY] : 5 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186894138]: [LINE_HISTORY] : 6 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186899070]: [LINE_HISTORY] : 7 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186899145]: [LINE_HISTORY] : 8 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall
[1186899169]: [LINE_HISTORY] : 9 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186899476]: [LINE_HISTORY] : 10 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186899794]: [LINE_HISTORY] : 11 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186900025]: [LINE_HISTORY] : 12 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186900176]: [LINE_HISTORY] : 13 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186900204]: [LINE_HISTORY] : 14 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186900686]: [LINE_HISTORY] : 15 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186900911]: [LINE_HISTORY] : 16 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186901156]: [LINE_HISTORY] : 17 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186901197]: [LINE_HISTORY] : 18 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186901250]: [LINE_HISTORY] : 19 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186902079]: [LINE_HISTORY] : 20 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186902585]: [LINE_HISTORY] : 21 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186904046]: [LINE_HISTORY] : 22 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186904108]: [LINE_HISTORY] : 23 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186904205]: [LINE_HISTORY] : 24 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186904216]: [LINE_HISTORY] : 25 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186904443]: [LINE_HISTORY] : 26 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnswerTimeout SipOnHook
[1186904690]: [LINE_HISTORY] : 27 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186904768]: [LINE_HISTORY] : 28 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186904842]: [LINE_HISTORY] : 29 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186905057]: [LINE_HISTORY] : 30 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186905096]: [LINE_HISTORY] : 31 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186905241]: [LINE_HISTORY] : 32 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186905355]: [LINE_HISTORY] : 33 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186905364]: [LINE_HISTORY] : 34 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186905536]: [LINE_HISTORY] : 35 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186907360]: [LINE_HISTORY] : 36 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186907463]: [LINE_HISTORY] : 37 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipSendBye SipByeAckNotReceived SipCallComplete SipOnHook
[1186907483]: [LINE_HISTORY] : 38 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186907506]: [LINE_HISTORY] : 39 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipInviteAckNotReceived SipOnHook
[1186907515]: [LINE_HISTORY] : 40 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186907606]: [LINE_HISTORY] : 41 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipInviteAckNotReceived SipOnHook
[1186907698]: [LINE_HISTORY] : 42 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186907849]: [LINE_HISTORY] : 43 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRingdRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186907880]: [LINE_HISTORY] : 44 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipInviteAckNotReceived SipOnHook
[1186907910]: [LINE_HISTORY] : 45 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnswerTimeout SipOnHook
[1186907978]: [LINE_HISTORY] : 46 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186908126]: [LINE_HISTORY] : 48 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186908187]: [LINE_HISTORY] : 49 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnswerTimeout SipOnHook
[1186908232]: [LINE_HISTORY] : 50 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSe
[1186908294]: [LINE_HISTORY] : 51 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186908323]: [LINE_HISTORY] : 52 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186908337]: [LINE_HISTORY] : 53 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete
[1186908375]: [LINE_HISTORY] : 54 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186908397]: [LINE_HISTORY] : 55 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186908485]: [LINE_HISTORY] : 56 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186908502]: [LINE_HISTORY] : 57 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipCallCanceled SipOnHook
[1186908559]: [LINE_HISTORY] : 58 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186908787]: [LINE_HISTORY] : 59 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186908995]: [LINE_HISTORY] : 60 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186909075]: [LINE_HISTORY] : 61 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnswerTimeout SipOnHook
[1186909129]: [LINE_HISTORY] : 62 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186909153]: [LINE_HISTORY] : 63 Line#: 2 : SipIncomingCallStart SipSendTrying SipSendRinging SipStartIncomingRing SipOkToAnswerCall SipAnsweringCall SipSend200Ok SipReceivedInviteAck SipIncomingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook

Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 13 2007 at 3:08pm | IP Logged Quote juice
And, this one happened with Outgoing call connection. Seems to be around the 19th usage of the line it got stuck.

Call State log 3:
Code:

[1186901547]: [LINE_HISTORY] : 1 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186901573]: [LINE_HISTORY] : 2 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipFarEndError SipOnHook
[1186901575]: [LINE_HISTORY] : 3 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186901586]: [LINE_HISTORY] : 4 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipFarEndError SipOnHook
[1186901587]: [LINE_HISTORY] : 5 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipCallCanceled SipOnHook
[1186901597]: [LINE_HISTORY] : 6 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipFarEndError SipOnHook
[1186901599]: [LINE_HISTORY] : 7 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186903205]: [LINE_HISTORY] : 8 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived183SessionProgress SipFarEndError SipOnHook
[1186903342]: [LINE_HISTORY] : 9 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived183SessionProgress SipFarEndError SipOnHook
[1186903800]: [LINE_HISTORY] : 10 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186907369]: [LINE_HISTORY] : 11 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186907403]: [LINE_HISTORY] : 12 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipFarEndError SipOnHook
[1186907416]: [LINE_HISTORY] : 13 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipInCall SipByeReceived SipSendByeAck SipCallComplete SipOnHook
[1186907473]: [LINE_HISTORY] : 14 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipCallCanceled SipOnHook
[1186907481]: [LINE_HISTORY] : 15 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipCallCanceled SipOnHook
[1186907503]: [LINE_HISTORY] : 16 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186907510]: [LINE_HISTORY] : 17 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186908003]: [LINE_HISTORY] : 18 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipInCall SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186912165]: [LINE_HISTORY] : 19 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186912190]: [LINE_HISTORY] : 20 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186921581]: [LINE_HISTORY] : 21 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186921603]: [LINE_HISTORY] : 22 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186921623]: [LINE_HISTORY] : 23 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipFarEndError SipOnHook
[1186921636]: [LINE_HISTORY] : 24 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipFarEndError SipOnHook
[1186921666]: [LINE_HISTORY] : 25 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipCallCanceled SipOnHook
[1186921687]: [LINE_HISTORY] : 26 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipFarEndError SipOnHook
[1186921711]: [LINE_HISTORY] : 27 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186921765]: [LINE_HISTORY] : 28 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186921793]: [LINE_HISTORY] : 29 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186921838]: [LINE_HISTORY] : 30 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived180Ringing SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook
[1186925874]: [LINE_HISTORY] : 31 Line#: 291 : SipOutgoingCallStart SipDialTone SipDialing SipSendInvite SipStartOutgoingRing SipReceivedProvisionalResponse SipReceived100Trying SipWaitForInviteOk SipReceived183SessionProgress SipInviteOkReceived SipSendInviteAck SipOutgoingCallConnected SipSendBye SipReceivedByeAck SipCallComplete SipOnHook SipBusyOutOn SipBusyOut


We are certain that these lines were not terminated as a result of a request to terminateLine. We also do not see a pattern. Hopefully, this helps to get this issue fixed. Also, we have Sip logs too, but they are difficult to match against a phone line number. Perhaps, your Sip logging could also show the phone line number, and Linux timestamps so that a complete recreation of all events could easily be done - to allow the sip messages to flow into the system the same way they came before when the issue appeared.
Back to Top View juice's Profile Search for other posts by juice
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: August 15 2007 at 10:51am | IP Logged Quote support
juice,

We are reviewing your posted info. We will repost with questions if required.

Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: August 16 2007 at 11:43am | IP Logged Quote support
Juice,

We need additional info from you. We have edited your call state logs in this forum. We simply labeled them “Call State log 1:“, “Call State log 2:“, etc.

We are currently looking at the call states from “Call State log 1:“. We want to be able to simulate your app and media engine setup as closely as possible. This is proving a bit difficult. Since we started this morning, we have pumped roughly 235,000 calls through a multi-lined media engine and have not generated any crashed or call state errors. We are evidently missing something important.

From another post, this is your setup:

User Agent <--> Sip proxy <--> B2BUA (Media Engine as PSTN gateway)


Question 1:
When you are performing your testing, what are you using to generate the User Agent call traffic?

Question 2:
For “Call State log 1:“, did your testing only generate call traffic in one direction? In other words, was all SIP call traffic initiated by the user agent(s)?

Question 3:
Is it possible for your team to supply us with your BTBUA binary image? We can use this directly for testing with the debug build of the media engine.

Question 4:
In an effort to resolve this ASAP, we may want to give you access to our VOIP system at our location so that we may speak with you directly. Where are you located geographically (time zone) and are you willing to do this?


The main goal is to understand what is occurring in your app and resolve the issue as soon as possible. Our CTO has expressed the desire to speak directly with you during this process.


Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 16 2007 at 7:28pm | IP Logged Quote juice
Question 1:
During testing, we are not able to reproduce this error. Only under regular call traffic from various user agents and scenarios have we seen this issue. As you, when just performing some standard testing (using tools such as SIPp), the media engine answers every call as expected, incoming and outgoing.

It seems that testing environments are not able to adequately reproduce the environment where this happens. In real world usage, there are of course numerous far end errors that happen, many different user agents, different from's/to's, call ids, destination gateways, timeouts, etc which are hard to reproduce in a test environment. If it helps, this seems to happen anywhere from 4 hours to 24+ hours after application start.

Question 2:
I think maybe I did not clearly express what the logs above mean. They are just a few lines out of many in a real world application that were being used. I can send you a complete call history for all lines that were being used for the lifetime of the application if you need - i.e. if you think other line states might affect these few bad lines.

Question 3:
This is a tricky question. Mainly, our application relies on an integrated environment (database backend, scripting environment, Sip Proxy, etc) to function. We will, however, look into the feasibility of providing you with a similar environment. Though, by even reducing a test app to some basic functionality, the odds of seeing this behavior would likely be slim.

Question 4:
Some sort of real time communication would definitely be appreciated. We cannot set a firm answer on this today, but will get back with you first thing in the morning (Pacific Standard Time) with an answer.

Again, thanks for being determined to help us find an answer for this issue. We look forward to working together to solve this problem.
Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 17 2007 at 2:35pm | IP Logged Quote juice
In regards, for question 3:

We have thought hard about this, and it is not logistically possibly to provide an environment to reproduce this outside of our running environment. The ideal solution, that we can think of, is perhaps providing lots of debugging output from the SipEngine into the Sip log, or a seperate log that would provide you much more details on the internal states. Perhaps logging all Media Engine calls that we made into your system, as well as parameters, or what ever you feel is appropriate.

There is a possibility, that we could also arrange a remote debugging session. Not 100% positive yet if we can set this up. But this could allow our debug application (source/pdb/etc) to stay protected, while allowing your debugging build (source/pdb/etc) to also stay protected with you. You would simply need to provide us with a debug build, and we could run the application for a period of time until we see the issue arise, after which you should be able to connect remotely to the system to step into the debug dll on our end with your source on your end. Again, I'm not sure if this is feasible yet, but if it was, this could prove to be the best bet.

However, for now, I think excessive logging would help isolate the issue. If you could provide us with a build that did this we would be more than willing to use this dll and report the logs as soon as the issue appears.

Or, if you have any other thoughts we are open to discuss them.

In regards to question 4, I still cannot say when we are available for more real time communication. Currently, we are in process of a large infrastructure change and do not have available time to focus on this issue exclusively. Hopefully, early next week... but, we will have to get back to you.

Again, thanks for your attention on this matter.
Back to Top View juice's Profile Search for other posts by juice
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: August 17 2007 at 2:57pm | IP Logged Quote support
juice,

Thanks for the info, we are also thinking about the appropriate path. Your points are well taken.

We are ramping down for the day so we will "get back in the saddle" on Monday.

Support

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: August 22 2007 at 9:29am | IP Logged Quote support
Hi juice,

Thanks for waiting as we digested your posted log data and your “monster” VOIP Media Engine SIP log you sent us. We worked on this over the weekend and the past few days. We believe we have located and fixed the problem. We took your SIP log and set up a mirror environment in our lab – to synthesize your deployment as close as possible. We have the ability to “compile” your sip log into command files that are then used by our other test apps to produce call flows that are basically identical to the ones shown in your SIP log. Then we just let the call scenarios run and run and run….

This problem was very elusive and very hard to duplicate. We did finally manage to put together a test environment with proper system loading that allowed us to experience the premature call termination as you reported. We used a 300 line media engine to simulate your media engine based B2BUA. So other users reading this can get a feel for what this forum thread is about, we will summarize:

The problem: Premature call termination
Premature call termination was detected in customer’s B2BUA application that uses a 512 line VOIP Media Engine. Premature call termination was sporadic and occurred for both incoming and outgoing calls. Normal media engine state transitions for calls are as follows:

Code:

Answering an incoming call:

SipIncomingCallStart
SipSendTrying
SipSendRinging
SipStartIncomingRing
SipOkToAnswerCall
SipAnsweringCall
SipSend200Ok
SipReceivedInviteAck
SipIncomingCallConnected
SipInCall



Code:

Making an outgoing call:

SipOutgoingCallStart
SipDialTone
SipDialing
SipSendInvite
SipStartOutgoingRing
SipReceivedProvisionalResponse
SipReceived100Trying
SipWaitForInviteOk
SipReceived100Trying
SipReceived180Ringing
SipInviteOkReceived
SipSendInviteAck
SipOutgoingCallConnected
SipInCall



Note that for both calls, the final call state is SipInCall. The problem that was experienced caused the media engine to not enter the SipInCall state but enter directly into the SipSendBye state which signals that call termination is under way.


Test results:
The cause of this problem is due to three factors:

1) The total number of calls being processed.
2) How quickly a call is started and then terminated.
3) Overall operating system loading.

Internally inside the media engine, the rtp receiver “start procedure” was not waiting for the RTP receiver thread to enter into the non blocking state before it returned. This would cause problems if the call is quickly terminated when the system is managing many calls and is under heavy load. Because the RTP receiver thread may not enter the non blocking state before the “stop RTP” procedure is called, RTP receiver logic could be left in an indeterminate state when stopping RTP. Once the condition is reached, subsequent IN and OUT calls would go from the “call connected” state directly to the "sending BYE" state because the start RTP logic would detect that RTP is already running and should not be. This in effect makes the phone line appear to be in a "stuck" error condition. To make matters worse, the media engine did not report this condition as an error to the VOIP application – it simply would terminate the call.

Solution:
The media engine has been updated to handle the above scenario without errors.

The media engine will also send the SipRtpFatalStartError phone line event to the VOIP application if it detects any unhandled RTP related error during call starts.




Juice, you can download a time bombed test DLL image from your support FTP account. Make sure to rebuild your application using the updated SipTelephonyApi.h and LMEVoip.lib files. Let us know your test results.

We will be conducting additional testing here regarding this issue and to monitor any abnormal call states of the media engine. We just wanted to get you this update as soon as we could.

Thanks,


Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 23 2007 at 11:55am | IP Logged Quote juice
This news is extremely good. We will test the new build as soon as possible. Thanks for working hard on this matter. Your above description seems to perfectly describe the issue. There was no discernible pattern we could see, and a thread timing issue that happens during (rare) certain sequence of events does definitely fits the bill.

Thanks again.
Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 31 2007 at 2:10pm | IP Logged Quote juice
Ok, we set up a test environment now and are testing the recent build now. We will report back any findings. There is one small thing which we have seen with the new build, though, cannot say if the problem is at all with Lanscape.

With the test build, we have seen more InviteAckNotReceived messages popping up then we have seen in our network before. Trying to rule out network issues, we set up a simply test tool to respond 100, 180, 200 ok, and on the other side the tool to generate invites and listen for those messages. Not one time did a 200 ok fail to make it to the other side. But, we have seen this on several occasions with the Lanscape enabled app. But, packet sniffing shows us that the 200 message did indeed go out to the NIC from Lanscape engine... But, on the other end, we never saw it reach us (the packet looked perfect - correct IP/port/etc). This is likely an issue with our router or the server in general I imagine, but weird how it never happened with test tool. I only mention because it is something that just started happening with recent build (coincidence I really think).

Anyway, we will keep you posted. I am very hopeful that this issue will be resolved with this build.

Thanks
Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: August 31 2007 at 3:10pm | IP Logged Quote juice
In regards to my last comment. I think the Invite Not received are just typical behavior with the current Sip implementation in Lanscape. Testing with the old build shows the same thing pop up occasioanlly (although, less frequent, just unlucky sometimes). I think maybe Lanscape needs to retransmit certain messages like this instead of just ending the call or ignoring the lost message. But, that's another thread/topic I think. For now, resolving the current issue of stuck lines is far more important.

Back to Top View juice's Profile Search for other posts by juice
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: September 07 2007 at 1:01pm | IP Logged Quote juice
Hello Support,

We are very pleased with the results from our testing with this latest build. We have seen no re-occurrences of stuck lines. We are ready to go forward with a final release that contains this fix.

Additionally, it would be excellent if this new build would contain access to the CallID information we spoke about in the other thread. As it is very important to allow us to provide additionally information when tracking issues and line states from INVITE to BYE. This information will hopefully speed up the time from reporting of problems to the final fix of the issue, since all line information will be known.

Thanks.
Back to Top View juice's Profile Search for other posts by juice
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 07 2007 at 2:32pm | IP Logged Quote support
Hi Andrew,

Thanks for the latest feedback. We have been wondering how your test results were progressing. The esoteric premature call termination should be resolved at this point and to ensure that it is, we are continuing testing at this end. Test results here are also favorable.

We are very busy here and have not immediately responded to all of your last 4-5 posts. Don’t worry though, we have reviewed all your posts and have noted all suggestions.

What we will probably do is review your posts again and figure out how we can implement some of your suggestions quickly. There are a few other customers that have similar requests so we will try to roll all those requests into the next release. Anything we can do to the API that will make support and debugging VOIP apps easier we will do. Not a problem at all. We will post to all your other open threads as soon as we can,

Thanks,


Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: September 18 2007 at 4:05pm | IP Logged Quote juice
Hello Support,

We are under the impression that the current release we received is under a time restriction after which it will cease to function. We are not sure when the deadline for it to stop working is, so we are hoping to hear some good news about when the next version will be available.

Thanks
Back to Top View juice's Profile Search for other posts by juice
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 19 2007 at 6:45am | IP Logged Quote support
Hi Juice,

We are satisfied that the premature call termination bug for high line density deployments has been fixed. If your tests show the same, please confirm this to us so that we can schedule your update. Your current build is OK until the end of this year.

Thanks,

Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
juice
Vetran
Vetran


Joined: December 05 2006
Location: United States
Posts: 139
Posted: September 21 2007 at 11:36pm | IP Logged Quote juice
Hello Support,

we've run days of tests and did not notice any problems, please let us know when we could schedule an update.

Thanks.
Back to Top View juice's Profile Search for other posts by juice
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum





Contact LanScape Hear what the Lawyers have to say How youm may use this site Read your privacy rights