Hi Ben,
If you run the dr_carrier_status MI command, do you see the same #012
in the ID of the carrier ? #012 is '\n' - are you sure you do not have
it by mistake in DB ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 25.03.2015 21:53,
*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Thursday, March 26, 2015 10:02 AM
*To:* OpenSIPS users mailling list; Newlin, Ben
*Subject:* Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs
Hi Ben,
If you run the dr_carrier_status MI command, do you see the same
#012
-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Thursday, March 26, 2015 10:02 AM
To: OpenSIPS users mailling list; Newlin, Ben
Subject: Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs
Hi Ben,
If you run the dr_carrier_status MI command, do you see the same #012 in the
ID of the carrier
, 2015 10:54 AM
To: Bogdan-Andrei Iancu; OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs
Bogdan,
It did occur to me that the code seemed to be the octal for newline, but I
don't know what the significance of that could be.
The MI command output
I am using OpenSIPS 1.11 and I am recently getting some weird behavior from the
DROUTING module. The module is corrupting the Carrier ID that is being returned
via AVP. This behavior is occurring only with the Carrier ID, not the gateway
or rule IDs, and only when it is returned from the
