SIP Trunk -Show registeration

[iptuser55]

We are currently running a voice recording and with SIP trunk using the built-in bridge method. At the moment checking the SIP registration is very hard, in RTMT the device>>device search>>>open device search>>>SIP Trunk - only shows the CUCM ip address of the DP assigned to the SIP trunk but not if it is registered to the destination and on the CUCM page you do not see any indication either. I`m wondering if we implement a SIP GW in the middle of the CUCM and the Voice Recording will it provide any better visual indication. I`m almost after something like debug isdn q931, q921 and SH ISDN STAT type debugs

thanks

[htluo]

SIP registration only applies to end points (eg. SIP phones).

SIP trunk is a logical concept.  It defines some parameters like the registrar server address, port number, security profile, etc.  The SIP trunk itself doesn't really "register" to any server from a SIP standard perspective.

Maybe you could elaborate what you tried to achieve so we could some suggestions?

Thanks!

Michael

http://htluo.blogspot.com

[iptuser55]

In  CUCM a SIP trunk is registered to our Voice Recorder (VR), the CUCM uses this trunk to send invites to the VR which in turns instructs CUCM to  tell the handset to send the RTP to another server which complies the RTP streams. One of the key parts is the normal SIP messages. At the moment we are blind to any messages being sent between the CUCM and VR, unless we download the traces from CUCM via RTMT nor can be tell if indeed the SIP trunk is registered. If we look in the RTMT as below you only see the IP add of the CUCM of the DP it uses. . Ideally we would like to see if confirm registration, messages etc and would it be easier using a SIP to SIP GW - debug ccsip etc

thanks 

CUPS

As it is you Michael

On a separate note , we are running CUCM 71.2.B have CUP8.x as a demo - Do you see any issue with this SW?  quite keen on video vi ateh phone rather then softphone

[htluo]

As far as I know, SIP trunk in CUCM does not "register" to anything.  The registration (INVITEs) are actually from IP phones.

Since there's no static "registration" status for the SIP trunk, if you're looking for something similar to "debug ccsip message", CCM SDI trace would be it.

Or you may do a packet capture from CUCM CLI:

utils network capture file myfile count 100000 size all host all 192.168.1.100

Where 192.168.1.100 is your VR address.

Then you may use RTMT pull the capture file and view the SIP flow in Wireshark or SIP Workbench.

Michael