03-31-2007 05:19 AM - edited 03-14-2019 08:47 PM
Hi All,
We have got an ISDX PABX connected to CCM 4.2 by DPNSS-Westel-QSIG connection (DPNSS from ISDX, Westel protocol converter, QSIG into CCM). The VG with E1 QSIG interface is Cisco 2800. Everything works fine except when an ISDX extension tries to setup CallFarwardAll to an extension in CCM. The setup fails with the the fault message on the ISDX. When I make an ISDN trace in the VG (see below) I can see that the VG accepts the procedure and sends back RELEASE signal with "Normal release" cause. Which it interpreted wrongly by ISDX or Westel and the procedure fails. Does anybody have any idea if there is any way around it? Did anybody try to connect CCM to ISDX via Westel DPNSS/QSIG converter?
Thanks a lot!
!!! Trace: !!!
TRRCM1#
Mar 31 11:42:48.136: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x3829
Sending Complete
Bearer Capability i = 0xA880
Standard = ISO/IEC
Transfer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = Packet - not specified
Channel ID i = 0xAC
Facility i = 0x9FAA068001008201008B0101A1240201D10201123080A50D0A0103120
837333232323936320A010080083733323234383930
Calling Party Number i = 0x4980, '73222962'
Plan:Private, Type:Subscriber(local)
Called Party Number i = 0xC9, '4890'
Plan:Private, Type:Subscriber(local)
Shift to Codeset 4
Codeset 4 IE 0x31 i = 0x80
Shift to Codeset 5
Codeset 5 IE 0x32 i = 0x81
Mar 31 11:42:48.148: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xB
829
Channel ID i = 0xAC
Mar 31 11:42:48.148: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0xB82
9
Cause i = 0x809F - Normal, unspecified
Mar 31 11:42:48.172: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x3829
TRRCM1#
03-31-2007 07:04 AM
alexander,
can you find out, why the pbx is sending the bearer cap. "Unrestricted Digital" information in the setup?
can you see this message also for a normal call from the pbx?
can you post your gateway config?
regards
mehmet
04-05-2007 07:40 AM
Mehmet,
ISDX engineer could not answer your questions strait away - he probably did not understand them or did not want to understand them. But he has forwarded a piece of his trace of this failed transfer. Here it is:
acknowledgement from ISDX < V01937 CRM/CIM 048;
disconnect from Cisco > V01937 CRM/CIM 048;
sub part of call (last digit) < V01937 SSRM(I) 0
start of call V=Virtual < V01937 ISRM(I) 10;*1#*50*73222962#*18*31*31*31#*19*O#*30B#489
call set up starting with a *30B which is DIV-V Diversion-Validation
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: