US CME to UK CME

Unanswered Question
Oct 1st, 2008

I inherited a CME in London and just installed one here in the US. I have extension to extension call working, now I am trying to configure the US CME to be able to make regular calls through the London CME via our VPN. I am looking for an example config to do this.


Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Brandon Buffin Wed, 10/01/2008 - 11:02

I'm not sure the dial plan structure is correct, but this should get you started.


US CME

dial-peer voice 1 voip

destination-pattern 90114420........

session target ivp4:2.2.2.2 (UK CME)

codec g711ulaw


UK CME

dial-peer voice 1 voip

incoming called-number 90114420........

codec g711ulaw


dial-peer voice 2 pots

destination-pattern 90114420........

forward-digits 10

port 1/0:23


There are other ways to do this and other options such as using g.729 across the WAN to conserve bandwidth.


Hope this helps.


Brandon

wplantier Wed, 10/01/2008 - 11:11

Thanks now I get a fast busy but I will troubleshoot it from here.


Brandon Buffin Wed, 10/01/2008 - 11:13

Make sure you have the following command in the UK CME.


voice service voip

allow-connections h323 to h323


Brandon

wplantier Wed, 10/01/2008 - 11:18

I broke something because my 3 digit dialing broke.



US


dial-peer voice 10 voip

destination-pattern 4..

session target ipv4:172.23.120.1

codec g711alaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 20 voip

destination-pattern 2...

session target ipv4:172.23.20.2

dtmf-relay h245-alphanumeric

codec g711ulaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 100 voip

description International excpet country code 1

destination-pattern 00[2-9]......T

!

dial-peer voice 1 voip

destination-pattern 90114420........

session target ipv4:172.23.120.1

codec g711ulaw

!


UK

voice service voip

allow-connections h323 to h323

!

!

!

!

!

!

!

!

!

!

voice translation-rule 1

rule 1 /\(.*\)/ /90\1/ type national national

rule 2 /\(.*\)/ /900\1/ type international international

!

!

voice translation-profile incoming_digits

translate calling 1


dial-peer voice 1 pots

description ** E1 Outgoing Dial Peer **

destination-pattern 9T

port 0/0/0:15

!

dial-peer voice 2 pots

description ** E1 Incomming Dial Peer **

translation-profile incoming icoming_digits

incoming called-number 323...

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 8000 voip

description ** CUE Voicemail Pilot Number **

destination-pattern 8000

session protocol sipv2

session target ipv4:172.23.120.10

dtmf-relay sip-notify

codec g711ulaw

no vad

!

dial-peer voice 10 voip

destination-pattern 2...

session target ipv4:172.23.20.2

codec g711alaw

ip qos dscp cs5 media

!

dial-peer voice 50 voip

incoming called-number 90114420........

codec g711ulaw

!

dial-peer voice 3 pots

destination-pattern 90114420........

port 0/0/0:15

forward-digits 10

!



Brandon Buffin Wed, 10/01/2008 - 12:05

If you turn on "debug voip dialpeer" on both gateways, do you see the call hit the correct dial peers?


Brandon

wplantier Wed, 10/01/2008 - 12:10



us side


Oct 1 16:01:07.598: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Calling Number=2448, Called Number=, Voice-Interface=0x486813EC,

Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

Oct 1 16:01:07.598: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20001

Oct 1 16:01:09.454: //-1/FE110B378101/DPM/dpMatchPeersCore:

Calling Number=, Called Number=4, Peer Info Type=DIALPEER_INFO_SPEECH

Oct 1 16:01:09.454: //-1/FE110B378101/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=4

Oct 1 16:01:09.454: //-1/FE110B378101/DPM/dpMatchPeersCore:

Result=Partial Matches(1) after DP_MATCH_DEST

Oct 1 16:01:09.454: //-1/FE110B378101/DPM/dpMatchPeersMoreArg:

Result=MORE_DIGITS_NEEDED(1)

Oct 1 16:01:09.650: //-1/FE110B378101/DPM/dpMatchPeersCore:

Calling Number=, Called Number=44, Peer Info Type=DIALPEER_INFO_SPEECH

Oct 1 16:01:09.650: //-1/FE110B378101/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=44

Oct 1 16:01:09.650: //-1/FE110B378101/DPM/dpMatchPeersCore:

Result=Partial Matches(1) after DP_MATCH_DEST

Oct 1 16:01:09.650: //-1/FE110B378101/DPM/dpMatchPeersMoreArg:

Result=MORE_DIGITS_NEEDED(1)

Oct 1 16:01:09.850: //-1/FE110B378101/DPM/dpMatchPeersCore:

Calling Number=, Called Number=442, Peer Info Type=DIALPEER_INFO_SPEECH

