Hello,
can you run kamailio with global parameter 'debug=3' and send the syslog messages for such case?
That will give the hints about what is going wrong there. I see some characters are hexa encoded, but better see first the logs.
Cheers, Daniel
On 4/8/11 11:14 AM, Pavel Segeč wrote:
Hi,
I'm using Kamailio SIMPLE AS server as the presence and XCAP solution as the extension for my Kamailio based IMS platfom. As the base Presence configuration i'm using the default config as is described inside of the tutorial from ASIPTO site, it works well for pure ietf SIP SIMPLE environment. But when using it with the IMS, I sniff during putting the new record 500 Error. May somebody show me a direction what should be wrong?
thanks
palo
PUT /xcap-root/resource-lists/users/palo/index/~~/resource-lists/list%5B@name=%22doubango%22%5D/entry%5B@uri=%22sip:segi@ims1.sip.uniza.sk%22%5D HTTP/1.1
Host: 158.193.139.36:5060
Content-Length: 151
Connection: Keep-Alive
User-Agent: XDM-client/OMA1.1
X-3GPP-Intended-Identity: palo
Content-Type: application/xcap-el+xml
<entry uri="sip:segi@ims1.sip.uniza.sk" xmlns="urn:ietf:params:xml:ns:resource-lists">
<display-name>segi@ims1.sip.uniza.sk</display-name>
</entry>HTTP/1.1 500 Server error
Via: SIP/2.0/TCP 158.193.152.64:20735
Server: kamailio (3.1.2 (i386/linux))
Content-Length: 0
__________ Informacia od ESET NOD32 Antivirus, verzia databazy 6025 (20110408) __________
Tuto spravu preveril ESET NOD32 Antivirus.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users