04-07-2013 12:16 PM - edited 03-16-2019 04:39 PM
It works fine without going to Auto Attendant/CUE. But when it goes via AA I have an issue it doesnt display the caller name. But the script works fine without AA.
Please can someone help me. This debug below is via AA and where it says
descr: Shibly thats the caller name. Please I need help to get the caller name passing through via AA
Apr 7 19:13:50.774: %IP-3-LOOPPAK: Looping packet detected and dropped -
src=192.168.42.2, dst=192.168.42.160, hl=20, tl=78, prot=17, sport=137, dport=137
in=GigabitEthernet0/0, nexthop=192.168.42.160, out=GigabitEthernet0/0
options=none -Process= "IP Input", ipl= 0, pid= 139
-Traceback= 22B60B10z 22B61DF4z 22B62FC0z 22B63498z 22B63A04z 22EC93C0z 22EC9500z 22ECB174z 22B4A714z 22B65018z 22B4C274z 22B4C4B4z 22B4C594z 22B4C7ACz 2380BBE8z 2380BBCCz
Apr 7 19:13:58.626: ISDN BR0/1/1 Q931: RX <- SETUP pd = 8 callref = 0x01
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x2183, '7728783361'
Plan:ISDN, Type:National
Called Party Number i = 0x81, '233331'
Plan:ISDN, Type:Unknown
Apr 7 19:13:58.630: //3918//TCL :/tcl_PutsObjCmd: -- in act_Setup
Apr 7 19:13:58.630:
Apr 7 19:13:58.630: //3918//TCL :/tcl_PutsObjCmd: -- ANI: 07728783361, DNIS: 5002
Apr 7 19:13:58.630:
Apr 7 19:13:58.630: //3918//TCL :/tcl_PutsObjCmd: -- in vxml_getinfo
Apr 7 19:13:58.630:
Apr 7 19:13:58.630: //3918//TCL :/tcl_PutsObjCmd: -- quering http://192.168.42.2/ipps_clid/ClidH323.aspx
Apr 7 19:13:58.630:
Apr 7 19:13:58.646: ISDN BR0/1/1 Q931: TX -> CALL_PROC pd = 8 callref = 0x81
Channel ID i = 0x89
Exclusive, B1
Apr 7 19:13:58.726: //3918//TCL :/tcl_PutsObjCmd: -- in act_SetupContinue
Apr 7 19:13:58.726:
Apr 7 19:13:58.726: //3918//TCL :/tcl_PutsObjCmd: -- descr: Shibly
Apr 7 19:13:58.726:
Apr 7 19:13:58.726: //3918//TCL :/tcl_PutsObjCmd: -- DNIS: 5002
Apr 7 19:13:58.726:
Apr 7 19:13:58.730: ISDN BR0/1/1 Q931: TX -> PROGRESS pd = 8 callref = 0x81
Progress Ind i = 0x8181 - Call not end-to-end ISDN, may have in-band info
Apr 7 19:13:58.758: ISDN BR0/1/1 Q931: TX -> ALERTING pd = 8 callref = 0x81
Apr 7 19:13:58.766: //3918//TCL :/tcl_PutsObjCmd: -- in act_SetupDone
Apr 7 19:13:58.766:
Apr 7 19:13:58.770: //3918//TCL :/tcl_PutsObjCmd: -- status: ls_000
Apr 7 19:13:58.770:
Apr 7 19:13:58.782: ISDN BR0/1/1 Q931: TX -> CONNECT pd = 8 callref = 0x81
Channel ID i = 0x89
Exclusive, B1
Apr 7 19:13:58.834: ISDN BR0/1/1 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x01
Apr 7 19:13:58.838: %ISDN-6-CONNECT: Interface BRI0/1/1:1 is now connected to 5002 N/A
Apr 7 19:14:04.838: //3119//TCL :/tcl_PutsObjCmd: TCL B-ACD: >>> B-ACD Service Running <<<
Apr 7 19:14:08.042: ISDN BR0/1/1 Q931: RX <- DISCONNECT pd = 8 callref = 0x01
Cause i = 0x8090 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
Apr 7 19:14:08.042: %ISDN-6-DISCONNECT: Interface BRI0/1/1:1 disconnected from 7728783361 , call lasted 9 seconds
Apr 7 19:14:08.042: //3918//TCL :/tcl_PutsObjCmd: -- in act_Cleanup
Apr 7 19:14:08.042:
Apr 7 19:14:08.078: ISDN BR0/1/1 Q931: TX -> RELEASE pd = 8 callref = 0x81
Apr 7 19:14:08.126: ISDN BR0/1/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x01
MoneyMatters-2911#
Solved! Go to Solution.
04-08-2013 01:40 AM
Hi,
May be you are hitting bug id
This is still under investigation at Cisco and has been referred to a second bug CSCsi06623
These refer to PRI but I reckon they really mean Q931 so PRI/BRI.
Regards,
Alex.
Please rate useful posts.
04-08-2013 01:40 AM
Hi,
May be you are hitting bug id
This is still under investigation at Cisco and has been referred to a second bug CSCsi06623
These refer to PRI but I reckon they really mean Q931 so PRI/BRI.
Regards,
Alex.
Please rate useful posts.
04-08-2013 06:08 AM
Thanks Alex. I guess you are right. Its strange when we hit with small issues and take time to find a work around. I had to get some extra help to get a work around done so when a call comes from AA/CUE the service initates thereby displaying the caller name.
Thanks,
Shibly
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