Re: ACF&CDR after triple stage rewriting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



GnuGk always shows rewritten numbers in all ACF and CDR messages.
You may use FileAcct/SqlAcct/RadAcct module to generate custom CDRs
and try %{Dialed-Number}accounting variable to get the dialed number instead
of %{Called-Station-Id} which is a rewritten number.
The dialed number is the one received before any rewrite (inbound or global).


----- Original Message ----- From: <UTShrike@xxxxxxxxxxxx>
Sent: Tuesday, January 25, 2005 2:48 PM



config:
[RasSrv::PermanentEndpoints]
1.2.3.4=endp2;7777.

[RasSrv::RewriteE164]
9999.=7777.

[RasSrv::GWRewriteE164]
endp1=in=.=9999.
endp2=out=%%%%.=.

Now, all calls from endp1 going to endp2, it's work but ...
if I call 12345 from endp1 what I have
12345
 |
999912345 <- endp1=in=.=9999.   <- incoming rewrite rule
 |
777712345 <- 9999.=7777.        <- global rewrite rule
 |
12345     <- endp2=out=%%%%.=.  <- outgoing rewrite rule (dst number)

but in ACF and CDR I see 777712345:dialedDigits not 12345
All rewriting made in outgoing rule like "endp2=out=%%%%.=." in [RasSrv::GWRewriteE164] works and I can see in log, but not show in ACF and CDR.


How I can see right destination number in ACF and CDR?



------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl

_______________________________________________________

List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux