Thanks Anca <br><br><div class="gmail_quote">On 8 April 2011 09:30, Anca Vamanu <span dir="ltr"><<a href="mailto:anca@opensips.org">anca@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Pete,<div><div></div><div class="h5"><br>
<br>
On 04/08/2011 10:40 AM, Pete Kelly wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi<br>
<br>
I am using this parameter with the b2b_logic module to capture the b2b session key, so I can use the bridging function later:<br>
<br>
modparam("b2b_logic", "b2bl_key_avp", "$avp(i:99)").<br>
<br>
However the key which is put into the avp looks quite short (5 digits long?)<br>
<br>
I expect this server to have to cope with many hundreds of b2bua sessions at the same time, can anyone advise if the key is truly unique or if there are any other considerations I should take?<br>
<br>
</blockquote>
<br></div></div>
Don't worry - it can hold a very large number of records and it will not overlap. That key represents actually the position in the hash table. It does not have a fixed length, it will get as long as it is needed. The first int represents the dimension of the hash table ( default is 1024, but you can increase by setting hash_size module parameter - beware that you have to put there the power of 2). The second int is the position in the list for that hash_index.<br>
<br>
Regards,<br>
<br>
-- <br>
Anca Vamanu<br>
OpenSIPS Developer<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks<br>
<br>
Pete<br>
</blockquote>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div><br>