05-03-2012 07:35 AM - edited 03-21-2019 05:45 AM
Hi,
I'm trying to get a Quescom Q50 GSM device to talk to an UC540. The Q50 pretends to be an ISDN line and is connected to the UC540 as such, we don't have any real ISDN lines, and any calls to the ISDN are routed by the Quescom as a GSM call.
Outgoing calls are working fine. I'm having trouble getting incoming calling working.
I've pasted a log sample below. The BAD FRAME errors are apparently because the Q50 doesn't do any CRC.
The Q50 is set to pretend any incoming call is coming into 123456, which you can see in the log. I've got an incoming Dial plan set by CCA on the UC540 with the calling ID of 123456 that routes it to a blast group.
Dialing on the Q50 gets threee rings then a disconnection.
Obviously I've got Quescom looking into this, but would value a second opinion. It would seem the Q50 is behaving correctly, as outgoing calls are fine.
Thanksm
Adam
012907: May 1 16:03:39.826: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up
012908: May 1 16:03:40.750: ISDN BR0/1/0 Q921: User RX <- SABMEp sapi=0 tei=0
012909: May 1 16:03:40.750: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=0
012910: May 1 16:03:40.778: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0
012911: May 1 16:03:40.782: ISDN BR0/1/0 Q921: User RX <- INFO sapi=0 tei=0, ns=0 nr=0
012912: May 1 16:03:40.782: ISDN BR0/1/0 Q931: SETUP pd = 8 callref = 0x1F
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 = 0x80, '07815197604'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '123456'
Plan:Unknown, Type:Unknown
High Layer Compat i = 0x9181
012913: May 1 16:03:40.786: ISDN BR0/1/0 Q921: User RX <- BAD FRAME(0x020173)
012914: May 1 16:03:41.778: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0
012915: May 1 16:03:41.786: ISDN BR0/1/0 Q921: User RX <- BAD FRAME(0x020173)
012916: May 1 16:03:42.118: %SYS-5-CONFIG_I: Configured from console by connect on vty0 (192.168.16.18)
012917: May 1 16:03:42.778: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0
012918: May 1 16:03:42.786: ISDN BR0/1/0 Q921: User RX <- BAD FRAME(0x020173)
012919: May 1 16:03:43.770: ISDN BR0/1/0 Q921: User RX <- INFO sapi=0 tei=0, ns=0 nr=0
012920: May 1 16:03:43.770: ISDN BR0/1/0 Q931: SETUP pd = 8 callref = 0x1F
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 = 0x80, '07815197604'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '123456'
Plan:Unknown, Type:Unknown
High Layer Compat i = 0x9181
012921: May 1 16:03:43.778: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2
012922: May 1 16:03:43.778: ISDN BR0/1/0 Q921: User TX -> IDVER ri=0 ai=0
012923: May 1 16:03:43.794: ISDN BR0/1/0 Q921: User RX <- IDCKRQ ri=0 ai=0
05-03-2012 10:29 AM
Please send "show run interface bri 0/1/0".
Also clarify if you're using some kind of ethernet cable, or a properly wired BRI cable, that has different pinout and pairs,
05-04-2012 01:37 AM
Thanks for the reply:
Current configuration : 227 bytes
!
interface BRI0/1/0
no ip address
isdn switch-type basic-net3
isdn overlap-receiving
isdn incoming-voice voice
isdn map address . plan isdn type unknown
isdn sending-complete
isdn static-tei 0
trunk-group ALL_BRI
end
Using an ethernet cable. It was the one that was in place when the ISDN line was in use so I just reused it. From your question can I assume that was a bad thing to do?
Adam
05-04-2012 02:07 AM
Check that the device can be set for dynamic TEI, not static.
You will also not need overlap-receive
You definitely need to use a proper BRI cable, not Ethernet.
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