Hello,
if you don't need to provide any of those parameters, then it should just work by not having them in the command.
But, for example, if you want to provide socket only, which is after the received as parameter order, then you must provide received parameter as well and use . or 0 to specify that received should not stored.
Cheers, Daniel
On Wed, Oct 18, 2017 at 10:24 AM, Juha Heinanen jh@tutpro.com wrote:
I noticed that my ul.add command that works OK in 5.0 doesn't anymore work in 5.1. I get back to the xmlrpc query:
<name>faultString</name> <value><string>Not enough parameters or wrong format</string></value>
I then went and compared ul.add in 5.0 and 5.1 and noticed that in 5.1 it has added two optional params:
received (optional) value with the received-from address (source address) (use '0' or '.' if it should not be set). Format: sip:srcip:srcport;transport=abc socket (optional) value with the local socket address (use '0' or '.' if it should not be set). Format: proto:localip:localport Note: the position of parameters is relevant, in the case of optional parameters, use '0' or '.' for parameters that should not be set which are positioned before any parameter that has to be set.What does that mean? Isn't optional really optional, but 0 or . is needed?
-- Juha
Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev