[Serusers] 400 ul_add: flags expected

Samuel Osorio Calvo samuel.osorio at nl.thalesgroup.com
Fri Jun 24 11:19:43 CEST 2005


There is one field missing after replicate, called flag. It is a boolean parameter that I think it determines wether the UA is natted or not. So, the right command is:
bash#serctl fifo ul_add {table} {AoR} {Contact} {Expires} {q} {replicate} {flags}
so, as an example:

serctl fifo ul_add location bob at biloxy.com bob at 192.168.2.45 3600 1 0 0


Other useful commands are:
bash#serctl fifo ul_rm {table} {AoR}--> which will remove all contacts for the given AoR
and
bash#serctl fifo ul_rm_contact {table} {AoR} {Contact} --> remove only the given contact for the AoR

Hope it helps,

Samuel


Unclassified.
>>> "Aisling" <ashling.odriscoll at cit.ie> 06/23/05 05:12PM >>>
Hello,
 
Has anyone experienced the above message when adding a permanent user
location via the serctl fifo interface?
 
I did a search and another post suggested it was due to a mismatch in
the database due to customizing SER or because of serweb but because I
haven't done anything like that, does anyone have another explanation?
 
Also would anyone know the exact format for setting the q value with
this command? According to previous correspondence this might be
possible ("I think the current usrloc fifo commands provide enough
flexibility to modify the q value, I don't know now the exact spelling
but something like:
serctl ul add location user at domain user at ip  {expires} {q} {replicate}")
 
Many Thanks,
Aisling.
 
_______________________________________
Aisling O' Driscoll
Research Student
Centre for Adaptive Wireless Systems
Cork Institute of Technology.
 
Email: ashling.odriscoll at cit.ie 
 


-------------------Legal  Disclaimer---------------------------------------

The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.




More information about the sr-users mailing list