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 <[email protected]>wrote: > Hi Brett, > > The acc module will log the last RURI of the failed branch...so what was > the RURI before sending the INVITE out....because 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 something custom to be logged, use the extra_accounting > options. > > Regards, > Bogdan > > Brett Nemeroff wrote: > >> 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 to get the 486 logged, but to have the >> right did in the record.. right now I use $oU. Maybe a revert_uri? (am I >> making that up?) >> >> >> Here's the 486 from my upstream: >> >> >> U 5.6.239.142:5060 <http://5.6.239.142:5060> -> 1.2.204.8:5060 < >> http://1.2.204.8:5060> >> >> SIP/2.0 486 Busy Here. >> >> Via: SIP/2.0/UDP 1.2.204.8;branch=z9hG4bK5a3.473e0af1.0. >> >> Via: SIP/2.0/UDP 2.3.72.138:5060 >> ;received=2.3.72.138;branch=z9hG4bK0bf20a91;rport=5060. >> >> From: "custdomain.com <http://custdomain.com>" <sip:custdomain.com < >> http://custdomain.com>@2.3.72.138 <http://2.3.72.138>>;tag=as0e9ef59a. >> >> To: <sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]> >> >>;tag=BeZcHaUmX1D8Q. >> >> Call-ID: [email protected] <mailto: >> [email protected]>. >> >> CSeq: 103 INVITE. >> >> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-12911. >> >> Accept: application/sdp. >> >> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, >> NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH. >> >> Supported: timer, precondition, path, replaces. >> >> Content-Length: 0. >> >> . >> >> >> >> U 2.3.72.138:5060 <http://2.3.72.138:5060> -> 1.2.204.8:5060 < >> http://1.2.204.8:5060> >> >> ACK sip:[email protected]:5060;transport=udp SIP/2.0. >> >> Via: SIP/2.0/UDP 2.3.72.138:5060;branch=z9hG4bK0bf20a91;rport. >> >> Route: >> <sip:1.2.204.8;lr=on;did=bf5.880cbc94>,<sip:5.6.239.142;lr=on;ftag=as0e9ef59a>. >> >> Max-Forwards: 70. >> >> From: "custdomain.com <http://custdomain.com>" <sip:custdomain.com < >> http://custdomain.com>@2.3.72.138 <http://2.3.72.138>>;tag=as0e9ef59a. >> >> To: <sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]> >> >>;tag=BeZcHaUmX1D8Q. >> >> Contact: <sip:custdomain.com <http://custdomain.com>@2.3.72.138 < >> http://2.3.72.138>>. >> >> Call-ID: [email protected] <mailto: >> [email protected]>. >> >> CSeq: 103 ACK. >> >> User-Agent: SS. >> >> Content-Length: 0. >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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
