Calling Party Tap: In the existing implementation, calling party tap is based on the SUBSCRIBER: DN1 always. So, the same method will be applied when SIP client user dials AOR. The BTS 10200 will make the TAP decision based on the DN1. The information sent to DF server would have following subscriber identity related fields.
Calling Number: DN1
Called Number: NULL
User Input: dialed AOR
When Calling party does not have SUBSCRIBER: DN1, call cannot be tapped.
Called Party Tap: Called party tap should be strictly based on the dialed-string information. Since the CALEA wiretap table contains only DIGITs information, there will be no tapping on the called party for AOR dialed call.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...