 Mediatrix 4400 BRI gateway. What happens here ?
Hello everybody.
We are having two kind of problems related to configuration of a Mediatrix 4404 BRI Gateway, but previous to put you in details of the problems let me explain our topology and situation:
We are a company with multiple offices in USA, Mexico, Costa Rica, Brazil, Argentina and Uruguay. We contracted an VoIP service from an Argentinean provider (IPLAN NETWORKS), and they supply us with typical SIP carrier services. Our VoIP service is hosted by them, and the core VoIP systems run by IPLAN are based on BroadWorks products.
Due to the nature of our business, we currently have circa 100 VoIP extensions (A mix of Phones (Linksys), FXO analog adaptors, Auto attendants, Hunting Groups, etc), each one mapped with a DID telephone number with Argentinean numbering. Also, we have in each of our offices, additional PSTN lines to interconnect with the local Telco. In Mexico, Costa Rica, USA and Brazil, we use standard POTS analog lines, routed using both Linksys SPA3102 and Audiocodes MP-118 FXO gateways.
The only exception is the Montevideo office, where the telco gives us ISDN (BRI) lines instead of old POTS services. We have 3 BRI lines (For a total of 6 interfaces), and our plan was to interconnect these lines with our VoIP network in a similar fashion we do with the rest of the offices. This is the reason why we chose the Mediatrix 4404 Gateway as a solution for our needs.
We have installed the gateway according to the Hardware Installation Guide, and performed the configuration according to instructions both in the Software Configuration Guide and the Configuration note 245 (Mediatrix 4400 Digital Gateway VoIP Gateway with the PSTN), and currently we have the following settings working fine:
- Network: Both interfaces (Rescue with Static IP and UpLink with DHCP) well configured and working fine. No VLAN, QoS or Local Firewall configurations.
- SIP: Registrar Host, Proxy Host and Outbound Proxy Host properly configured as default servers. Bri1, Bri2 and Bri3 Endpoints properly configured using three Authentication entries. All three endpoints are registering OK in the registrar server trough the default gateway and are unlocked. No special configuration is set in the SIP/Misc entries.
- ISDN: The three interfaces are configured in the same way. Relevant parameters are: Endpoint Type: TE, Clock mode: Auto (Get clock from the PSTN terminal adapter, recommended by the telco), Connection Type: Point to Multipoint (We also tried the Point to Point configuration with the same results). The remaining settings are defined as the default values.
- Telephony: In the call routing configuration, we have defined three routes for incoming calls: isdn-Bri1 to sip-default, isdn-Bri2 to sip-default and isdn-Bri3 to sip-default, and one route for outgoing calls sip-default to hunt-HUNT_PSTN, where the HUNT-PSTN are defined as a hunt group for the three isdn-Bri destinations. All the remaining parameters under Telephony are in the default configuration.
The situation we are facing is this:
1) ISDN ports:
When the ISDN service starts, the interface Physical Link and the Signaling went UP, but at 15 seconds the signaling went down, and at 2 minutes, the physical link also went down. If I make a call from an external line to the number associated to this particular Bri, both interfaces went UP, and then goes down in the same fashion (Signaling at 15 seconds, Physical at 2 minutes). From the phone used to call the number of Bri1, I only hear a BUSY tone.
Because I’m not able to make an outgoing call (yet, please see problem number 2), I can’t tell you if the behavior is the same for outgoing calls.
My first question: I suppose is normal the signaling went down if no one is using the Bri, so the 15-seconds period to the signalinks went down looks correct, but what i´m not sure is correct is the physical link to went down in the 2-minute period. It seems to be a configuration problem. What can be wrong configured here ?
Just to help the troubleshooting, I make a local loop setting Bri1 as TE and Bri2 as NT (the idea was to “emulate” the telco network terminal using the Bri2 as an NT) and connecting both ports with a standard UTP a cable, and in this situation both the signaling and the physical link remain up all the time.
Also, we connected the Bri2 configured as NT with our legacy Siemens PBX (using the TE interface) and the signaling went down if clock mode is set to auto, but remains if the signaling is set by the Bri2 interface (Master). All this points to me to think there is a setting we need to adjust when connecting with the telco. Any ideas ??
2) Routing:
The second thing we are facing, seems to be an interpretation problem of us: Assuming incoming calls are entering well thought the Bri interface (because, as stated previously, when a call is placed to the Bri number, both the signaling and the physical link went up), we are missing one piece on the puzzle, because we don’t found where to set which one is the physical device where incoming calls are routed.
As I stated previously, we created 3 routes for calls sourcing in Bri1, Bri2 and Bri3 with destination to sip-default. But, what means exactly sip-default ?? What is the configuration we are missing to indicate “sip-defaults destination must ring on extension 1152767928” ??
I think a similar issue is what actually avoid us to place calls using the outgong calls routes, but this is just a supposition.
Can you help us with these issues ?? If needed, I can temporally publish the interface in the web to allow you to remotely access the gateway. Just ask, and will be done in minutes.
Kind regards.
[font=Verdana][size=1][color=#990000][color=#990000][font=Verdana]Mart  |
Re: Mediatrix 4400 BRI gateway. What happens here ? 
Linear Mode
