Audiocodes

[AELMAN]

thread798-1589491

Can not seem to get international calls to route through the
MP-112, always seeing 100 and 100011 being delete for international calls national calls are working fine

.trac 200 0 0 0 dev

ACTIVE VTN 200 0 00 00

ORIG VTN 200 0 00 00 IPTI RMBR 20 1 INCOMING VOIP GW CALL
FAR-END SIP SIGNALLING IP: 192.168.3.229
FAR-END MEDIA ENDPOINT IP: 192.168.3.229 PORT: 6020
FAR-END VendorID: Audiocodes-Sip-Gateway-MP-112 FXS/v.6.20A.022.003
TERM TN 022 23 IPMG 000 0 V PHYSICAL TN 000 0 00 01 DID RMBR 39 23 OUTGO
ING TRUNK CALL
VGW TN 000 0 00 01
FAR-END H.323 SIGNALLING IP: 192.168.98.51
FAR-END MEDIA ENDPOINT IP: 192.168.98.171 PORT: 5202
FAR-END VendorID: Not available
MEDIA PROFILE: CODEC G.711 MU-LAW PAYLOAD 20 ms VAD OFF
RFC2833: RXPT 101 TXPT 101 DIAL DN 90115073003200
MAIN_PM DIAL AUX_PM COMPLETE
TALKSLOT ORIG 11 TERM 11 JUNCTOR ORIG0 TERM0
EES_DATA:
NONE
QUEU NONE
CALL ID 0 566

COS_ORIG CTD COS_TER UNR
TGAR_ORIG 1 TGAR_TER 0
NCOS_ORIG 0 NCOS_TER 0
EXP_ROUTE NO

---- ISDN ISL CALL (ORIG) ----
CALL REF # = 385
BEARER CAP = VOICE
HLC =
CALL STATE = 9 INCOMING
CALLING NO = 6888 NUM_PLAN:UNKNOWN TON:UNKNOWN ESN:UNKNOWN
CALLED NO = 10090115073003200 NUM_PLAN:UNKNOWN TON:UNKNOWN ESN:UNKNOWN

---- ISDN ISL CALL (TERM) ----
CALL REF # = 17882
BEARER CAP = VOICE
HLC =
CALL STATE = 3 OUTGOING
CALLING NO = 6888 NUM_PLAN:UNKNOWN TON:UNKNOWN ESN:UNKNOWN
CALLED NO = 5073003200 NUM_PLAN:E164 TON:NATIONAL ESN:NPA
PDCA 1 PAD 0 0 PCML MU MU

 

[allenmac]

Here's what my trace looks like:

.trac 104 1 5 1

ACTIVE VTN 104 1 05 01

ORIG VTN 104 1 05 01 IPTI RMBR 51 2 INCOMING VOIP GW CALL
FAR-END SIP SIGNALLING IP: 172.xxx.yyy.zzz
FAR-END MEDIA ENDPOINT IP: 172.xxx.yyy.zzz PORT: 6012
FAR-END VendorID: Audiocodes-Sip-Gateway-MP-112 FXS/v.5.60A.020.006
TERM TN 049 01 IPMG 000 1 V PHYSICAL TN 000 1 00 08 DID RMBR 2 93 OUTGOING TRUNK CALL
VGW TN 000 1 00 08
MEDIA ENDPOINT IP: 172.xxx.yyy.zzz PORT: 5216
MEDIA PROFILE: CODEC T.38 NO-LAW PAYLOAD 1 ms VAD OFF
RFC2833: RXPT 101 TXPT N/A DIAL DN 9011442074913201
MAIN_PM ESTD
TALKSLOT ORIG 93 TERM 2 JUNCTOR ORIG0 TERM0
EES_DATA:
NONE
QUEU NONE
CALL ID 01 9278


---- ISDN ISL CALL (ORIG) ----
CALL REF # = 486
BEARER CAP = VOICE
HLC =
CALL STATE = 10 ACTIVE
CALLING NO = 1NPANXXXXXX NUM_PLAN:E164 TON:INTERNATIONAL ESN:UNKNOWN
CALLED NO = 103442074913201 NUM_PLAN:E164 TON:INTERNATIONAL ESN:UNKNOWN (<----- '103' is the TCOS for this call)
---- ISDN ISL CALL (TERM) ----
CALL REF # = 661
BEARER CAP = VOICE
HLC =
CALL STATE = 10 ACTIVE
CALLING NO = 1NPANXXXXXX NUM_PLAN:E164 TON:INTERNATIONAL ESN:UNKNOWN
CALLED NO = 442074913201 NUM_PLAN:E164 TON:INTERNATIONAL ESN:UNKNOWN
PDCA 1 PAD 0 0 PCML MU MU

SIP signaling can be very fickle, and there are a lot of settings in the PBX, NRS and AudioCodes that will affect the success (or failure) of your call routing.

 

[AELMAN]

how do you get 1NPANXXXXXX to show in you calling number field
what did you program in you PBX. i found out that i needed to up the Ncos to get international calls to work

 

[allenmac]

I have found that having the call types marked correctly is important when integrating 3rd party devices and also when networking multiple pbx systems.

Here are the main parts of the configuration.

In the Customer Data Block in your NET data:

CNTC 1 (1 should be used in North America).
NATC 1 (This is your National Dialing Prefix. Again 1 for North America).
INTC 011 (This is your international dialing prefix).

In the CLID programming make sure you have the proper value assigned to the INTL prompt. (I use 1 because I am in North America).

Also make sure that your CLID table entries are built correctly.

