The VoIP session (on FXO) logs 4 entries for all connections: 1. start from port 2. start from user connection 3. stop from user connection 4. stop from port
in 1 and 4 you can see FXO port number also, opening ports doing authentication with username of your pots peer number mask (3640 with FXO for example). But it doesn't care about result of it.
in new IOS versions i see some changes in this.
The VoIP ports on Cisco 36xx series with NM-HDV voice modules generate port names as 'ISDN number:number' unless you use "aaa nas port voip" configuration command - than portname is 'Serial num/num:num '
if you use tacacs+ for Cisco VoIP gateway authentication, than you should write your TCL script so, that it should be aware of: 1. in first authentication session voip gw does not send information to tacacs+ about source/destination phone numbers 2. it does not send information about phone numbers in authorization request packets, and it does not send any av-pair in authorization start 3. authorization request from TCL script create two requests to tacacs+ server - authentication with setted username/pin and with source/destination phone numbers and after that it generate void authorization request, but for send values from tacacs+ to TCL you should use authorization responce in form: h323-credit-time=digit (or any other h323-related av-pairs, see documentation upper or in Cisco documentation)
Due to logging information where i plan to use device DNS names, not ip addresse s (due to more right logfile understanding, and for statistics), carefully check your DNS entries about network device and database servers names in native and r everse DNS zones. May be the best way - use /etc/hosts file for it.