IPO to BCM50 via H323

[texmatlock]

So I set this up. I can successfully call from the BCM to the IPO.
When I attempt to call from the IPO to BCM No Luck.
My trace code looks like this

3549744mS H323Evt: v=0 stacknum=18 State, new=NullState, old=NullState id=-1
3549745mS H323Evt: v=0 stacknum=18 State, new=Initiated, old=NullState id=1950
3549746mS H323Tx: dst=172.20.2.10:1720
H323 Pcol=08(Q931) Reflen=2 ref=0008(Remote)
Message Type = Setup
3549933mS H323Rx: src=172.20.2.10:1720
H323 Pcol=08(Q931) Reflen=2 ref=0008(Local)
Message Type = ReleaseComplete
3549934mS H323Evt: v=0 stacknum=18 State, new=NullState, old=Initiated id=1950
3558369mS H323Evt: Removing inactive H323 socket from 10.4.20.1:7833
3573374mS H323Rx: src=10.4.20.1:7834
H323 Pcol=0D(UNK) Reflen=0 ref=(Remote)
0000 0d 00 1f 01 01 00 00 00 2f 00 00 00 08 00 00 00 ......../.......
0010 01 00 00 00 2b 49 50 20 35 30 30 20 56 32 00 ....+IP 500 V2.

Can someone point me in the right direction based on this trace?

 

[phoneguy610]

have you watched the call come through in the bcm monitor tool.

i think i had this problem once before and it was because i programmd the rec digits as public instead of private

review this doc:

http://downloads.avaya.com/css/P8/documents/100164746

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars

 

[texmatlock]

Well that's at least something I can pass to my BCM know-it-all partner and make it his problem . Thanks. I did watch an outbound call on the IPO System status and it said call rejected by the BCM (reason #28 BCM did not recognize the extension I was calling), so that confirms that you are pointing me in the right direction.

My main concern was that it possibly could not be done over H323. Lots of folks are telling me you have to have a SIP trunk from IPO to BCM.

 

[phoneguy610]

ooo brain fart... i didnt even realize you were using h323

im not sure you can , i have setup all mine with a sip trunk and thats with the documenation calls for

my guess is you just wont get all of the networking features but you should still be able to dial across

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars

 

[texmatlock]

I can't imagine why it wouldn't be POSSIBLE. I can see there being limitations, but they should still be able to get basic functionality. SIP would be easy. The IP Office really is an easy system to do just about anything with. But this is kinda tricky because comparatively BCMs are so complicated.

Does anyone out there know for sure of this ever being successfully done? BCM_>IPO via H323?