I have two installations of the UC5xx using Radius to obtain call records. One of those deployments is working perfectly fine and I am obtaining the calling number (dialed number). However my other deployment is not. I am getting an error:
904286: *Aug 31 17:19:33.996: RADIUS: authenticator 76 D4 34 66 21 CE 34 0B - 7D CA 46 A7 32 03 7A 97
904287: *Aug 31 17:19:33.996: RADIUS: Acct-Session-Id  10 "0001BCE0"
904288: *Aug 31 17:19:33.996: RADIUS: Calling-Station-Id  12 "2605551234"
904289: *Aug 31 17:19:33.996: RADIUS: Called-Station-Id  5 "334"
047965: Aug 31 18:21:28.620: RADIUS: authenticator C1 35 13 B5 A2 A4 F5 13 - A5 AF 40 A4 04 5F 37 0F
045662: Aug 31 16:09:33.760: RADIUS: Acct-Session-Id  10 "000067A9"
045663: Aug 31 16:09:33.760: RADIUS: Vendor, Cisco  56
Any ideas? Is there a setting on the UC that I have enabled on one but not the other. I have taken the liberty of attaching both configs.
In the non-working and working scenario are both calls coming in from the FXO port? If so, can you enable the following debugs for the working and failed case-
debug voip ccapi inout
debug vpm signal
I have attached the debug logs for both the working and nonworking configs. Just a note: The working config is running IOS 12.4 while the nonworking is running 15.0.
If I downgrade the UC5xx from 15.0 to 12.4 I am back to receiving the Calling-Station-Id.
It appears to be an issue with IOS 15.0. Which needs to be installed with this deployment.
Sorry about the delay. Can you be more specific about what fixed the issue?
There has been a change in behavior in IOS 15M/T wrt radius accouting-
The following example shows how to allow the NAS port details to be included in the Calling Station ID:
Router(config)# radius-server attribute 31 send nas-port-detail
Was wondering if that's what you configured.
Thanks for the confirmation. I'll see if we can add this in the default configurations in the SWP.