Multiple CME problem

Answered Question
Dec 14th, 2007

hi, i have configured on both of my routers 2 CME with the ollowing address:

CME 1 192.168.1.1

CME 2 192.168.2.1

and i have tried to connect these CME via a dial-peer configurations but it doesn't work ... i have defined an ip routing and i'm able to ping from each FE interface of the routers and i have defined the following dial plan:

dial-peer voice 1 voip

destination-pattern 2...

session target ipv4:192.168.X.1 (address of the remote CME)

codec g711ulaw

and i was unable to place a call between the two routers

you will find an attach one of my router configuration's and by the way i connect them using a WIC-2T cable and DTE/DCE cable thanks for your help i really appreacite it

Kindly Seifddine

no vad

Attachment: 
I have this problem too.
0 votes
Correct Answer by Brandon Buffin about 8 years 12 months ago

On second look, it's only incorrect in one of the configs.

Brandon

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Loading.
Brandon Buffin Fri, 12/14/2007 - 07:43

You will also need incoming dial peers on each side. Such as:

dial-peer voice 5 voip

incoming called-number 2...

Hope this helps.

Brandon

Brandon Buffin Fri, 12/14/2007 - 09:00

If you enter "debug voip dialpeer" on both routers and make the call, do you see the call hit a dial peer on both routers?

Brandon

Seifeddine-Tlili Fri, 12/14/2007 - 09:18

yep when i use the debug cmd i can on both routers some results here r some of them:

from One router i called 3122 and 3... was a destination to the other router

Dec 14 17:16:08.699: //-1/9F002A04804B/DPM/dpAssociateIncomingPeerCore:

Calling Number=100, Called Number=3122, Voice-Interface=0x0,

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

Peer Info Type=DIALPEER_INFO_SPEECH

*Dec 14 17:16:08.699: //-1/9F002A04804B/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=2

*Dec 14 17:16:08.699: //-1/9F002A04804B/DPM/dpAssociateIncomingPeerCore:

Calling Number=100, Called Number=3122, Voice-Interface=0x0,

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

Peer Info Type=DIALPEER_INFO_SPEECH

*Dec 14 17:16:08.699: //-1/9F002A04804B/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=2

Seifeddine-Tlili Fri, 12/14/2007 - 09:28

it was like the router does't strip out the extension 3 and transfer the call to the ephone-dn 122 am i right??

thanks for ur assitance

Brandon Buffin Fri, 12/14/2007 - 09:42

Yes, that is correct. Explicitly matched digits are stripped on POTS dial peers, but not on VOIP dial peers. If you want 3122 to go to extension 122 on the other end you will need a voice translation rule such as:

voice translation-rule 1

rule 1 /^3\(...$\)/ /\1/

voice translation-profile profile1

translate called 1

dial-peer voice 5 voip

incoming called-number 3...

translation-profile incoming profile1

This will translate incoming called numbers that begin with 3 followed by 3 numbers to the last 3 numbers.

Hope this helps. If so, please rate the post.

Brandon

Seifeddine-Tlili Fri, 12/14/2007 - 10:15

thanks for your help Mr Buffin but unfortunatly the translation profile doesn't work and i don't know why even more more i have tried to chek up the translation rule with the cmd test voice translation-rule 1 3100 so it shows up the right translation so i have created a DN with the extension number 3100 on the other side and i ommit the dial-peer voice to set up the incomming called number 3... and it works fine :) but i stoneshed why the translation rule doesn't work

thanks again and if u can provide an answer it would the best welcome kindly

Brandon Buffin Fri, 12/14/2007 - 10:21

If you enable "debug voip dialpeer" on the far end, does the call hit the correct dial peer? The one with the translation profile applied?

Brandon

Seifeddine-Tlili Fri, 12/14/2007 - 10:34

yes it hot the correct dial-peer but the destination don't changed i mean there aren't any digit manipulation or translation effectued ?? it makes confused thanks for looking after my interests i really appreciate your help

kindly

Brandon Buffin Fri, 12/14/2007 - 10:37

Can you attach the config from both routers and the output from the debug?

Brandon

Brandon Buffin Fri, 12/14/2007 - 11:05

Your translation rule should match your incoming called number. So, on the router receiving the call for 3100, you should have:

voice translation-rule 1

rule 1 /^3\(...$\)/ /\1/

!

!

voice translation-profile profile1

translate called 1

dial-peer voice 3 voip

translation-profile incoming profile1

incoming called-number 3...

It looks like your translation rules are reversed in the configs.

Brandon

Correct Answer
Brandon Buffin Fri, 12/14/2007 - 11:07

On second look, it's only incorrect in one of the configs.

Brandon

Seifeddine-Tlili Fri, 12/14/2007 - 12:16

thanks amn what a big mistake, right now i'm at home and i'll be back to the office the next Monday i'll fix it and keep you in touch with the results thanks again

Kindly

Seifeddine-Tlili Mon, 12/17/2007 - 10:47

I have changed the configuration as needed but still got the same proble here r the confs after the modification thanks for your help i really appreciate

kindly Seif

Attachment: 
Brandon Buffin Mon, 12/17/2007 - 11:03

Add "codec g711ulaw" to your incoming dial peers. The default is g.729, so your incoming/outgoing dial peer codecs are currently mismatched.

Brandon

Actions

This Discussion