From smontour@twc.com Sun Aug 30 20:23:24 2015
From: Admin <smontour@twc.com>
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] unsupported route_type 64
Date: Sun, 30 Aug 2015 13:23:22 -0500
Message-ID: <1440959002.2642.3.camel@twc.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1388037802=="

--===============1388037802==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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":1341515=
504,"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.






--===============1388037802==--


From 568691@gmail.com Sun Aug 30 21:32:05 2015
From: Alexandru Covalschi <568691@gmail.com>
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] unsupported route_type 64
Date: Sun, 30 Aug 2015 22:31:40 +0300
Message-ID:
 <CAD_iGr_4kdOc84FWbEphjw9hh2Pnj-DT=8X8Yq7ODrAPx70pCA@mail.gmail.com>
In-Reply-To: <1440959002.2642.3.camel@twc.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1250299756=="

--===============1250299756==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

well, xlog("$(var(Event){s.rm,"})"); shouldn't have " " unless it's just
you logged that this way - so at the end we should have
route(CGR_AUTH_REPLY);
I don't see any problems in that part of config and don't understand which
other parts can generate such messages.
According the fact you receive error from tmx module, that may be
t_continue("$var(id_index)", "$var(id_label)", "CGRATES_AUTH_REPLY")
But I'm not sure, can't say anything bout that, construction looks
legitimate



--===============1250299756==
Content-Type: text/html
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="attachment.html"
MIME-Version: 1.0

PGRpdiBkaXI9Imx0ciI+PGRpdj53ZWxsLCB4bG9nKCZxdW90OyQodmFyKEV2ZW50KXtzLnJtLCZx
dW90O30pJnF1b3Q7KTsgc2hvdWxkbiYjMzk7dCBoYXZlICZxdW90OyAmcXVvdDsgdW5sZXNzIGl0
JiMzOTtzIGp1c3QgeW91IGxvZ2dlZCB0aGF0IHRoaXMgd2F5IC0gc28gYXQgdGhlIGVuZCB3ZSBz
aG91bGQgaGF2ZSA8YnI+PC9kaXY+PGRpdj5yb3V0ZShDR1JfQVVUSF9SRVBMWSk7PGJyPjwvZGl2
PjxkaXY+SSBkb24mIzM5O3Qgc2VlIGFueSBwcm9ibGVtcyBpbiB0aGF0IHBhcnQgb2YgY29uZmln
IGFuZCBkb24mIzM5O3QgdW5kZXJzdGFuZCB3aGljaCBvdGhlciBwYXJ0cyBjYW4gZ2VuZXJhdGUg
c3VjaCBtZXNzYWdlcy4gPGJyPjwvZGl2PjxkaXY+QWNjb3JkaW5nIHRoZSBmYWN0IHlvdSByZWNl
aXZlIGVycm9yIGZyb20gdG14IG1vZHVsZSwgdGhhdCBtYXkgYmU8c3BhbiBjbGFzcz0iaW0iPjwv
c3Bhbj48YnI+dF9jb250aW51ZSgmcXVvdDskdmFyKGlkX2luZGV4KSZxdW90OywgJnF1b3Q7JHZh
cihpZF9sYWJlbCkmcXVvdDssICZxdW90O0NHUkFURVNfQVVUSF9SRVBMWSZxdW90Oyk8YnI+PC9k
aXY+PGRpdj5CdXQgSSYjMzk7bSBub3Qgc3VyZSwgY2FuJiMzOTt0IHNheSBhbnl0aGluZyBib3V0
IHRoYXQsIGNvbnN0cnVjdGlvbiBsb29rcyBsZWdpdGltYXRlPGJyPjwvZGl2PjwvZGl2Pgo=

--===============1250299756==--


From miconda@gmail.com Wed Sep  2 09:22:25 2015
From: Daniel-Constantin Mierla <miconda@gmail.com>
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] unsupported route_type 64
Date: Wed, 02 Sep 2015 09:22:16 +0200
Message-ID: <55E6A3A8.7020909@gmail.com>
In-Reply-To: <1440959002.2642.3.camel@twc.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1908357625=="

--===============1908357625==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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":13415=
15504,"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(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

--=20
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com



--===============1908357625==--