cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
772
Views
0
Helpful
6
Replies

QSIG problems

rdamaso
Level 1
Level 1

Hi.

I have a problem with ISDN QSIG.

My setup is:

A---PBX-A----2651A----FR----2651B----PBX-B---B

When A calls to B, I see the call arriving in 2651A but the call doesn´t arrive in 2651B. I enabled debug voice cca inout and I don´t see anything.

When B calls to A , the phone A rings but I don´t ear nothing and the call is finished.

My config is the follow:

2651A

no network-clock-participate slot 1

no network-clock-participate wic 0

network-clock-participate wic 1

network-clock-select 1 E1 0/1

voice-card 0

dspfarm

!

ip cef

!

isdn switch-type primary-qsig

!

voice call send-alert

voice call carrier capacity active

voice rtp send-recv

!

controller E1 0/1

framing NO-CRC4

line-termination 75-ohm

pri-group timeslots 1-8,16

!

interface Serial0/1:15

no ip address

no logging event link-status

isdn switch-type primary-qsig

isdn overlap-receiving

isdn protocol-emulate network

isdn incoming-voice voice

isdn T310 4000

isdn send-alerting

no cdp enable

!

voice-port 0/1:15

bearer-cap Speech

!

dial-peer voice 1 pots

incoming called-number .

destination-pattern 10

direct-inward-dial

port 0/1:15

!

dial-peer voice 2 voip

destination-pattern 20....

session target ipv4:1.1.1.1

dtmf-relay cisco-rtp

2651B

network-clock-participate wic 1

network-clock-select 1 E1 0/1

voice-card 0

dspfarm

!

ip cef

!

isdn switch-type primary-qsig

!

voice call send-alert

voice call carrier capacity active

voice rtp send-recv

!

controller E1 0/1

framing NO-CRC4

line-termination 75-ohm

pri-group timeslots 1-8,16

!

interface Serial0/1:15

no ip address

no logging event link-status

isdn switch-type primary-qsig

isdn overlap-receiving

isdn protocol-emulate network

isdn incoming-voice voice

isdn T310 4000

isdn send-alerting

no cdp enable

!

voice-port 0/1:15

bearer-cap Speech

!

dial-peer voice 1 pots

incoming called-number .

destination-pattern 20

direct-inward-dial

port 0/1:15

!

dial-peer voice 2 voip

destination-pattern 10....

session target ipv4:1.1.1.2

dtmf-relay cisco-rtp

What is wrong??

I think that the problem is relative to ISDN signalization.

Thanks.

6 Replies 6

dgahm
Level 8
Level 8

What digits need to be sent to the PBX?

POTS dial peers by default do not forward the digits that match, so in your case the first 2 digits will not be sent. You can change this with a forward-digits X or forward-digits all under the peer.

A debug ISDN Q931 will show you what is being sent.

The fact the call does not go fast busy suggest the E1 D channel is up and talking, but you should see layer 2 multiple frames established if you show isdn status

Hi.

See the file attached.

Thanks.

The ISDN Q931 signalling between the PBXs and the routers look OK, but all the H225 call signalling messages are not making it from the terminating router to the originating router. It would be interesting to see the output from debug h225 event for both A & B.

What version IOS are you running?

Look debug in 2651A

Jul 12 02:57:29.695: Changing to new event: CONNECT

h323chan_chn_connect: connecting to 83C815A4:1720

Jul 12 02:57:29.695: h323chan_gw_conn: Created socket fd=2

Jul 12 02:57:29.695: h323chan_gw_conn: connect in progress on fd=2h323chan_chn_connect: using fd=2, owner_data(ccb) 0x83

C77FD0

changing from NONE state to CONNECTING state

Jul 12 02:57:29.735: h323chan_chn_process_read_socket: fd=2 of type CONNECT_PENDING has data

Jul 12 02:57:29.735: Changing to new event: CONNECTED

changing from CONNECTING state to CONNECTED state

Jul 12 02:57:29.735: compose_TunnelledSignallingMessage_cisco Tunnelled Content:

IAM,

PRN,isdn*,,QSIG*,

USI,rate,c,s,c,1

USI,lay1,alaw

TMR,00

CPN,00,,4,201003

CGN,00,,4,y,1,6604

CPC,09

FCI,,,,,,,y,

GCI,85003e36f1b711d980a1c0b0562607dd

....

Jul 12 02:57:29.739: The length of message content is:[166]

Hex representation of the SETUP TPKT to send.: 080200350504038090A36C060980363630347007893233313030307E02520520800600089

14A00042800B500001240013C0501000085003E36F1B711D980A1C0B0562607DD00CD1D82000700C8B653522B4C11008500DAF6F1B711D980A3C0B05

62607DD3402130000000C2013800B05000100C8B653524081801E400000060401004C2013801215000100C8B65352408000C8B653524081800100010

001800180010010A8018081170140B5000012810FE0010000010480FE04038090A31803A983881C2291AA068001008201008B0100A11402020100060

42B0C09008008485120414E4452451E0281836C06098036363034700789323331303030A1953101

803201811CB19E010003677464000000A649414D2C0D0A50524E2C6973646E2A2C2C515349472A2C0D0A5553492C726174652C632C732C632C310D0A

5553492C6C6179312C616C61770D0A544D522C30300D0A43504E2C30302C2C342C3233313030300D0A43474E2C30302C2C342C792C312C363630340D

0A4350432C30390D0A4643492C2C2C2C2C2C2C792C0D0A4743492C38353030336533366631623731316439383061316330623035363236303764640D

0A0D0A06800600040000000380AE02046774640180A649414D2C0D0A50524E2C6973646E2A2C2C515349472A2C0D0A5553492C726174652C632C732C

632C310D0A5553492C6C6179312C616C

h225SetupRequest: Q.931 SETUP sent from fd=2

Jul 12 02:57:29.747: h323chan_chn_process_read_socket: fd=2 of type CONNECTED has data

Jul 12 02:57:29.747: h323chan_recvdata: No Data on fd=2

PROCESS_READ: FAILED/NOT COMPLETE,rc 10, fd=2

Jul 12 02:57:44.748: compose_TunnelledSignallingMessage_ciscoNo tunnelled content.

Hex representation of the RELEASE COMPLETE TPKT to send.: h225TerminateRequest: Q.931 RELEASE COMPLETE sent from fd=2. C

all state changed to [Null].

Jul 12 02:57:44.752: h323chan_close: TCP connection from fd=2 closed

In 2651B I didn´t see any message. Nothing arrives.

In 2651A, I use c2600-ipvoice-mz.123-6a.bin and in 2651B I use c2600-ipvoice-mz.123-4.T6.bin.

Thanks.

I am assuming you can ping fully between the 2 routers? Are there any firewalls or access-lists between the 2?

If you can ping, and are sure there is no filtering occurring I would load the A router with the same IOS T code as the B.

David,

The ISP did a big mistake. I´ve checked a lot frame-relay parameters with ISP and it not configured correctly.

The problem was QoS and fragmentation in backbone.

Thanks a lot.