Re: [SR-Users] looks like send core function does not exist

2013-04-07 Thread Daniel-Constantin Mierla
As I said yesterday, it was moved from core to corex module, the wiki most likely was not updated at that time: - http://lists.sip-router.org/pipermail/sr-users/2013-April/077402.html You can remove from wiki. Cheers, Daniel On 4/7/13 8:06 AM, Juha Heinanen wrote: i removed corex from loaded

Re: [SR-Users] looks like send core function does not exist

2013-04-07 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > As I said yesterday, it was moved from core to corex module, the wiki > most likely was not updated at that time: > > - http://lists.sip-router.org/pipermail/sr-users/2013-April/077402.html > > You can remove from wiki. sorry, i somehow missed your earlier re

[SR-Users] problem with core forward function

2013-04-07 Thread Juha Heinanen
now that the send function issue got resolved, i tried core forward function. core cookbook tells: forward Forward the SIP request to the given destination in stateless mode. This has the format of [proto:]host[:port]. Host can be an IP or hostname; supported protocols are UDP, TCP and TLS. (For

[SR-Users] path uri problem

2013-04-07 Thread Juha Heinanen
it is not my lucky day. anything new that i try, does not work. in proxy 1, i call add_path_received() on register request, which results into this kind of path header: Path: . then i forward the request to proxy 2 and call save() on it. it results in error: Apr 7 14:01:44 wheezy1 /usr/sbin

[SR-Users] path uri problem

2013-04-07 Thread Juha Heinanen
Juha Heinanen writes: > Path: > . according to rfc3261 pvalue = 1*paramchar paramchar = param-unreserved / unreserved / escaped param-unreserved = "[" / "]" / "/" / ":" / "&" / "+" / "$" unreserved = aphanum / mark mark = "-" / "_" / "." / "!" / "̃" / "*" / "’" / "(" / ")" my conclusion is tha

[SR-Users] path uri problem

2013-04-07 Thread Juha Heinanen
Juha Heinanen writes: > my conclusion is that ; and = in received value needs to be escaped. i escaped them, but it didn't help. path header now looks like: Path: . and i still get the same error: Apr 7 14:49:47 wheezy1 /usr/sbin/sip-proxy[8709]: ERROR: registrar [save.c:887]: Failed to pa

[SR-Users] path uri problem

2013-04-07 Thread Juha Heinanen
i also tried by removing single quotes from received value: Path: since they are not serving any purpose, but that didn't help either. -- juha ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org

[SR-Users] path uri problem

2013-04-07 Thread Juha Heinanen
i find and fixed the bug that caused parsing of path uri to fail when save() was called. it still holds true that the path uri generated by add_path_received() is syntactically bogus. if the receiver is not kamailio, parsing of path uri would thus most likely fail. what should be done about it?

[SR-Users] textops warning

2013-04-07 Thread Juha Heinanen
i don't remember seeing this before: Apr 7 19:09:57 siika /usr/sbin/sip-proxy[8734]: WARNING: textops [textops.c:1816]: free function has not been defined for spve what should i do about it? -- juha ___ SIP Express Router (SER) and Kamailio (OpenSER

[SR-Users] textops warning

2013-04-07 Thread Juha Heinanen
Juha Heinanen writes: > i don't remember seeing this before: > > Apr 7 19:09:57 siika /usr/sbin/sip-proxy[8734]: WARNING: textops > [textops.c:1816]: free function has not been defined for spve it comes from here: static int fixup_free_in_list(void** param, int param_no) { if ((param_no =

Re: [SR-Users] path uri problem

2013-04-07 Thread Peter Dunkley
Thanks for the bug-fix as the parsing should always work, but I am having difficulty understanding the configuration in use here. This particular parsing problem only occurs when outbound is enabled in registrar and you have a received parameter to the Path: header. However, when using outbound I

[SR-Users] Kamalio report 404 not found upon INVITE ?

2013-04-07 Thread Khoa Pham
Hi, I have my SIP client registered to Kamailio successfully. I've check the location table in Kamailio and assert this successful registration. But when another SIP client tries to make call to me, it receive 404 not found from Kamailio. What cause this problem ? Please help -- Khoa Pham HCMC

Re: [SR-Users] path uri problem

2013-04-07 Thread Juha Heinanen
Peter Dunkley writes: > Thanks for the bug-fix as the parsing should always work, but I am having > difficulty understanding the configuration in use here. > > This particular parsing problem only occurs when outbound is enabled in > registrar and you have a received parameter to the Path: header