The error message is written because you attempt to print the tm sip
reply code in an event_route (where the transaction is not available).
Overall it is harmless, the returned value is 0.
In master branch I pushed a patch changing the error level to info for
such case.
Cheers,
Daniel
On 30/08/15 20:23, Admin wrote:
> Here is the output from "event_route[evapi:message-received]"
>
> Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO:
> <script>: Message received in evapi:
> {"Event":"CGR_AUTH_REPLY","TransactionIndex":39453,"TransactionLabel":1341515504,"MaxSessionTime":60,"Suppliers":"","Error":""}
> Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO:
> <script>: Event received in evapi: "CGR_AUTH_REPLY"
> Aug 30 13:19:00 everest /usr/local/kamailio/sbin/kamailio[3891]: ERROR:
> tmx [t_var.c:521]: pv_get_tm_reply_code(): unsupported route_type 64
>
> Thanks.
>
>
>
>
>
> _______________________________________________
> 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
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
_______________________________________________
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
