Ring Back Tone issue

[czerewacz]

Dear all:

I need some light to continue troubleshooting a Ring Back tone issue. The problem is that it is only happening when someone calls to the USA DID number from an USA line. ( I tested from an Argentina trunk and Germany trunk and there is RBT)

I have a CUCME wich is also an H323 gateway.

This is the topology more or less:

[USA DID Provider] ---SIP Trunk---[SBC]---GK/H323----[CME]----IP Phones

This is the config

voice call send-alert

voice rtp send-recv

!

voice service voip

h323

  ras rrq dynamic prefixes

!

voice class codec 1

codec preference 1 g729r8 bytes 60

dial-peer voice 1 voip

huntstop

destination-pattern .T

voice-class codec 1

session target ras

dtmf-relay h245-alphanumeric

fax protocol t38 nse ls-redundancy 2 hs-redundancy 2 fallback pass-through g711alaw

!

dial-peer voice 3 voip

voice-class codec 1

incoming called-number .T

!

gateway

timer receive-rtp 1200

!

!

telephony-service

max-ephones 20

max-dn 144

ip source-address x.x.x.x port 2000

auto assign 1 to 20

service phone pcPort 1

service phone settingsAccess 2

timeouts interdigit 3

  time-zone 25

time-format 24

date-format dd-mm-yy

max-conferences 8 gain -6

transfer-system full-consult

transfer-pattern *

transfer-pattern .T

!

!

ephone-dn  1  dual-line

number xxx no-reg primary

!

!

ephone-dn  2  dual-line

number xxx no-reg primary

!

!

ephone  1

mac-address x.x.x

type 7941

button  1:2

!

!

!

ephone  2

mac-address x.x.x

type 7942

button  1:1

I tested serveral configurations regarding RBT:

- Remove the global voice call send-alert

- Configured the progress_ind setup enable 3, 1, 0 under dial-peer 1

- Configured the tone ringback alert no PI

- Tested the delay transport address command

Can anyone help me? Which debugs should i run to proper catch this?

Thanks!!

Marcelo

[czerewacz]

One more:

If i assing the USA DID to an extension that is behind an other H323 gateway with FXS cards, I can heard the ring back tone.

Any idea?

[czerewacz]

Debug cch323 h225  - This is the call to the DID

un 10 22:50:17.535: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type SETUPIND_CHOSEN

Jun 10 22:50:17.535: //-1/xxxxxxxxxxxx/H323/setup_ind: Entry

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/setup_ind: callingNumber[3055391450] calledNumber[2362201202]

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/setup_ind: ---- calling IE present

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/setup_ind: ====== PI = 0    ---> This could be the problem?

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/setup_ind: Receive: infoXCap 0

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/setup_ind: Receive: infoXCap ccb 0

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/setup_ind:

setup_ind: is_overlap = 0, info_complete = 0

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/cch323_h225_receiver: SETUPIND_CHOSEN: src address = 172.31.13.253; dest address = 200.12.222.11

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_FS_SETUP_IND while at state H225_IDLE

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/idle_fsSetupInd_hdlr: Setup ccb 0x48EEEAE8

Jun 10 22:50:17.535: //882/67DF242B1C92/H323/act_fastStartSetupInd: full match is found

Jun 10 22:50:17.539: //882/67DF242B1C92/H323/act_fastStartSetupInd: codec match = 1

Jun 10 22:50:17.539: //882/67DF242B1C92/H323/cch323_h225_set_new_state: Changing from H225_IDLE state to H225_REQ_FS_WAIT_FOR_ARQ state

Jun 10 22:50:18.131: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_RAS_SUCCESS while at state H225_REQ_FS_WAIT_FOR_ARQ

Jun 10 22:50:18.131: //882/67DF242B1C92/H323/cch323_h225_set_new_state: Changing from H225_REQ_FS_WAIT_FOR_ARQ state to H225_REQ_FS_SETUP state

Jun 10 22:50:18.131: //882/67DF242B1C92/H323/cch323_create_incoming_callinfo_block: peer 45580F14, voice_peer_tag 3, ccb: 48EEEAE8

Jun 10 22:50:18.135: //882/67DF242B1C92/H323/cch323_h225_handle_deferred_ind: UnBuffering deferred indications

Jun 10 22:50:18.147: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_CALLPROC while at state H225_REQ_FS_SETUP

Jun 10 22:50:18.147: //882/67DF242B1C92/H323/cch323_h225_set_new_state: Changing from H225_REQ_FS_SETUP state to H225_ACC_FS_CALLPROC state

Jun 10 22:50:18.147: //882/67DF242B1C92/H323/generic_send_callproc: ====== PI = 0

Jun 10 22:50:18.147: //882/67DF242B1C92/H323/fastStartIdle: ccb->status_1 = 0x1

Jun 10 22:50:18.155: //-1/xxxxxxxxxxxx/H323/cch323_post_call_service_msg: callID=882, notify data mask=0x00000007

Jun 10 22:50:18.155: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_ALERT while at state H225_ACC_FS_CALLPROC

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/cch323_h225_set_new_state: Changing from H225_ACC_FS_CALLPROC state to H225_ACC_FS_ALERT state

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/generic_send_alert: ====== PI = 0

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/generic_send_alert: get ALERT displayInfo

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_NOTIFY while at state H225_ACC_FS_ALERT

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/send_notify_msg: Notify data found, mask=0x00000007

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/send_notify_msg: Sending NOTIFY Display Info IE =

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/send_notify_msg: Sending NOTIFY Notification Indicator IE = 113

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/send_notify_msg: Sending NOTIFY Connected Number as ASN non-std

Jun 10 22:50:18.159: //882/67DF242B1C92/H323/send_notify_msg: [cnum]/[oct]/[oct3a] = [2362201202]/[0x00]/[0x00]

Jun 10 22:50:18.735: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type FACILIND_CHOSEN

Jun 10 22:50:18.735: //882/67DF242B1C92/H323/cch323_h225_receiver: FACILIND_CHOSEN: src address = 172.31.13.253; dest address = 200.12.222.11

Jun 10 22:50:18.735: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_FACILITY_IND while at state H225_ACC_FS_ALERT

Jun 10 22:50:18.739: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_TRANSMIT_TUNNELING while at state H225_ACC_FS_ALERT

Jun 10 22:50:18.739: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_TRANSMIT_TUNNELING while at state H225_ACC_FS_ALERT

Jun 10 22:50:18.739: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_TRANSMIT_TUNNELING while at state H225_ACC_FS_ALERT

Jun 10 22:50:18.743: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type FACILIND_CHOSEN

Jun 10 22:50:18.743: //882/67DF242B1C92/H323/cch323_h225_receiver: FACILIND_CHOSEN: src address = 172.31.13.253; dest address = 200.12.222.11

Jun 10 22:50:18.743: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_FACILITY_IND while at state H225_ACC_FS_ALERT

Jun 10 22:50:18.743: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_TRANSMIT_TUNNELING while at state H225_ACC_FS_ALERT

Jun 10 22:50:19.299: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type FACILIND_CHOSEN

Jun 10 22:50:19.299: //882/67DF242B1C92/H323/cch323_h225_receiver: FACILIND_CHOSEN: src address = 172.31.13.253; dest address = 200.12.222.11

Jun 10 22:50:19.299: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_FACILITY_IND while at state H225_ACC_FS_ALERT

Jun 10 22:50:20.059: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type FACILIND_CHOSEN

Jun 10 22:50:20.059: //882/67DF242B1C92/H323/cch323_h225_receiver: FACILIND_CHOSEN: src address = 172.31.13.253; dest address = 200.12.222.11

Jun 10 22:50:20.059: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_FACILITY_IND while at state H225_ACC_FS_ALERT

Jun 10 22:50:20.059: //882/67DF242B1C92/H323/run_h225_sm: Received event H225_EV_H245_SUCCESS while at state H225_ACC_FS_ALERT