Re: IPVC 3525 PRI GW

droessler · ‎10-02-2002

I have TCS4 enabled on the GW and in the WAN Paramters. I am have # set as the Delimiter.

I have an internal H323 endpoint w/ E.164 1000. When a caller dials the IPVC GW number 1866XXXXXXX#1000 it doesnt route to the endpoint - it just stays in the IVR.

Is it that I have missed something in the setup? The caller is using a Sony5100.

aglowack · ‎10-02-2002

Have you tried disabling the IVR and see if the call will route?

frank.yule · ‎10-03-2002

I have had identical problems with my gateway. I bypassed the problem by entering two # characters instead of one. My calls were then routed to my endpoints directly.

droessler · ‎10-03-2002

Did you have the caller enter two # or did you enter the ## in the WAN call paramter and the Delimiter setup on the GW?

Disabling IVR is not an option as we have multiple endpoints and VC's going on at one time.

frank.yule · ‎10-03-2002

The caller has to enter two # at their end....

I have just tested again and if you use one hash the IVR intercepts the call, but if you enter two # then you call the endpoint direct

jdrohen · ‎06-30-2005

I’m trying to dial my IPVC IVR from a IP phone. I have set up H.225 trunk in CCM and a route pattern to point to that trunk. I created a static e.164 address on the gatekeeper to point to the IVR. When I dial the IVR from a phone “IVR Application” shows up on the phone but disconnects immediately. I have done the same process with my MCU and when I dial the pattern it drops me into an ad-hoc conference. I need the users to be able to dial the IVR and enter a conference ID. Does anyone know what steps I’m missing?

Thanks,

Jesse

gatekeeper

zone local CTSF3745 10.0.0.19

alias static 10.0.0.25 1620 gkid CTSF3745 terminal ras 10.0.0.25 1619 e164 620

gw-type-prefix 1#* default-technology

no use-proxy CTSF3745 default inbound-to terminal

no use-proxy CTSF3745 default outbound-from terminal

no shutdown

CTSF3745#sh gatekeeper endpoints

GATEKEEPER ENDPOINT REGISTRATION

================================

CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags

--------------- ----- --------------- ----- --------- ---- -----

10.0.0.19 1720 10.0.0.19 1719 CTSF3745 MCU

H323-ID: IPVC3540

E164-ID: 610

E164-ID: 80

E164-ID: 81

E164-ID: 82

E164-ID: 83

E164-ID: 84

E164-ID: 85

E164-ID: 86

E164-ID: 87

E164-ID: 881

E164-ID: 882

E164-ID: 887

E164-ID: 888

E164-ID: 889

E164-ID: 89

10.0.0.25 1820 10.0.0.25 1719 CTSF3745 H320-GW

H323-ID: RV-GW-172024054241

Voice Capacity Max.= Avail.= Current.= 0

10.0.0.25 1620 10.0.0.25 1619 CTSF3745 TERM S

H323-ID: CTSFIVR

E164-ID: 620 (static)

10.0.0.100 56228 10.0.0.100 49424 CTSF3745 VOIP-GW

H323-ID: TRUNK_IPVC_1

Voice Capacity Max.= Avail.= Current.= 0

10.0.0.101 60430 10.0.0.101 50010 CTSF3745 VOIP-GW

H323-ID: TRUNK_IPVC_2

Voice Capacity Max.= Avail.= Current.= 0

150.114.144.101 1720 150.114.144.101 17300 CTSF3745 TERM

E164-ID: 12545327066

H323-ID: IPOWER9000

Total number of active registrations = 6

jdrohen · ‎06-30-2005

Here is the info while telneted into the GW card. I'm not sure what the "Mandatory information element missing" is?

Thanks,

Jesse

1964999|USER INFO|#|INFO| ###############################################

##########################################

1964999|USER INFO|CALL SETUP|INFO| CALL SETUP: From IP, Bearer Capability

Rate=[64 Kbps], Actual Rate=[64 Kbps] taken from Bearer Caps

rcNum=[2469] destNum=[] bitRate=[64 Kbps] restricted=[NO]

1964999|USER INFO|CALL SETUP|INFO| PORTS ALLOCATION: Allocated Rate=[64 Kb

ps, 1 Ports], Actual Rate=[64 Kbps]

DN: line[1], B-Channel[13], calledAddr[], callingAddr[2469]

DN, dropReason=[Mandatory information element missing]

DN, dropReason=[Mandatory information element missing]

1965013|USER INFO|Sess[0]|#|INFO| #######################################

##################################################

1965013|323 ADAPTER|DEFAULT SWITCH|ERROR| appGen2LanCallDisconReason: Val

ue: [q931 Disconnect Reason]=[96]