01-23-2012 09:45 AM - edited 03-16-2019 09:09 AM
Hi to all!
Here is the problem:
At customer site we have old PBX system that we replacing with CUCM+C2911 E1 trunk to PSTN. Customer also have two GSM gateways connected to PBX. It is Blue Gate ISDN:
http://www.telsyco.cz/assets/photos/TELSYCO%20BlueGate%20ISDN%20manual%20en.pdf
We have no access to this GSM gateway and our task is to replace PBX with Cisco without additional configuring that Blue Gate ISDN GSM gateway.
When I connect Blue Gate to ISDN BRI interface, I can receive incoming calls but outgoing calls not passing. I tried with different outgoing number patterns, but nothing works.
Here is error with csim test:
csim: called number = 0992414876, loop count = 1 ping count = 0
csim err csimDisconnected recvd DISC cid(422)
csim: loop = 1, failed = 1
csim: call attempted = 1, setup failed = 1, tone failed = 0
So, I tried to intercept outgoing calls from old PBX to Blue Gate - I connect BRI 0/2/0 to Blue Gate and BRI 0/2/1 to PBX, but interface to PBX is not going up.
Here is status:
ISDN BRI0/2/0 interface
******* Network side configuration *******
dsl 8, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 8 CCBs = 0
The Free Channel Mask: 0x80000003
ISDN BRI0/2/1 interface
dsl 9, interface ISDN Switchtype = basic-net3
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 9 CCBs = 0
The Free Channel Mask: 0x80000003
Total Allocated ISDN CCBs = 0
Config is:
interface BRI0/2/0
no ip address
isdn switch-type basic-net3
isdn protocol-emulate network
isdn layer1-emulate network
isdn incoming-voice voice
isdn static-tei 0
isdn skipsend-idverify
!
interface BRI0/2/1
no ip address
isdn switch-type basic-net3
isdn incoming-voice voice
So I have two questions:
1. what could be reason that outgoing calls not going through Blue Gate but incoming does?
2. what ISDN BRI configuration should be for connecting to old PBX (MD110)?
Thanks in advance,
Sinisa.
Solved! Go to Solution.
01-26-2012 10:12 AM
01-23-2012 09:53 AM
Take "debug isdn q931" with "term mon".
01-23-2012 12:25 PM
Hi Paolo,
here is debug- first incoming call that is OK:
2w5d: ISDN BR0/2/0 Q931: RX <- SETUP pd = 8 callref = 0x76
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x81
Preferred, B1
Progress Ind i = 0x8081 - Call not end-to-end ISDN, may have in-band info
Calling Party Number i = 0x0180, '0038599241xxxx' <<< I hide last 4 digits
Plan:ISDN, Type:Unknown
Called Party Number i = 0x80, '600' <<< 600 is my internal extension
Plan:Unknown, Type:Unknown
High Layer Compat i = 0x9181
Sending Complete
2w5d: ISDN BR0/2/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xF6
Channel ID i = 0x89
Exclusive, B1
2w5d: ISDN BR0/2/0 Q931: TX -> ALERTING pd = 8 callref = 0xF6
Jan 23 21:14:14 HR: %ISDN-6-CONNECT: Interface BRI0/2/0:1 is now connected to 0038599241xxxx N/A
2w5d: ISDN BR0/2/0 Q931: TX -> CONNECT pd = 8 callref = 0xF6
Channel ID i = 0x89
Exclusive, B1
2w5d: ISDN BR0/2/0 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x76
Jan 23 21:14:17 HR: %ISDN-6-DISCONNECT: Interface BRI0/2/0:1 disconnected from 0038599241xxx , call lasted 3 seconds
2w5d: ISDN BR0/2/0 Q931: TX -> DISCONNECT pd = 8 callref = 0xF6
Cause i = 0x8290 - Normal call clearing
2w5d: ISDN BR0/2/0 Q931: RX <- RELEASE pd = 8 callref = 0x76
Cause i = 0x8090 - Normal call clearing
2w5d: ISDN BR0/2/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xF6
then outgoing call:
2w5d: ISDN BR0/2/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 600
2w5d: ISDN BR0/2/0 Q931: Sending SETUP callref = 0x0046 callID = 0x80AA switch = basic-net3 interface = Network
2w5d: ISDN BR0/2/0 Q931: TX -> SETUP pd = 8 callref = 0x46
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x0081, '600'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '099241xxxx' <<< I hide last 4 digits here
Plan:Unknown, Type:Unknown
2w5d: ISDN BR0/2/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xC6
Cause i = 0x80D8 - Incompatible destination
then also try outgoing call...but I dial full international number 00385xxxxxx:
2w5d: ISDN BR0/2/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num xxx600 <<< I hide first 3 digits
2w5d: ISDN BR0/2/0 Q931: Sending SETUP callref = 0x0047 callID = 0x80AB switch = basic-net3 interface = Network
2w5d: ISDN BR0/2/0 Q931: TX -> SETUP pd = 8 callref = 0x47
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Exclusive, B1
Calling Party Number i = 0x0081, 'xxx600' <<<< I hide first 3 digits
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '0038599241xxxx'
Plan:Unknown, Type:Unknown
2w5d: ISDN BR0/2/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xC7
Cause i = 0x80D8 - Incompatible destination
So as I can see...in second attempt GSM gateway puts 3 digits on internal extension as calling number...which is then real PSTN outside number, but not on GSM side... So I suppose that there is something with translation patterns that I shold play? I tried...but have no idea what to try next.
Regards,
S.
01-23-2012 01:26 PM
Are you using H.323 or MGCP ?
01-23-2012 02:35 PM
2911 router with this ISDN BRI card is configured as H323 gateway on CUCM for all calls, if you asked that.
01-23-2012 03:18 PM
Try:
interface br0/2/0
isdn outgoing-voice info-transfer-capability 3.1kHz
If not that, have to look in the number format accepted by the other device.
01-23-2012 04:26 PM
Nope...doesn't work...same error.
What do you mean by "look in the number format accepted by other device"?
01-24-2012 02:46 AM
Somehow the called number is not right, you have to find what the other device expects.
01-26-2012 08:04 AM
Hi,
today I managed to connect to GSM gateway via serial port. Nothing special there...I also speak with man which was configuring that gateway few years ago, and conclusion is that there is no special requirements for called or calling number.
It seams like there is some problem with BRI configuration on my side.
01-26-2012 10:12 AM
Can you try:
voice-port 0/2/0
compand-type a-law
bearer-cap speech
01-26-2012 01:26 PM
EXCELLENT!!!
Thank you Paolo wery much!!
It works!
Best regards,
Sinisa.
01-26-2012 01:57 PM
I did not noticed the u-law companding before.
Thanks for the nice rating and good luck!
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