Here is a sample CLID table entry from my main site:

ENTRY 0
HNTN 301
ESA_HLCL 272
ESA_INHN YES
ESA_APDN YES
HLCL 272
DIDN YES
DIDN_LEN 0
HLOC 01
LSC
CLASS_FMT DN

One of my DID ranges is NPA-301, NXX-272. I also use LOC codes for on-net dialing between my sites, and this site is UDP LOC 01.

IN LD 90 under AC1 ('9' For my enterprise), I have entries for every NPA. We have entries using 1+NPA for anything that is long distance and entries using just the NPA for calls in our local calling area. We use 10 digit dialing so I don't have any NXX entries. I include the Toll-Free NPA's and do not program them as SPNs (Programming the Toll-Free NPA's as SPNs can cause problems in this environment). Here are a couple of examples of entries from my LD 90 AC1 tables:

NPA 1800
RLI 1
DENY 976

SDRR DENY CODES = 1
ITEI NONE


NPA 1801
RLI 1
DENY 976

SDRR DENY CODES = 1
ITEI NONE

NPA 703
RLI 0
DENY 976

SDRR DENY CODES = 1
ITEI NONE

Note: RLI 0 is for local calling, RLI 1 is for National calling.

In LD 86 in my RLB's I don't do any special digit manipulation if the call is going out of the PBX to the PSTN. If the call is going out over my virtual trunks, then I use a DMI to reformat the digits and mark the call with the correct call type.

DMI 1
DEL 1
ISPN NO
CTYP NCHG

DMI 1 is used on RLB 1 to strip the leading 1. The call is already marked as NATL at this point by the PBX, so I don't need to change the call type.

DMI 11
DEL 3
ISPN NO
CTYP INTL

DMI 11 is used in my RLB 11 for international calls. If all of my local trunks are busy, I route the call over my virtual trunks to another pbx in the network, and then out to the PSTN. In this case, I strip off the leading '011' and mark the call as international. This will leave the call in E.164 Format. I do have switches in Europe, so if the call exits to the PSTN from a European location the correct access code and international prefix are appended by the destination pbx.

In The AudioCodes gateways, my dialing translation looks like this:

In Protocol Configuration -> Manipulation Tables -> Dest Number Tel->IP:

For International calls
Destination Prefix: 9011*
Source Prefix: *
Stripped Digits Number: 4
Prefix (Suffix) to Add: + (This formats the call as E.164)
Number of Digits to Leave: (Left Blank)

For National Long Distance (1+NPA+NXX+XXXX) calls
Destination Prefix: 91[2-9]*
Source Prefix: *
Stripped Digits Number: 2
Prefix (Suffix) to Add: +1 (This formats the call as E.164 with '1' as the Country Code)
Number of Digits to Leave: (Left Blank)

For Local 10-digit dialing (NPA+NXX+XXXX) calls
Destination Prefix: 9[2-9]*
Source Prefix: *
Stripped Digits Number: 1
Prefix (Suffix) to Add: +1 (This formats the call as E.164 with '1' as the Country Code)
Number of Digits to Leave: (Left Blank)

In Protocol Configuration -> Manipulation Tables -> Source Number Tel->IP:

For International Calls:
Destination Prefix: 9011*
Source Prefix: [5100-5199] (This varies depending on the DN originating the call on the AudioCodes.)
Stripped Digits Number: 0
Prefix (Suffix) to Add: +1301555 (This formats the call as E.164 with '1' as the Country Code. The outbound CLID would be +13015555100 - +13015555199)
Number of Digits to Leave: (Left Blank)
Presentation: Allowed

For national calls:
Destination Prefix: 91xxxxxxxxxx#
Source Prefix: [5100-5199] (This varies depending on the DN originating the call on the AudioCodes.)
Stripped Digits Number: 0
Prefix (Suffix) to Add: +1301555 (This formats the call as E.164 with '1' as the Country Code. The outbound CLID would be +13015555100 - +13015555199)
Number of Digits to Leave: (Left Blank)
Presentation: Allowed

For local 10-digit calls (NPA+NXX+XXXX):
Destination Prefix: 9xxxxxxxxxx#
Source Prefix: [5100-5199] (This varies depending on the DN originating the call on the AudioCodes.)
Stripped Digits Number: 0
Prefix (Suffix) to Add: +301555 (This formats the call as E.164 . The outbound CLID would be +3015555100 - +3015555199)
Number of Digits to Leave: (Left Blank)
Presentation: Allowed

In the NRS:

On your AudioCodes endpoint make sure you fill out the E.164 country code (mine is 1), and the E.164 area code (mine is 301). I also enter my pbx AC1 in the following fields: E.164 international dialing access code, E.164 national dialing access code and E.164 local (subscriber) dialing access code.

In the Routes section of the NRS make sure you have routes built for E.164 international calls and also E.164 national calls. These can be default routes, or you can have multiple routes with Route Cost values that will determine the order of preference for various endpoints. I use both. I have default routes for both call types and I also have Routing Entries with different country codes in the DN Prefix to route calls to specific endpoints in Europe. For E.164 national I also have routes with different NPA's in the DN prefix to route calls to specific PBXs in a given NPA.

Finally, use caution when implementing these types of changes. If everything is not correct, you may end up breaking your outbound call routing to the point where outbound calling fails. Take care also with marking your calls using DMIs in LD 86, as not all carriers play nice with explicit call type tags.

 

[AELMAN]

Your the man, we got it working great now.. thanks for all the help..

 

[allenmac]

Glad to hear it!