Re: [reSIProcate-users] Helper::computeCallId returns the same value
This issue has been previously seen, but we haven't been able to pin it
down.
Previous reports can be found here:
http://list.resiprocate.org/archive/resiprocate-devel-old/msg03200.html
http://list.resiprocate.org/archive/resiprocate-devel/msg06605.html
Aron's solution -- shunting "getRandom" over to "getCryptoRandom" --
worked for him. Of course, you impose a higher load on your CPU when you
do so, so you may want to try tracking the problem down and addressing
it in a more efficient way.
The problem does not seem to surface except when using DUM.
/a
Ilana Polyak wrote:
Hello
I have just started to use dum in our application and noticed that if
I run calls in a very high rate the call id repeats itself?
What am I doing wrong I have a separate thread that calls buildFdSet,
stack process and dum process. There is a semaphore before it and
semaphore for all the api calls that come from my application.
I have run a call for computeCallId from the same thread ( the thread
that runs the dum and stack) and the value returned seems to be fine.
But when it gets called from the api makeInviteSession which is called
from the context of my application thread the value repeats it self
for around 8 calls.
The calls are created one after another in a very high volume. If the
calls are created in a low volume (let’s say one per second)
everything is fine.
Have anyone seen this problem?
Thanks
**_Ilana Polyak_**
Senior Software Engineer, Protocol Group
Blade Business Line
**_ _**
**_AudioCodes USA, Inc._**
27 World's Fair Drive
Somerset, NJ 08873
Tel: 732-469-0880 ext. 137
Fax: 732-469-2298
Direct: 732-652-4677
Corporate URL: http://www.audiocodes.com <http://www.audiocodes.com/>
Blade Business Line URL: http://www.audiocodes.com/blades
**
------------------------------------------------------------------------
This email and any files transmitted with it are confidential
material. They are intended solely for the use of the designated
individual or entity to whom they are addressed. If the reader of this
message is not the intended recipient, you are hereby notified that
any dissemination, use, distribution or copying of this communication
is strictly prohibited and may be unlawful.
If you have received this email in error please immediately notify the
sender and delete or destroy any copy of this message
------------------------------------------------------------------------
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/