04-27-2004 01:36 PM - edited 03-13-2019 04:49 AM
Back on CM version 3.1, we were trying to use called ID name (which wasn't supported). We're now up to ver. 3.3.3 which is supposed to support callerid and I'm trying to make sure everything is still set up correctly. We have PRI ckts coming into a VG200, and at one time I was able to turn on a debug or a show command on the VG200 that let me see the incoming callerid info in hex. I've tried debug voip ccapi inout and debug voice ccapi inout, but if it's in there I don't see it. We were actually able to read it by converting it to ASCII the last time. Does anyone know what that might have been? We've had the phone company turn name and number callerid back on for our PRI ckts and we're still not getting anything and I need to verify that it is actually being sent by them.
Thanks!
04-27-2004 11:18 PM
The debug vopi ccapi should show you the callerid numbers if they are coming in. This is from a 2611xm router though. This is what my debug looks like.
*Mar 5 06:34:07.041: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields:
*Mar 5 06:34:07.045: cc_api_call_setup_ind:
*Mar 5 06:34:07.045: cisco-username=
*Mar 5 06:34:07.045: ----- ccCallInfo IE subfields -----
*Mar 5 06:34:07.045: cisco-ani=3105555555
*Mar 5 06:34:07.045: cisco-anitype=2
*Mar 5 06:34:07.045: cisco-aniplan=1
*Mar 5 06:34:07.045: cisco-anipi=0
*Mar 5 06:34:07.045: cisco-anisi=3
*Mar 5 06:34:07.045: dest=7445
*Mar 5 06:34:07.045: cisco-desttype=0
*Mar 5 06:34:07.045: cisco-destplan=0
*Mar 5 06:34:07.045: cisco-rdn=
*Mar 5 06:34:07.045: cisco-rdntype=-1
*Mar 5 06:34:07.045: cisco-rdnplan=-1
*Mar 5 06:34:07.045: cisco-rdnpi=-1
*Mar 5 06:34:07.045: cisco-rdnsi=-1
*Mar 5 06:34:07.045: cisco-redirectreason=-1
*Mar 5 06:34:07.049: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: (vdbPtr=0x8378C3EC, callInfo={called=7445,called_oct3=0x80,c
alling=3105555555,calling_oct3=0x21,calling_oct3a=0x83,calling_xlated=false,subscriber_type_str=RegularLine,fdest=1,peer_tag=1, p
rog_ind=0,callingIE_present 1, src_route_label=, tgt_route_label= clid_transparent=0},callID=0x82AE12AC)
*Mar 5 06:34:07.049: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:
*Mar 5 06:34:07.049: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: type 13 , prot 0
*Mar 5 06:34:07.049: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 5 06:34:07.049: ccCheckClipClir: calling number is: "3105555555", calling oct3a is: 0x83
*Mar 5 06:34:07.049: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 5 06:34:07.049: Calling Party number is Network Provided
*Mar 5 06:34:07.049: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir:
*Mar 5 06:34:07.053: Leaving ccCheckClipClir
calling number is: "3105555555"
calling oct3 is: 0x21
calling oct3a is: 0x83
04-28-2004 03:24 AM
Right, I can see the numbers, it's the CallerID NAME field I'm looking for. I remember seeing a string of hexadecimal numbers that when converted to ASCII would give you "John Smith" or whatever name info the phone company is transmitting for that number. Unfortunately after 2 years I'm having a hard time re-finding it. If it should indeed also be in the debug voip ccapi inout, then it's likely that the telco isn't actually sending it yet, but I'd like to be sure and have some sort of proof before I call them up.
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide