Bogdan,What was happening is that a call to a carrier failed and caused the
RURI which was written to the DB to come from the Contact header of the 486
that came from the carrier. I'm not sure why it used that instead of the
OURI..
I fixed this issue by storing the OURI to an avp ON INVITE and the
HI Brett,
You lost me here.
The $oU is the original username (whatever opensips received in the RURI
of the request). Also you mentioned about the Contact URI (mod_sofia),
right??
So, what exact part of the message are you trying to log?
Regards,
Bogdan
Brett Nemeroff wrote:
> No, actu
No, actually, the original invite, had a perfectly valid RURI in it.. but
the contact had sip:mod_sofia in it..
I am using extra_accounting and I'm looking $oU, which is why I'm confused
since the actual $oU is valid and not sip:mod_sofia
On Wed, Apr 8, 2009 at 8:40 AM, Bogdan-Andrei Iancu
wrote
Hi Brett,
The acc module will log the last RURI of the failed branch...so what was
the RURI before sending the INVITE outbecause if I look at the ACK,
I guess the INVITE also has "mod_sofia", right ?
In failure route you cannot change the branch that was just completed
If you want somet
Hey All,I'm sure I'm doing someting stupid here.. In general, I set all the
acc_db flags at the top of my script so everything gets logs. I'm getting
486 Busy from the far end and nice, pretty to_did from the original RURI is
being blown away with 'sip:mod_sofia'
Question is.. what do I need to do
