Hi, thanks for your reply. I already have that command in place. Re the firmware - do you think its the E1 card firmware or something else..?

My new site is sitting of the back of a 100Mb LES circuit, the building is connecter the the WAN point of entry via a 100Mb PAV link (half duplex connection) the WAN link is a 2Mbps MPLS connection to our central site where the UCM publisher is located - I am starting to think that it might be lost h225 signal packets due to the PAV link running at half duplex.

I activated SRST on the H323 gateway and did not have the problems!!!

Hi Rod,

Try this on the pots dial peer:

progress_ind alert strip 8

hth,

nick

hi nick,

I tried your command this morning and it stil didn't work.

We are re-locating out WAN link to the building where the LES 100Mb circuit terminates - rulling out the PAV and Duplex issue - I'm hopping this will solve my issue - will post later today if it has.

any other ideal would be welcome.

Thanks..

Rod

Hi Nick, I have found the following issue from my debug isdn q931 command:

Rining

*Jan 23 12:18:10.431: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 8823

*Jan 23 12:18:10.435: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 07949997718

*Jan 23 12:18:10.435: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x008F

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98382

Exclusive, Channel 2

Progress Ind i = 0x8183 - Origination address is non-ISDN

Calling Party Number i = 0x0081, '8823'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '07949997718'

Plan:Unknown, Type:Unknown

*Jan 23 12:18:10.639: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x808F

Channel ID i = 0xA98382

Exclusive, Channel 2

*Jan 23 12:18:16.279: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x808F

*Jan 23 12:18:23.859: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x008F

Cause i = 0x8090 - Normal call clearing

*Jan 23 12:18:24.039: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x808F

*Jan 23 12:18:24.039: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x008F

Not Ringing

*Jan 23 12:19:33.107: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 8823

*Jan 23 12:19:33.107: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 07949997718

*Jan 23 12:19:33.107: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0092

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98382

Exclusive, Channel 2

Calling Party Number i = 0x0081, '8823'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '07949997718'

Plan:Unknown, Type:Unknown

*Jan 23 12:19:33.287: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8092

Channel ID i = 0xA98382

Exclusive, Channel 2

*Jan 23 12:19:38.723: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8092

*Jan 23 12:19:47.331: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x0092

Cause i = 0x8090 - Normal call clearing

*Jan 23 12:19:47.519: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x8092

*Jan 23 12:19:47.523: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0092

it looks like the Progress Ind i = 0x8183 - Origination address is non-ISDN line is missing from the debug of the phone that didn't have ringback???

any ideas?

That's odd - you're sending ringback in the setup.

What's the full call flow, including protocols and versions of software?

hth,

nick

Hi Nick,

We are using spservicesk9-mz.124-9.t7.bin, the phones are using skinny and the voip gateway is h323.

Call flow is

IP PHONE>LES>PAV>MPLS>UCM

All PSTN numbers break out at local gateway

I heard there was a bug in 12.4 with outgoing PSTN problems, I trying downloading 12.3 SPS and it doesn't have the commands for enabling the E1 card ?...

Thanks

Rod

Hi Nick,

We moved our WAN connection and it hasn't stopped the problem. ringback is still failing sometimes.

I have no idea why you're sending in-band information in a SETUP. It doesn't really make sense.

I would have to read through CUCM traces and dig deeper to figure out why you're doing something like that.

-nick

Any ideas on this onoe ever Rob?

I have the same issue on

H.323 -> gatekeeper -> CVP -> gatekeeper -> CCM - > outbound H323 PSTN.

Same thing no ringback and see that progress is being sent in band.. originating is not ISDN.

Anyways ideas would rock

Chad

Hi Chad,

I changed the configuration on my pots dial-peer and it fixed my problem.

New config:

dial-peer voice 1 pots

tone ringback alert-no-PI

description *** Outgoing calls to PSTN ***

destination-pattern 9T

progress_ind setup enable 3

progress_ind progress enable 8

progress_ind connect enable 8

port 0/0/0:15

good luck

rod