Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Problem when connecting PBX to Gateway

hello,

you find the scheme in the below image.

the problem is when that the phone behind the PBX (site A) cannot call phone behind PBX (site C), and when i debug isdn q931, the message : " service opertional violated " is displayed in the gateway near to site B.On the contrary, the call from phone behind PBX (site C) to phone (site A) works succefully.

Help me please.

thanks at advance

10 REPLIES
Hall of Fame Super Gold

Re: Problem when connecting PBX to Gateway

Hi,

please send output of mentioned debug for the failed call.

New Member

Re: Problem when connecting PBX to Gateway

this is the debug :

Router-SiteB#

*Jan 25 16:05:21.645: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Calling num 910945

*Jan 25 16:05:21.645: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Called num 561498

*Jan 25 16:05:21.645: ISDN Se0/3/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0782

Bearer Capability i = 0x9090A3

Standard = CCITT

Transer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839F

Exclusive, Channel 31

Calling Party Number i = 0x0080, '910945'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '561498'

Plan:Unknown, Type:Unknown

*Jan 25 16:05:21.713: ISDN Se0/3/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x8782

Channel ID i = 0xA9839F

Exclusive, Channel 31

*Jan 25 16:05:21.717: ISDN Se0/3/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x8782

Cause i = 0x80B4 - Service operation violated

*Jan 25 16:05:21.721: ISDN Se0/3/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x0782

*Jan 25 16:05:21.781: ISDN Se0/3/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8782

Cause i = 0x8090 - Normal call clearing

*Jan 25 16:05:22.917: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Calling num 910945

*Jan 25 16:05:22.921: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Called num 561498

*Jan 25 16:05:22.921: ISDN Se0/3/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0783

Bearer Capability i = 0x9090A3

Standard = CCITT

Transer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839F

Exclusive, Channel 31

Calling Party Number i = 0x0080, '910945'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '561498'

Plan:Unknown, Type:Unknown

*Jan 25 16:05:22.981: ISDN Se0/3/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x8783

Channel ID i = 0xA9839F

Exclusive, Channel 31

*Jan 25 16:05:22.989: ISDN Se0/3/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x8783

Cause i = 0x80B4 - Service operation violated

*Jan 25 16:05:22.989: ISDN Se0/3/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x0783

*Jan 25 16:05:23.041: ISDN Se0/3/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8783

Cause i = 0x8090 - Normal call clearing

*Jan 25 16:05:24.189: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Calling num 910945

*Jan 25 16:05:24.193: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x0, Called num 561498

*Jan 25 16:05:24.193: ISDN Se0/3/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0784

I attach you the configurations of site A and site B

thank you.

Hall of Fame Super Gold

Re: Problem when connecting PBX to Gateway

Hi, really you should ask PBX people why the call is rejected, because the setup seems perfectly valid. You can compare it with a setup from B or C, to A.

By the cause, it seems like incoming calls are blocked.

Can site A call site B ?

New Member

Re: Problem when connecting PBX to Gateway

hi,

thank for reply.

Site A can call site B, and one thing that i have forgotten to say last time is that when i simulate the call from the router with "csim start 561498" command, it works and the call passes.Also, the call from Site C to Site A passes succeffully

i send you the attachement of two calls : one from router and the other from phone behind PBX that i have token from the Router-SiteB

Regards.

Hall of Fame Super Gold

Re: Problem when connecting PBX to Gateway

Hi,

On router B, take a q931 trace of the csim call that works, to compare with the one that does not.

The only difference should be the calling number, none in case of csim.

If this is true, as a workaround we can try changing the calling number.

Do not take ccapi debugs that are not useful in this case.

New Member

Re: Problem when connecting PBX to Gateway

hello,

you find below the trace of the call that works, dipslayed in Router B

Jan 28 10:23:01.761: ISDN Se0/3/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0077

Bearer Capability i = 0x8090A3

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9838C

Exclusive, Channel 12

Calling Party Number i = 0x0083, '1498'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '910941'

Plan:Unknown, Type:Unknown

High Layer Compat i = 0x9181

*Jan 28 10:23:01.781: ISDN Se0/3/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8077

Channel ID i = 0xA9838C

Exclusive, Channel 12

*Jan 28 10:23:03.425: ISDN Se0/3/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8077

Progress Ind i = 0x8588 - In-band info or appropriate now available

*Jan 28 10:23:07.205: ISDN Se0/3/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8077

