Meridian 11c rls 4.5 and BCM50 rls 3 H323 Interconnection

[lexer]

Hi, I've a Meridian 11c rls 4.5 and BCM50 rls 3 H323 interconnected via H323 Iptrunk, I can call from the BCM50 rls 3 to Meridian but I cannot call from The Meridian to the BCM50 rls 3. Before, I have a BCM50 rls 2 working with the meridian, I could call from the Meridian to BCM50 rls 2 and viceversa. The BCM50 rls 2 crashed, I installed a new BCM50 rls 3 with the same programming that had BCM50 rls 2.

BCM Rls 3 Parameters

Ip 192.168.2.19

======

Dialing Plan Routing
*******************************

Destination Codes
---------------------
2
Normal route: 01
Absorbed Lenght: 0

Routes
01
Use Pool: BLOCA
DN Type: Private

Private Network
---------------------
Private Network Type: CDP
Private Network Id: 1
Private Network DN lengtg: 3

Telephony Resources:
*************************
Routing Table
-------------
Name: CCS
Destination Digit: 2
IP: 1.0.0.248
GW Type: Other
MCDNProtocolo: None
VoIP protocol: H323

H323 Setting
------------
Call Signaling: Gatekeeper Resolved
Alias Names -- NAME: MERCANTILBCM50
registration TTL: 60
Gatekeeper TTL: 30

H323 Media Parameters
------------

Codes Selected:
G.729
G.711

G.729 payload -- 30
G.711 payload -- 30

Target Line
- Line 149 -Controlset: 101 -Line Type: Public
- Primeset:101 -Public received#:101 -Private received#:101

Meridan Ip Information:

ELAN:
CS 1.0.80.2
SS 1.0.80.3
MC 1.0.80.4

TLAN:
Node 1: 1.0.0.247
SS 1.0.0.248
MC 1.0.0.249


When I trace a Incomming call on Meridian Ip trunk port 61 0 (coming from BCM50 rls 3):

.trak 61 0

ACTIVE VTN 061 0 00 00

ORIG TN 003 0 00 00 KEY 0 SCR MARP CUST 0 DN 0 TYPE 3904
VGW TN 009 0 00 12
FAR-END H.323 SIGNALLING IP: 1.0.80.4
FAR-END MEDIA ENDPOINT IP: 1.0.0.249 PORT: 5224
TERM VTN 061 0 00 00 VTRK IPTI RMBR 10 1 OUTGOING VOIP GW CALL
FAR-END H.323 SIGNALLING IP: 0.0.0.0
FAR-END MEDIA ENDPOINT IP: 0.0.0.0 PORT: 0
MEDIA PROFILE: CODEC n/a A-law PAYLOAD 1 ms VAD OFF
DIAL DN 101
MAIN_PM DIAL AUX_PM COMPLETE
TALKSLOT ORIG 14 TERM 14
EES_DATA:
NONE
QUEU NONE
CALL ID 0 1700


AUX NARS



---- ISDN ISL CALL (TERM) ----
CALL REF # = 4384
BEARER CAP = VOICE
HLC =
CALL STATE = 3 OUTGOING
CALLING NO = 0 NUM_PLANRIVATE TON:ABBREVIATED ESN:CDP
CALLED NO = 101 NUM_PLANRIVATE TON:ABBREVIATED ESN:CDP

Trace of an Outgoing call from Meridian to BCM50 rls 3 Ip trunk 61 0, It shows in FAR-END ip 0.0.0.0

.trak 61 0

ACTIVE VTN 061 0 00 00

ORIG TN 003 0 00 00 KEY 0 SCR MARP CUST 0 DN 0 TYPE 3904
VGW TN 009 0 00 14
FAR-END H.323 SIGNALLING IP: 1.0.80.4
FAR-END MEDIA ENDPOINT IP: 1.0.0.249 PORT: 5228
TERM VTN 061 0 00 00 VTRK IPTI RMBR 10 1 OUTGOING VOIP GW CALL
FAR-END H.323 SIGNALLING IP: 0.0.0.0
FAR-END MEDIA ENDPOINT IP: 0.0.0.0 PORT: 0
MEDIA PROFILE: CODEC n/a A-law PAYLOAD 1 ms VAD OFF
DIAL DN 101
MAIN_PM DIAL AUX_PM COMPLETE
TALKSLOT ORIG 17 TERM 17
EES_DATA:
NONE
QUEU NONE
CALL ID 0 1699


AUX NARS



---- ISDN ISL CALL (TERM) ----
CALL REF # = 4384
BEARER CAP = VOICE
HLC =
CALL STATE = 3 OUTGOING
CALLING NO = 0 NUM_PLANRIVATE TON:ABBREVIATED ESN:CDP
CALLED NO = 101 NUM_PLANRIVATE TON:ABBREVIATED ESN:CDP

Please any ideas?

 

[Firebird Scrambler]

I have provided you with a useful guide that was released by Nortel many years ago on this problem.

You might want to use the BCM Monitor tool to see if you can see any incoming traffic from the CS1000 end.

Have you got the site ID from the original BCM 50 and the site ID for the replacement one as it might be an idea to compare the keycodes in case you don't have all the packages on the release 3.0 system.

I seem to recall that there were slight changes in the H323 configuration at BCM 50 3.0.


Firebird Scrambler
Nortel and Avaya Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Very advance high level knowledge on Linux BCM with keycode support

http://www.linkedin.com/in/davidbromley

 

[Firebird Scrambler]

I've uploaded another Avaya guide that mainly relates to SIP trunking for your reference.


Firebird Scrambler
Nortel and Avaya Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Very advance high level knowledge on Linux BCM with keycode support

http://www.linkedin.com/in/davidbromley

 

[lexer]

Thanks for your answers, I was wrong, The new BCM50 I installed is rls 5.0, the old BCM50 rls 2 and the BCM50 rls5 have the same keycodes(The new BCM50 rls5 just has 2 Ip trunks):

SW Version BCM50 Release 5.0
ACTIVE Int Analog Trunk 4
ACTIVE Int Analog Sets 4
ACTIVE Int Digital Sets 12
ACTIVE Exp Port 1
ACTIVE VM seat 8
ACTIVE VoIP GW Trunk 2
ACTIVE UM seat 8
ACTIVE Fax Messaging 1

BCM Rls 2
Feature licenses
Status Name Data
ACTIVE VM seat 8
ACTIVE VoIP GW Trunk 4
ACTIVE Int Analog Trunk 4
ACTIVE Int Analog Sets 4
ACTIVE Int Digital Sets 12
ACTIVE Exp Port 1

 

[lexer]

Thanks guys, I solve the problem, It was a triviality, I forgot to program target lines for ringing on stations

 

[Firebird Scrambler]

Your BCM keycodes for both systems will accept either SIP or H323. The trunks can be increased up to 12.

It's important to find out if the BCM is seeing any incoming traffic. Look for any small changes against the VoIP lines, usually line 001. Any change in the time on the BCM monitor tool would indicate that it's trying to receive the call.

Contact me if you require any more help.


Firebird Scrambler
Nortel and Avaya Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Very advance high level knowledge on Linux BCM with keycode support

http://www.linkedin.com/in/davidbromley