Mexico City / Telmex

[wpetilli]

We are in the process of opening a new remote office in Mexico City. This would be an LSP hung off of my US core 6.0.1. We plan to deploy a G450/s8300D with an MM710 E1/T1 and MM711 and the carrier in country is Telmex.

After a discussion with the carrier, they indicate they use R2 modified interface, which I've never heard of. Sounds as if they don't hand off via ethernet. Does this require a special adapter on the AVAYA end that I'd need to order? We typically just order a MM710 or 710B and connect to carrier via Ethernet.

Also, they indicate they supply the service in increments of 10 channels. Based on asking for 100 DID's we are being quoted 30 channels. I've read through a few threads about Telmex/Mexico City and I want to make sure I'm handling this properly.

If this R2 is some type of protocol, I see in 'disp sys cust' that Multifrequency Signaling is set to 'y'. Is that what I need on the switch end?

Lastly, they mentioned for analog they use G.703. What do I need for something like that?

 

[jimbojimbo]

You are correct. In Mexico you will see Multi-Frequency R2 Protocol. Haven't worked on this in years. You need to make sure you get the correct multifrequency-signaling setup in CM. You can probably google it. Alternative is to work with a local VAR in Mexico who can set the coding for you.

 

[CarlosPrex]

Hi
I hope it helps


G.703 ++++++++++++

It´s coaxial, so you´ll just need the 888A amphenol/coaxial adapter


DS1 ++++++++++++

change ds1 01b03 Page 1 of 1
DS1 CIRCUIT PACK

Location: 01B03 Name: TELMEX DIGITAL
Bit Rate: 2.048 Line Coding: hdb3

Signaling Mode: CAS

Interconnect: CO Country Protocol: 7

Interface Companding: alaw CRC? n
Idle Code: 11111111


Slip Detection? y Near-end CSU Type: other

Echo Cancellation? n


MULTIFREQUENCY FOR R2 SIGNALING +++++++++

change multifrequency-signaling Page 1 of 4
MULTIFREQUENCY-SIGNALING-RELATED PARAMETERS
Incoming Call Type: group-ii-mfc ANI Prefix:
Outgoing Call Type: group-ii-mfc Default ANI:
Maintenance Call Type: none NEXT ANI DIGIT
Incoming: next-digit
Outgoing: next-digit
Maximum Resend Requests:
Received Signal Gain (dB): 0
Transmitted Signal Gain (dB): -3
Request Incoming ANI (non-AAR/ARS)? y
Outgoing Forward Signal Present Timer (sec): 15
Outgoing Forward Signal Absent Timer (sec): 30
MF Signaling Intercept Treatment - Incoming? n Outgoing: tone
Collect All Digits Before Seizure? n
Overlap Sending on Link-to-Link Tandem Calls? n
Private Group II Permissions and Public Interworking? n

Use COR for All Group II Responses? n
Group II Called Party Category: user-type
Use COR for Calling Party Category? n

change multifrequency-signaling Page 2 of 4
MULTIFREQUENCY-SIGNALING-RELATED PARAMETERS

Request Call Category at Start of Call? n
Restart ANI from Caller Category? y
Number of Incoming ANI Digits: 0
Number of Outgoing ANI Digits: 0
Truncate Station Number in ANI: no
Address Digits Include End-of-digits Signal? n
Call Category for Vector ii-digits? n
Request CPN at Start of Call? n
Do Not Send Group B Signals to CO? n
ANI Source for Forwarded & Covered Calls: caller

INCOMING OUTGOING
ANI Available:
ANI Not Available:

change multifrequency-signaling Page 3 of 4
MULTIFREQUENCY-SIGNALING-RELATED PARAMETERS

INCOMING FORWARD SIGNAL TYPES INCOMING BACKWARD SIGNAL TYPES
(Tones from CO) (Tones to CO)

Group-I Group-II Group-A Group-B
11: ignored 1: normal 1 : next-digit 1 : free
12: ani-not-avail 2: normal 3 : end-of-dial 2 : busy
13: ignored 3: normal 6 : send-ani 4 : congestion
14: ignored 4: normal : 7 : intercept
15: end-of-ani 5: normal : :
6: normal : :
7: normal : :
8: normal : :
9: normal : :
10: normal : :
11: normal : :
12: normal : :
13: normal : :
14: normal : :
15: normal : :

change multifrequency-signaling Page 4 of 4
MULTIFREQUENCY-SIGNALING-RELATED PARAMETERS

OUTGOING FORWARD SIGNAL TYPES OUTGOING BACKWARD SIGNAL TYPES
(Tones to CO) (Tones from CO)

Group-I Group-II Group-A Group-B
12: ani-not-avail 2 : normal 1: next-digit 1: free
15: end-of-ani 2 : attendant 2: restart 2: busy
: 2 : data-call 3: end-of-dial 3: congestion
: : 4: congestion 4: congestion
: : 5: congestion 5: intercept
: 6: send-ani 6: congestion
: 7: congestion 7: congestion
: 8: congestion 8: congestion
: 9: congestion 9: congestion
: 10: congestion 10: congestion
: 11: congestion 11: congestion
: 12: congestion 12: congestion
: 13: congestion 13: congestion
: 14: congestion 14: congestion
: 15: congestion 15: congestion


TRUNK GROUP SETTINGS *********************

change trunk-group 1 Page 1 of 11
TRUNK GROUP

Group Number: 1 Group Type: tie CDR Reports: y
Group Name: TELMEX DIGITAL COR: 1 TN: 1 TAC: 801
Direction: two-way Outgoing Display? n Trunk Signaling Type:
Dial Access? y Busy Threshold: 99 Night Service:
Queue Length: 0 Incoming Destination:
Comm Type: voice Auth Code? n
Trunk Flash? n

TRUNK PARAMETERS
Trunk Type (in/out): wink/immed Incoming Rotary Timeout(sec): 5
Outgoing Dial Type: mf Incoming Dial Type: mf
Disconnect Timing(msec): 500
Digit Treatment: insertion Digits: 9*
Expected Digits: 4 Sig Bit Inversion: none
Analog Loss Group: 9 Digital Loss Group: 13
Incoming Dial Tone? y

Disconnect Supervision - In? y Out? y
Answer Supervision Timeout: 0 Receive Answer Supervision? y


change trunk-group 1 Page 2 of 11
TRUNK FEATURES
ACA Assignment? n Measured: none
Internal Alert? n Maintenance Tests? y
Data Restriction? n

Used for DCS? n
Suppress # Outpulsing? n
Seize When Maintenance Busy: neither-end



Connected to CO? n
MF Tariff Free? n
Ds1 Echo Cancellation? n


-Carlos

 

[wpetilli]

That is super helpful.. thanks so much!

 

[wpetilli]

If I can ask... we're a bit confused with what the carrier is stating about the handoffs. For the 30 channel voice circuit is that handed off ethernet (since the AVAYA module is a MM710B) or Coax? or is the G.703/coax part related to the out of band lines that won't be terminating onto the AVAYA GW?

 

[CarlosPrex]

Sorry
Just noticed it´s a G450/s8300D with an MM710 E1/T1, then you´ll need a balloon.
The 888A adaptor is an amphenol/coaxial adapter, as mentioned.