Call Party Release Source in RADIUS CDR
A problem that arises when troubleshooting a failed called is knowing where the call release came from. The IMG 2020 however has the functionality to inform the user whether the release came from the IMG 2020 (local) or the release came from the remote party (remote). When a call fails, the release information is written into the Call Detail Record (CDR) in RADIUS. The Call Party Release Info will display one of the following values below in the Radius CDR dialogic-release-source
CALLED PARTY RELEASE - Local
CALLED PARTY RELEASE - Remote
CALLING PARTY RELEASE - Local
CALLING PARTY RELEASE- Remote
Example CDR
The example below displays that the destination channel group of the inbound call does not have any free channels available so the IMG 2020 releases the call. In the CDR below it displays  dialogic-release-source = "CALLED PARTY RELEASE,Local" meaning the release came from the local party.
Wed Sep 16 13:47:45 2009
NAS-IP-Address = 10.129.44.230
NAS-Port = 1812
Calling-Station-Id = "9195551313"
Called-Station-Id = "2125551212"
Acct-Session-Id = "00201c13153b008f00c31000fa4123a40008"
Acct-Status-Type = Start
NAS-Port-Type = Ethernet
Service-Type = Login-User
dialogic-call-origin = "originate"
dialogic-call-type = "ISDN"
Acct-Delay-Time = 0
Login-IP-Host = 10.129.44.249
Tunnel-Client-Endpoint:0 = "10.129.44.230"
dialogic-setup-time = "WED SEP 16 17:47:45:709 2009 +0000"
dialogic-dnis-pre-translate = "4003"
dialogic-ani-pre-translate = "9195551313"
dialogic-call-direction = "INCOMING LEG"
dialogic-trunk-grp-in = "8000_ISDN_0"
Client-IP-Address = 10.129.44.230
Acct-Unique-Session-Id = "a9fd07c66fb06a77"
Timestamp = 1190224065
Wed Sep 16 13:47:45 2009
NAS-IP-Address = 10.129.44.230
NAS-Port = 1812
Calling-Station-Id = "9195551313"
Called-Station-Id = "4003"
Acct-Session-Id = "00201c13153b008f00c31000fa4123a40008"
Acct-Status-Type = Start
NAS-Port-Type = Ethernet
Service-Type = Login-User
dialogic-call-origin = "answer"
dialogic-call-type = "SIP"
Acct-Delay-Time = 0
Login-IP-Host = 10.129.44.249
Tunnel-Client-Endpoint:0 = "10.129.44.230"
dialogic-setup-time = "WED SEP 16 17:47:45:719 2009 +0000"
dialogic-dnis-post-translate = "4003"
dialogic-ani-post-translate = "9195551313"
dialogic-call-direction = "OUTGOING LEG"
dialogic-trunk-grp-out = "4003_SIP_MG02"
dialogic-next-hop-ip = "0.0.0.0"
dialogic-next-hop-dn = "0.0.0.0"
dialogic-call-id = "0"
dialogic-voip-dst-sig-ip-out = "0.0.0.0"
dialogic-voip-dst-rtp-ip-out = "0.0.0.0"
dialogic-voip-src-rtp-ip-out = "0.0.0.0"
dialogic-voip-src-sig-ip-out = "10.129.44.230"
dialogic-voip-remote-vocoders = "NULL"
Client-IP-Address = 10.129.44.230
Acct-Unique-Session-Id = "a9fd07c66fb06a77"
Timestamp = 1190224065
Wed Sep 16 13:47:45 2009
NAS-IP-Address = 10.129.44.230
NAS-Port = 1812
Calling-Station-Id = "9195551313"
Called-Station-Id = "4003"
Acct-Session-Id = "00201c13153b008f00c31000fa4123a40008"
Acct-Session-Time = 0
Acct-Status-Type = Stop
Acct-Terminate-Cause = Service-Unavailable
NAS-Port-Type = Ethernet
Service-Type = Login-User
dialogic-call-origin = "answer"
dialogic-call-type = "SIP"
dialogic-Q931-disconnect-cause = "22"
Acct-Delay-Time = 0
Login-IP-Host = 10.129.44.249
Tunnel-Client-Endpoint:0 = "10.129.44.230"
dialogic-setup-time = "WED SEP 16 17:47:45:719 2009 +0000"
dialogic-disconnect-time = "WED SEP 16 17:47:45:729 2009 +0000"
dialogic-release-source = "CALLED PARTY RELEASE,Local"
dialogic-dnis-post-translate = "4003"
dialogic-ani-post-translate = "9195551313"
dialogic-call-direction = "OUTGOING LEG"
dialogic-trunk-grp-out = "4003_SIP_MG02"
dialogic-next-hop-ip = "0.0.0.0"
dialogic-next-hop-dn = "0.0.0.0"
dialogic-call-id = "0"
dialogic-voip-dst-sig-ip-out = "0.0.0.0"
dialogic-voip-dst-rtp-ip-out = "0.0.0.0"
dialogic-voip-src-rtp-ip-out = "0.0.0.0"
dialogic-voip-src-sig-ip-out = "10.129.44.230"
dialogic-voip-remote-vocoders = "NULL"
Client-IP-Address = 10.129.44.230
Acct-Unique-Session-Id = "a9fd07c66fb06a77"
Timestamp = 1190224065
Wed Sep 16 13:47:45 2009
NAS-IP-Address = 10.129.44.230
NAS-Port = 1812
Calling-Station-Id = "9195551313"
Called-Station-Id = "2125551212"
Acct-Session-Id = "00201c13153b008f00c31000fa4123a40008"
Acct-Session-Time = 0
Acct-Status-Type = Stop
Acct-Terminate-Cause = Service-Unavailable
NAS-Port-Type = Ethernet
Service-Type = Login-User
dialogic-call-origin = "originate"
dialogic-call-type = "ISDN"
dialogic-Q931-disconnect-cause = "22"
Acct-Delay-Time = 0
Login-IP-Host = 10.129.44.249
Tunnel-Client-Endpoint:0 = "10.129.44.230"
dialogic-setup-time = "WED SEP 16 17:47:45:709 2009 +0000"
dialogic-disconnect-time = "WED SEP 16 17:47:45:739 2009 +0000"
dialogic-release-source = "CALLED PARTY RELEASE,Local"
dialogic-dnis-pre-translate = "4003"
dialogic-ani-pre-translate = "9195551313"
dialogic-call-direction = "INCOMING LEG"
dialogic-trunk-grp-in = "8000_ISDN_0"
Client-IP-Address = 10.129.44.230
Acct-Unique-Session-Id = "a9fd07c66fb06a77"
Timestamp = 1190224065
Â
Release Scenarios
Below are examples of calls being released and what would be displayed in the RADIUS CDR.
CALLED PARTY RELEASE - Local
All channels in outgoing channel group are out of service.
dialogic-release-source = "Called Party Release - Local"
dialogic-Q931-disconnect-cause = "22"
Â
Timed out waiting for Alerting from destination network.
dialogic-release-source = "Called Party Release - Local"
dialogic-Q931-disconnect-cause = "12"
Â
CALLED PARTY RELEASE - Remote
User busy.
dialogic-release-source = "Called Party Release - Remote"
dialogic-Q931-disconnect-cause = "11"
Â
Unallocated number.
dialogic-release-source = "Called Party Release - Remote"
dialogic-Q931-disconnect-cause = "1"
Â
CALLING PARTY RELEASE - Local
No match in incoming translation table. Un-allocated number.
dialogic-release-source = "Calling Party Release - local"
dialogic-Q931-disconnect-cause = "1"
Â
No match in route table. No route to destination.
dialogic-release-source = "Calling Party Release - local"
dialogic-Q931-disconnect-cause = "3"
Â
CALLING PARTY RELEASE - Remote
Normal call clearing.
dialogic-release-source = "Calling Party Release - Remote"
dialogic-Q931-disconnect-cause = "16"
Â
If the call is released internally by any signaling layer, the reason will indicate remote. This is being worked on and will be fixed in a future release. Until the issue is fixed, further analysis will be needed to determined the origin. For example viewing call traces.