Connecting a Ericsson webswitch 100 to a M1 analog

[fboucher]

I am trying to use two Ericsson VoIP gateway (Webswitch 100)
to replace tie lines between a M1 PBX and a Hitachi PBX.

On the test setup, I can place an incoming call to the
M1 through the VoIP gateway. This works fine. The call
comes in through the M1 route 6, which forward it to the
automated attendant.

The problem is for the outgoing call from the M1 to the
VoIP: from a phone, I place a call (through DN 5000),
the trunk (TN: 12 1 11 3) is activated, and the VoIP
makes the connection. I can then ear my other person
on the line (incoming audio to the M1 works), but my
speech is not working! (outgoing audio from the M1 is
silent.) A butt set connected on the BIX of the trunk
does not get ANY audio when I speak. I tried to use
other trunk TNs, same result. I think this is a configuration problem. Any help or suggestion will be
very much appreciated!

My M1 is a 51C with release 22.16, no PRI packages, so I
MUST interface only with analog trunk (NT8D14) cards.

Here is the trunk config:

TN   012 1 11 03 
TYPE COT 
CDEN 8D
CUST 0 
XTRK XUT 
TIMP 600 
BIMP 3COM
NCOS 0 
RTMB 5 1 
NITE 
SIGL LOP 
SUPN YES 
STYP BTS 
CLS  UNR DTN WTA LPR APN 
     P10 TRC LOL 
TKID 2
DATE  7 OCT 2003 

And here the route data block config:
ld 21
PT1000 

REQ: prt
TYPE: rdb
CUST 0
ROUT 5

TYPE RDB 
CUST 00 
ROUT 5 
DES  OUTGOING
TKTP COT 
PRIV NO  
SAT  NO  
RCLS EXT 
PTYP ACO 
AUTO NO  
ICOG OGT 
RANX NO  
SRCH LIN 
STEP 
ACOD 5000
CPP  NO  
TARG 
OABS 
TIMR ICF 512 
     OGF 512 
     EOD 13952 
     DSI 34944 
     NRD 10112 
     DDL 70 
     ODT 4096 
     RGV 640 
     FLH 510 
     GRD 896 
     SFB 3 
     CRD 512 
     TFD 0 
     LEXT 100 
SST  3 0 
NEDC ETH 
FEDC ORG 
CPDC NO  
SPCT IMM 
HOLD 02 02 40 
SEIZ 02 02 
RGFL 02 02 
RVSD 08 31 
ILLR 02 02 
CDR  NO  
MUS  NO  
MR   NO
MANO NO  
EQAR NO  
FRL  0 0 
FRL  1 0 
FRL  2 0 
FRL  3 0 
FRL  4 0 
FRL  5 0 
FRL  6 0 
FRL  7 0 
TTBL 0 
OHTD NO  
MCTS NO  
ALRM NO  
ART  0 
AACR NO

Thanks,
Francois

 

[RFWatts]

Ah...the old h.323 problem rises again! This is a common h.323 problem across routers. I'm guessing that you have the two sites connected by routers correct? Basically, the UDP packets are getting addressed to the internal address of the remote device, so when they hit the router, they get sent off to never-never land! Probably the easiest fix here is to use the cisco h.323 fixup command in your routers (if they are cisco and IOS 12+). There are a couple of other things you can do as well. You can use a VPN tunnel between the devices so that they appear to be on the same LAN. The other method that I have had limited sucess (with the WebSwitch P4) is add a NAT entry for the webswitch port. You can download the config file from the webswitch to determine what port it is using. BTW, you can also change the port in the config file, and upload it to the unit for a non-standard configuration. If you use the wizzard, it will configure the webswitch for the standard h.323 ports.

Hope this helps!

 

[fboucher]

Hmmm, I'm afraid this can't be it!
In this test setup, the two webswitches are connected
on a 10baseT hub. Not even a switch! Thus, this eliminates
any suspected router problem.

I think the problem is on the Meridian side, because
I don't get any audio out when I tap the wiring between
the M1 and the Webswitch.
If I go into ld 36 (trunk test),
then I call 12 1 11 3,
I then get the audio 1KHz tone which is correctly heard
to the end destination. The butt set taped onto the
wires also gives the 1 KHz tone.

So far, I am in deep technical interrogation!

Best regards,

Francois


If life was simple, it would not be complicated.

 

[RFWatts]

Are you able to get end to end audio using a 2500 set plugged into each webswitch?

 

[fboucher]

I got the answer to my problem:
As this is defined as an outgoing trunk route, the
Meridian will block the output of any audio until
the user dials a least one DTMF digit.
it then wait 15 seconds for the other digits, then
timeouts and hangup.
To work, the user MUST dial at least 3 digits. Then,
there is no timeouts, and the conversation works as
planned.

The configuration above are thus directly usable for the
interfacing of a M1 with a webswitch.

Best regards,

Francois

If life was simple, it would not be complicated.

 

[RFWatts]

Thanks for posting the resolution...I'm considering installing a 4-port as a tie between my Meridian, and Definity. I've configured a tie between a Partner and Definity, and the audio quality was amazingly good.