4 May
2012
4 May
'12
5:44 p.m.
Hello,
On 5/4/12 12:54 PM, Krishna Kurapati wrote:
That's what I thought too. There are no errors in
the debug log. Since
I am using xmlrpc instead of fifo,
are there any restrictions on the format?
maybe you can get more details if you run with debug=3. Should be no
restriction, apart of valid xml, on the other hand I am not sure the
xmlrpc module does escaping/unescaping of the xml tags in the parameters
of the xmlrpc commands.
Cheers,
Daniel
Krish Kura
On Fri, May 4, 2012 at 3:16 AM, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
Hello,
t_uac_dlg is general purpose command, so it should work with
notify as well -- iirc, kamctl had some ping command that used NOTIFY.
Do you get any error in the log messages?
Cheers,
Daniel
On 4/27/12 11:48 PM, Krishna Kurapati wrote:
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi,
I was able to send MESSAGE using xmlrpc (mi and t_uac_dlg) I got
the 200 OK response to the message.
However, when I try to send NOTIFY, I receive HTTP response but
with empty methodResponse.
Is NOTIFY not suppored by t_uac_dlg?
Thanks
Krish Kura
POST /RPC2 HTTP/1.0
User-Agent: ruby-sip-client
Host: 10.1.0.6
Content-Type: text/xml
Connection: keep-alive
Content-Length: 650
<?xml version="1.0"
?><methodCall><methodName>mi</methodName><params><param><value><string>t_uac_dlg</string></value></param><param><value><string>NOTIFY</string></value></param><param><value><string>sip:kkurapati_staff_test@10.1.0.6
<mailto:sip%3Akkurapati_staff_test@10.1.0.6></string></value></param><param><value><string>.</string></value></param><param><value><string>.</string></value></param><param><value><string>From:
<sip:kkurapati_provider_test@10.1.0.6
<mailto:lt%3Bsip%3Akkurapati_provider_test@10.1.0.6>>
To: <sip:kkurapati_staff_test@10.1.0.6
<mailto:lt%3Bsip%3Akkurapati_staff_test@10.1.0.6>>
Max-Forwards: 70
Call-ID: e3f15b5dc200234cff2c7b648d79c49f(a)10.1.0.3
<mailto:e3f15b5dc200234cff2c7b648d79c49f@10.1.0.3>
</string></value></param><param><value><string>User
added</string></value></param></params></methodCall>
##
T 2012/04/27 14:39:11.579281 10.1.0.6:5060 <http://10.1.0.6:5060>
-> 10.1.0.3:44817 <http://10.1.0.3:44817> [AP]
HTTP/1.0 200 OK.
Via: SIP/2.0/TCP 10.1.0.3:44817 <http://10.1.0.3:44817>.
Server: kamailio (3.3.0-dev7 (x86_64/linux)).
Content-Length: 137.
.
<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value><array><data>
</data></array></value>
</param>
</params>
</methodResponse>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -http://www.asipto.com
http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda>
-http://www.linkedin.com/in/miconda