*Jan 28 10:23:07.257: ISDN Se0/3/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0077

*Jan 28 10:23:13.201: %ISDN-6-CONNECT: Interface Serial0/3/0:11 is now connected to 1498 login local

--More-- line vty 5 15

--More-- password 7 *********

--More-- login local

!

scheduler allocate 20000 1000

!

end

*Jan 28 10:23:24.733: ISDN Se0/3/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0077

Cause i = 0x8090 - Normal call clearing

*Jan 28 10:23:24.733: %ISDN-6-DISCONNECT: Interface Serial0/3/0:11 disconnected from 1498 , call lasted 17 seconds

*Jan 28 10:23:24.733: ISDN Se0/3/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x8077

*Jan 28 10:23:24.797: ISDN Se0/3/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0077

Cause i = 0x8090 - Normal call clearing

thanks.

Hall of Fame Super Gold

Re: Problem when connecting PBX to Gateway

Hi,

you said that site A can call B, but not C.

The trace you have sent is for a call from B or C to A, we knew already that is working.

Now since it appears B is blocking calls from A to C, but whit csim start is works, you can try resetting the calling number, the easier way is "clid network-number XXX" in DP. Try placing some number that belongs to B.

New Member

Re: Problem when connecting PBX to Gateway

Hi,

the trace that i sent you regards the call from 'A' to 'C'.

Now, all the calls from and to all sites works, except the call from A to C.

I don't understand what's clid network-number XXX and which site must accept this command.

thanks.

Hall of Fame Super Gold

Re: Problem when connecting PBX to Gateway

Hi,

maybe you took the tace on A, because it is an incoming call. If it was taken on B, for a call from A to either B or C, it would be an outgoing call.

The command goes under dial-peer. You need to verify that on B, you reproduce the same parameters as for the "csim" that works.

But it is only a worjaround. Only the PBX people can tell you why your call is not accepted.

Now before you say that I understand they is possible that they don't answer/don't know/cannot be asked, etc.

Cisco Employee

Re: Problem when connecting PBX to Gateway

I think the problem is not related to calling numbers.

Here is the original Q931 setup message that fails -

*Jan 25 16:05:21.645: ISDN Se0/3/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0782

Bearer Capability i = 0x9090A3

Standard = CCITT

Transer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839F

Exclusive, Channel 31

Calling Party Number i = 0x0080, '910945'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '561498'

Plan:Unknown, Type:Unknown

*Jan 25 16:05:21.713: ISDN Se0/3/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x8782

Channel ID i = 0xA9839F

Exclusive, Channel 31

*Jan 25 16:05:21.717: ISDN Se0/3/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x8782

Cause i = 0x80B4 - Service operation violated

Here is the inwards Q931 setup message that works -

Jan 28 10:23:01.761: ISDN Se0/3/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0077

Bearer Capability i = 0x8090A3

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9838C

Exclusive, Channel 12

Calling Party Number i = 0x0083, '1498'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '910941'

Plan:Unknown, Type:Unknown

High Layer Compat i = 0x9181

*Jan 28 10:23:01.781: ISDN Se0/3/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8077

Channel ID i = 0xA9838C

Exclusive, Channel 12

*Jan 28 10:23:03.425: ISDN Se0/3/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8077

Progress Ind i = 0x8588 - In-band info or appropriate now available

*Jan 28 10:23:07.205: ISDN Se0/3/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8077

*Jan 28 10:23:07.257: ISDN Se0/3/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0077

The difference is in the bearer capability. The failing call has a bearer cap of 0x9090A3 - 3.1khz audio. This is for 'speech', but in the past, this was generally used for conditioned fax services.

The working call uses a bearer cap of 0x8090A3, which is 'normal' G711alaw. For whatever reason, it looks like the PBX can't handle the 3.1khz bearer capability.

I can't help noticing you have the following configured under the D channel on Router A and B -

isdn outgoing-voice info-transfer-capability 3.1kHz-audio

This command is going to overide the outgoing bearer cap on both routers, so first thing you need to do is remove it and try the test calls again.

Second thing you need to do - add 'network-clock-select 1 e1 0/3/0' on router B. You might not have noticed it, but the E1 on router B would be seeing incrementing clock slips. Do a 'sh controller e1 0/3/0' before and after the you have added the above command to confirm the clock slips have been cleared.

611
Views
5
Helpful
10
Replies