Hi Razvan,
you are right, it was wrong URI. Regarding drouting, i can no to routing
with drouting module if in Ruri is "E", right?
So the best case would be to transform "E" with dialplan in some number
and then do drouting or do you have any better preposition?
br
miha
On 15/09/2015 12:06, Răzvan Crainea wrote:
Hi, Miha!
That does not look like an URI at all: it contains only the username,
not the scheme, host, port, etc. Do you have the original message to
track this down?
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 09/15/2015 11:41 AM, Miha wrote:
Hi,
one of our costumer is sending as uri with "E" like "<E6000012370828"
and opensips return:
Sep 15 10:36:30 sip-adria ./opensips[18583]: ERROR:core:parse_uri:
bad uri, state 0 parsed: <E600> (4) / <E6000012370828> (14)
Sep 15 10:36:30 sip-adria ./opensips[18583]:
ERROR:core:parse_sip_msg_uri: bad uri <E6000012370828>
how to deal with this as we need also to send him with this kind of
prefix?
tnx
miha
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
