Author |
|
Jalal Vetran
Joined: April 24 2006 Location: Iran Posts: 188
|
Posted: July 31 2011 at 8:08am | IP Logged
|
|
|
Hi Randal,
We have recently encountered a deadlock which I thought you would like to know.
When we call SendUdpDatagramUsingSipPort in UserNotifyCallbackProc while receiving SipModifySipMessage event, in rare circumstances, deadlock occures, and UserNotifyCallbackProc will never be called again until next restart.
I solved this problem by calling SendUdpDatagramUsingSipPort in another thread.
Good Luck,
Jalal Abedinejad
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: August 01 2011 at 7:13am | IP Logged
|
|
|
Hi Jalal,
Thanks for your post. I hope all is well with you.
I have made a note of your report. We will look into it further and see what exactly is occurring.
I quickly tested this and I do not see this behavior. The internals of the SendUdpDatagramUsingSipPort() API proc are pretty simple and should not be causing deadlocks. Maybe the software version you are running is significantly changed from the current version?
One thing I did see is that if you specify a destination host that cannot be resolved via netbios name resolution or DNS, an app will appear to hang as the network name resolution times out.
Anyway, I am glad you could understand the issue and locate a temporary work around.
Many thanks,
Randal
|
Back to Top |
|
|
Jalal Vetran
Joined: April 24 2006 Location: Iran Posts: 188
|
Posted: August 01 2011 at 7:37am | IP Logged
|
|
|
Hi,
The situatation is happenning very rarely, under full load. I think it is very important for LMEVoip to return from UserNotifyCallbackProc immediately, to process all received and queued sip messages. As SendUdpDatagramUsingSipPort is a little time consuming function, it causes the sip message receive queue to starvation.
We did not use a Name for destination host.We used IP Address.
Thanks
|
Back to Top |
|
|