Hi Chris,
To be honest I fail to understand what you are trying to do - better
please post the failure_route part (or the script).
Regards.
Bogdan
On 07/04/2011 12:24 PM, Chris Martineau wrote:
Hi Bogdan,
Tried these methods.
1.Doesn't seem to help entry of the custom reason into the db.
2.Sort of works in that it creates another entry with the sip reason
changed but then doesn't have anything in the sip code field? Also
using this method does some strange stuff in the failure route in that
unless you have triggered a missed call flag it doesn't create a
record at all!
You also indicate that the reason code is being picked up from the
incoming error message however when I create an internal error message
which doesn't have an incoming error message the reason code is still
set to the default in the db even though the custom reason is sent
out? In this case where does it get the reason code from?
Many thanks
Chris
*From:*Bogdan-Andrei Iancu [mailto:[email protected]]
*Sent:* 01 July 2011 17:18
*To:* OpenSIPS users mailling list
*Cc:* Chris Martineau
*Subject:* Re: [OpenSIPS-Users] Entered reason in t_reply doesn't get
entered in db
Hi Chris,
The missed call events are generated when a negative final reply is
received / generated on the outbound part of a transaction (from the
next hop).
So the missed call record will contain information about the received
reply and not the reply you are sending out. This is why you see the
received reason code and not the one you are forcing.
If you want to force your own stuff, you may try two options:
1) in failure route, before "t_reply()" set again the missed call
flags, so you will force a second missed call event when reply is sent out
2) do not use the missed call flag (auto acc) and use the
acc_db_request() function from script to generate your missed call
custom event.
Regards,
Bogdan
On 07/01/2011 04:54 PM, Chris Martineau wrote:
Hi,
We are entering custom reason codes into the t_reply and sl_reply like
("403","No Funds") which gets sent out okay but doesn't get put into
the missed_call db. The entry in the db is always the default reason
for that code 403 Forbidden in this case.
Is there a way to get the custom reason code into the db?
Regards
Chris
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Bogdan-Andrei Iancu
OpenSIPS solutions and "know-how"
--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
