18 Oct
2017
18 Oct
'17
5:40 a.m.
Juha Heinanen writes:
Perhaps the error is due to this change:
in 5.0:
path value of the contact
in 5.1:
path value with the Path vector (use '0' or '.' if it should not be
set)
In my xmlrpc command path param has empty string value:
..<param>.
...<value>.
....<string></string>.
...</value>.
..</param>.
This was not the reason. I change path param to
.<param>.
...<value>.
....<string>.</string>.
...</value>.
..</param>.
and still the error.
Below is the whole xmlrpc request/response.
-- Juha
-----------------------------
T 2017/10/18 12:36:50.360916 127.0.0.1:58310 -> 127.0.0.1:6060 [AP]
<?xml version="1.0" ?>.
<methodCall>.
.<methodName>ul.add</methodName>.
.<params>.
..<param>.
...<value>.
....<string>location</string>.
...</value>.
..</param>.
..<param>.
...<value>.
....<string>foo(a)bar.com</string>;/string>.
...</value>.
..</param>.
..<param>.
...<value>.
....<string>sip:foo@vm.bar.com</string>.
...</value>.
..</param>.
..<param>.
...<value>.
....<int>0</int>.
...</value>.
..</param>.
..<param>.
...<value>.
....<double>0.2</double>.
...</value>.
..</param>.
..<param>.
...<value>.
....<string>.</string>.
...</value>.
..</param>.
..<param>.
...<value>.
....<int>0</int>.
...</value>.
..</param>.
..<param>.
...<value>.
....<int>16</int>.
...</value>.
..</param>.
..<param>.
...<value>.
....<int>15</int>.
...</value>.
..</param>.
.</params>.
</methodCall>.
##
T 2017/10/18 12:36:50.361093 127.0.0.1:6060 -> 127.0.0.1:58310 [AP]
HTTP/1.0 200 OK.
Sia: SIP/2.0/TCP 127.0.0.1:58310.
Server: OpenSIPg SIP Proxy (5.1.0-0b4 (x86_64/linux)).
Content-Length: 295.
.
<?xml version="1.0"?>
<methodResponse>
<fault>
<value>
<struct>
<member>
<name>faultCode</name>
<value><int>500</int></value>
</member>
<member>
<name>faultString</name>
<value><string>Not enough parameters or wrong
format</string></value>
</member>
</struct>
</value>
</fault>
</methodResponse>