| Author |
|
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: June 01 2007 at 4:36pm | IP Logged
|
|
|
In the following scenario, a Bye message is ignored by LanScape Voip Engine:
SipIncomingCallStart : 0 : 80
SipIncomingCallInitialized : 0 : 81
SipSendTrying : 0 : 84
SipModifySipMessage : -1 : 153
SipSendRinging : 0 : 85
SipModifySipMessage : -1 : 153
SipStartIncomingRing : 0 : 83
SipOkToAnswerCall : 0 : 87
At this point, we have not yet taken the incoming call off hook, as we start another connecting leg going out, and we want the incoming caller to still get ringing.
SipOutgoingCallInitializing : 249 : 62
SipOutgoingCallStart : 249 : 64
SipDialTone : 249 : 65
SipDialing : 249 : 66
SipSendInvite : 249 : 67
SipModifySipMessage : -1 : 153
SipStartOutgoingRing : 249 : 68
SipModifySipMessage : -1 : 153
SipReceivedProvisionalResponse : 249 : 69
SipReceived100Trying : 249 : 70
SipWaitForInviteOk : 249 : 76
SipModifySipMessage : -1 : 153
SipModifySipMessage : -1 : 153
SipModifySipMessage : -1 : 153
SipModifySipMessage : -1 : 153
SipReceived100Trying : 249 : 70
SipModifySipMessage : -1 : 153
SipReceived183SessionProgress : 249 : 74
SipModifySipMessage : -1 : 153
SipInviteOkReceived : 249 : 77
SipSendInviteAck : 249 : 78
SipModifySipMessage : -1 : 153
SipOutgoingCallConnected : 249 : 79
SipInCall : 249 : 93
SipAnsweringCall : 0 : 91
SipSend200Ok : 0 : 88
SipModifySipMessage : -1 : 153
Now, this is the weird part. The incoming call leg hung up long before this point and sent a bye. However, LanScape appears to have ignored the Bye so long as the call was not OffHook. But, what happens, is since the destination leg was just placed "SipInCall", we try to take the originator "OffHook". But, since he hung up long ago, he gets the invite ack not received message.
SipInviteAckNotReceived : 0 : 89
SipOnHook : 0 : 59
SipSendBye : 249 : 108
SipModifySipMessage : -1 : 153
SipModifySipMessage : -1 : 153
SipReceivedByeAck : 249 : 109
SipCallComplete : 249 : 111
SipOnHook : 249 : 59
That completed the call with both sides immediately getting OnHook events. The problem seems to of course come from the fact that we never took the incoming leg off hook until he was already hung up, but LanScape did not inform us of that earlier. Expected behavior would be for LanScape to immediately inform the application of an OnHook state for originator phone line (line zero in this case). I could provide a Sip message log; however, it simply illustrates what the sip events above tell - caller one sent bye and LanScape ignored it while it was not taken off hook.
We could work around this by simply taken the caller off hook earlier, and playing a ringing noise, but the correct behavior seems to be immediately notifying the application of an OnHook condition.
Thanks.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 04 2007 at 10:47am | IP Logged
|
|
|
Hi Andrew,
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 |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 07 2007 at 10:58am | IP Logged
|
|
|
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 |
|
| |
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: July 05 2007 at 3:45pm | IP Logged
|
|
|
Just want to update this thread. The problem actually laid in the Sip Proxy we were using for testing. It had an issue sending bye's when multiple call forks were being made. Though, I swear that I saw a bye in the Sip log... but, log's can easily get confusing when Sip Messages from multiple phone calls with same user ID's are contained within.
Sorry about putting the blame on the LanScape engine :-)
|
| Back to Top |
|
| |
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Topic: unhandled "Bye"
