03-29-2007 05:43 AM - edited 03-14-2019 08:45 PM
Hi,
I have the following setup:
A Siemens PBX connecting to a CallManager via Qsig (mgcp controlled)
and
the CCM connecting to PSTN via PRI (mgcp controlled)
Calls to and from CCM works fine (inbound from PSTN and outbound to PSTN)
Calls to and from PBX works fine (inbound from PSTN and outbound to PSTN)
Calls from CCM to PBX works fine
Calls from PBX to CCM does not work
Currently the PBX sends me only 4 digits when trying to dial an ext on CCM and CCM extensions are 5 digits.
My D-channel towards the PBX looks like this:
!
interface Serial1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn overlap-receiving T302 2000
isdn incoming-voice voice
isdn bind-l3 ccm-manager
isdn sending-complete
no cdp enable
end
!
and debug isdn q931 gives the following:
01260: Mar 25 11:13:42.699 SAST: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0001
Sending Complete
Bearer Capability i = 0x9090A3
Standard = CCITT
Transfer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x91AA068001008201008B0100A10D02017D06042B0C092903020780
Facility i = 0x91AA068001008201008B0102A11302017E02013B300B30090A01050A01040A0103
Facility i = 0x91AA068001008201008B0100A11402017F06042B0C09008009524543455054494F4E
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0183, '0008'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x89, '70051'
Plan:Private, Type:Unknown
Locking Shift to Codeset 5
Codeset 5 IE 0x32 i = 0x81
001261: Mar 25 11:13:42.727 SAST: ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8001
Channel ID i = 0xA98381
Exclusive, Channel 1
001262: Mar 25 11:13:42.727 SAST: ISDN Se1/0:15 Q931: TX -> FACILITY pd = 8 callref = 0x8001
Facility i = 0x9FAA06800100820100A40602017E800100
001263: Mar 25 11:13:42.727 SAST: ISDN Se1/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8001
Facility i = 0x9FAA06800100820100A112020101020101800A4D6172636F204465656E
Progress Ind i = 0x8088 - In-band info or appropriate now available
001264: Mar 25 11:13:42.759 SAST: ISDN Se1/0:15 Q931: RX <- STATUS pd = 8 callref = 0x0001
Cause i = 0x81E41C - Invalid information element contents
Call State i = 0x03
001265: Mar 25 11:13:42.771 SAST: ISDN Se1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x8001
Cause i = 0x80E2 - Message not compatible with call state or not implemented
001266: Mar 25 11:13:43.075 SAST: ISDN Se1/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x0001
001267: Mar 25 11:13:43.099 SAST: ISDN Se1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8001
03-29-2007 06:05 AM
hi,
which version of qsig (ecmav1,v2, iso) do you have on the ccm ?
do you have the right network and user side configuration on the pbx and ccm? can you check, why the pbx is sending the berarer cap = 3.1 khz audio ?
regards
mehmet
03-29-2007 06:25 AM
Hi,
From what I can see it is using qsig verion ISO. Network and user side is setup correctly as the PBX needs to get to the CCM in order to get out to PSTN. I have no idea why the PBX is sending me bearer cap = 3.1 khz audio. Will ask when I meet the PBX tech onsite.
03-30-2007 02:16 AM
Hi,
So CCM uses Qsig iso v2 by default it seems. Got the PBX guys to change their side and all is working now.
Thnx
Charl
03-29-2007 06:07 AM
Charl,
I am seeing the PBX send 5-digits not 4 as you stated...Called Party Number i = 0x89, '70051'
I also noticed the following message in the debug which is causing the disconnect:
Cause i = 0x80E2 - Message not compatible with call state or not implemented
Take a look at this link it can possibly guide you to the cause:
http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a008012e95f.shtml
03-29-2007 06:27 AM
Hi,
I was referring to the Calling party being 4 digits.
Thnx
Charl
03-29-2007 08:18 AM
I think you have to look at CM traces for this case, as this is MGCP. Perhaps the CCM doesn't like the facilites in the setup, on the other hand being this QSIG, supposedly any kind of facility must be dealt with.
03-29-2007 10:42 AM
How old is this PBX? You may have to use the DTRAN table and adjust the digits from there.
03-29-2007 12:59 PM
It looks to me like the PBX is sending 5 digits 70051
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0183, '0008'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x89, '70051'
Plan:Private, Type:Unknown
if you find this
Cause i = 0x81E41C - Invalid information element contents
you'll probably find your problem....is this like setup as E1 or T1
04-01-2007 10:09 PM
Charl,
It i do had the similar probelm faced while integration with alcatel PBX.Let me ask you , whether the firmware running is old version on the PBX, if yes you need to set the advance sysstem paramater ( PRI & MGCP)on CCM
for QSIG variant ECMA.By default its is set to ISO which is higher version.
Let me know after the changes....
vishwesh
04-02-2007 01:14 AM
Hi,
I have no idea what firmware is running on the PBX. The PBX tech changed his end to Qsig ISO version 2 and that seems to have fixed my problem. I did see those settings under the advance system settings - however you can only change it between ECMA and ISO. You can not change the version of ISO.
Thnx
04-12-2007 09:46 AM
Have a read here or get back to me as I am an Ex-Siemens Engineer and now work on Call Manager ;-)
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