As mentioned above i have a requirement to connect our current OCS infrastructure to our local PBX (Nortel BCM50).
Now the BCM50 doesn't have v3 of the firmware which would allow it to establish a direct sip trunk to the OCS server and it only has H.323 capabilities (and i believe they are restricted).
At the moment im only trying to establish the h.323 part with the BCM50 which is having a few problems ...
I have a dialplan in the BCM50 and my phone extension is 251 ... so when i try to start a connection to my extension from the router i get the following disconnect ...
csim start 251
csim: called number = 251, loop count = 1 ping count = 0
*Jun 10 09:13:03.579: h323chan_chn_process_read_socket: fd=2 of type CONNECTED has data
*Jun 10 09:13:03.583: h323chan_chn_process_read_socket: fd=2 of type CONNECTED has data
*Jun 10 09:13:03.583: h323chan_chn_process_read_socket: h323chan accepted/connected fd=2
*Jun 10 09:13:03.583: //-1/xxxxxxxxxxxx/H323/cch323_gw_process_read_socket: owner_data=0x65052B44, len=50, msgPtr=0x64F5657C
*Jun 10 09:13:03.583: //-1/xxxxxxxxxxxx/H323/cch323_gw_process_read_socket: Received msg for H.225
Hex representation of the SETUP TPKT received: 080280075A080280AF7E0026052580060008914A000411181100BC86903054D511DE800FD86FBE38ED6B0100014010800100
Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length : 2
CRV Value : 0x8007
Message Type : 0x5A: RELEASE_COMP
Cause: Length Of IE=2
User-User: Length Of IE=38
Data 052580060008914A000411181100BC86903054D511DE800FD86FBE38ED6B0100014010800100h225ParseData: Q.931 RELEASE COMPLETE received on fd=2
*Jun 10 09:13:03.583: //-1/xxxxxxxxxxxx/H323/cch323_h225_receiver: Received msg of type RELEASEIND_CHOSEN
*Jun 10 09:13:03.583: //7/BC869030800E/H323/release_ind: Disconnect cause 47 location code 0
*Jun 10 09:13:03.583: //-1/xxxxxxxxxxxx/H323/h323_set_release_source_for_peer: ownCallId, src
*Jun 10 09:13:03.583: //7/BC869030800E/H323/cch323_h225_receiver: RELEASEIND_CHOSEN: src address = 192.168.1.4; dest address = 192.168.1.20
*Jun 10 09:13:03.583: //7/BC869030800E/H323/run_h225_sm: Received event H225_EV_RELEASE_IND while at state H225_REQ_FS_SETUP
*Jun 10 09:13:03.583: //7/BC869030800E/H323/cch323_traverse_enum_contact_list: State = 2
*Jun 10 09:13:03.587: //7/BC869030800E/H323/cch323_do_call_disconnect: gw_id=1, discCause=47
*Jun 10 09:13:03.587: //-1/xxxxxxxxxxxx/H323/cch323_iev_queue_service: Dispatch 0x9 internal event to H225 SM
*Jun 10 09:13:03.587: //7/BC869030800E/H323/run_h225_sm: Received event H225_EV_RELEASE while at state H225_REQ_FS_SETUP
*Jun 10 09:13:03.587: //7/BC869030800E/H323/cch323_h225_send_release: Cause = 47; Location = 0
*Jun 10 09:13:03.587: //7/BC869030800E/H323/cch323_h225_send_release: h225TerminateRequest: src address = -1062731516; dest address = 192.168.1.20
*Jun 10 09:13:03.587: compose_TunnelledSignallingMessage_ciscoNo tunnelled content.
Now the h.323 setup should be really straight forward as there is no catch (all numbers to the voip dialpeer ...)
Can you give some help please ? Or point me to documents which will allow me to configure the things properly (i think the PBX may have some configuration missing)
Thanks in advance ...