Oct 1 16:01:09.850: //-1/FE110B378101/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=442

Oct 1 16:01:09.850: //-1/FE110B378101/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

Oct 1 16:01:09.850: //-1/FE110B378101/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=10

Oct 1 16:01:09.854: //-1/FE110B378101/DPM/dpMatchPeersCore:

Calling Number=, Called Number=442, Peer Info Type=DIALPEER_INFO_SPEECH

Oct 1 16:01:09.854: //-1/FE110B378101/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=442

Oct 1 16:01:09.854: //-1/FE110B378101/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DE


nothing on the UK side

Brandon Buffin Wed, 10/01/2008 - 12:13

You have "term mon" on on the UK side, right? Can you ping 172.23.120.1 from the US CME. If you're not seeing anything on the UK side, the call is never reaching that box. Sounds like an IP address/IP connectivity problem.


Brandon

Brandon Buffin Wed, 10/01/2008 - 12:29

3-digit dialing worked before entering the TEHO config? If so, take this config out and see if it starts working again.


Brandon

Brandon Buffin Thu, 10/02/2008 - 05:42

Looks like the London debug show a 9011442........ call hitting dial peer 10. Did you renumber your dial peers? Can you post the config for the router?


Brandon

wplantier Thu, 10/02/2008 - 05:49

Raleigh


dial-peer voice 10 voip

destination-pattern 4..

session target ipv4:172.23.120.1

codec g711alaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 20 voip

destination-pattern 2...

session target ipv4:172.23.20.2

dtmf-relay h245-alphanumeric

codec g711ulaw

ip qos dscp cs5 media

no vad

!

dial-peer voice 1 voip

destination-pattern 90114420........

session target ipv4:172.23.120.1

codec g711alaw

!


London


dial-peer voice 1 pots

description ** E1 Outgoing Dial Peer **

destination-pattern 9T

port 0/0/0:15

!

dial-peer voice 2 pots

description ** E1 Incomming Dial Peer **

translation-profile incoming icoming_digits

incoming called-number 323...

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 8000 voip

description ** CUE Voicemail Pilot Number **

destination-pattern 8000

session protocol sipv2

session target ipv4:172.23.120.10

dtmf-relay sip-notify

codec g711ulaw

no vad

!

dial-peer voice 10 voip

destination-pattern 2...

session target ipv4:172.23.20.2

codec g711alaw

ip qos dscp cs5 media

!

dial-peer voice 50 voip

destination-pattern 90114420........

incoming called-number 90114420........

codec g711ulaw

!

dial-peer voice 4 pots

destination-pattern 90114420........

port 0/0/0:15

forward-digits 10


Brandon Buffin Thu, 10/02/2008 - 06:44

Remove "destination-pattern 90114420........ " from dial peer 50. After doing this, is it possible to dial 90114420........ from the London office?


Brandon

wplantier Thu, 10/02/2008 - 13:01

So apparently I need to translate 2883 to my london main number of 02078323440 because the London telco doesnt recognize the 4 digit number.

glenn.white Fri, 10/03/2008 - 02:49

Hi, don't know if your translation worked or not but one of the ways around this is on the UK end create a voice translation profile that 'translates' your calling US extension to have type and plan unknown.

In the following example assume that the US extensions are in the 1... range:


voice translation-rule 4

rule 1 /1.../ // type any unknown plan unknown unknown


voice translation-profile OUTBOUND

translate calling 4


dial-peer voice $$$ pots

translation-profile outgoing OUTBOUND


This has worked for me in the past when US callers are using TEHO through the UK.


Hope it helps.

iptuser55 Fri, 10/03/2008 - 05:39

If I`m right from the US you send all the digits to the UK and then the UK translates it?


It seems you have a UK translation which is any number with a type internatuional add prefix 900, or national add 90 so you end up with a number of 900901144..... or 9090...... ???????????????


Also the Dial-peer


dial-peer voice 3 pots

destination-pattern 90114420........

port 0/0/0:15

forward-digits 10

!


will not work either as you are sending 20XXXXXXXX when you should be sendin a prefix of 0


prefix 0

forward-digits 10


so you now send 020XXXXXXX




Depending on where you wish to do the translations my choice is the sending the switch



voice translation-rule 1

rule 1 /^901144\(*\)/ /90\1/ TYPE UNKNOWN INTERNATIONAL PLAN UNKNOWN NATIONAL ISDN

!

This changes the number from US international to UK with national - normally ok if not change it to unknown as well

!

voice translation-profile US to UK

translated called 1



dial-peer voice 11 voip

translation-profile incoming US to UK

session target IP4V X.X.X.X





Actions

This Discussion