Help ? How (CME1)phone can make external call throught (CME2) Fxo Card

[DJAHIDCISCO]

Hello everyone

 I have two CME sites connected to each other

CME1 ( Ext 1001,Ext 1002 ) communicates with CME2 (Ext 3001 Ext 3002) successfully 

(Ext 3001 3002)  on CME 2 make external PSTN calls through port 0/0/1 successfully

My first scenario is what are the commands that I must put so that ext 1001, 1002 can make external pstn calls through ports 0/0/1 of cme 2

please Refer to the diagram attached

[Roger Kallberg]

In CME1 create a dial peer that points the dial pattern for external calls to CME2. As you already have communication between these and can send internal calls between the two it should not be all that much to it. In CME2 make sure that calls coming from CME1 are matching a suitable inbound dial peer and also the intended outbound dial peer to send calls out the FXO port.

For detailed information on how call routing and dial peers operate please have a look at this excellent document. In Depth Explanation of Cisco IOS and IOS-XE Call Routing 

If you need specific configuration assistance please post your current configuration from both routes as attached text files so that we can suggest the needed changes specifically for your configuration.

[DJAHIDCISCO]

can you show me an exmple of command for CME1 and CME2 ?

CME1 ( ext: 200 ext: 100)

CME2 (ext: 300 ext 400 )

All ext communicate on internal

Ext 300 / 400 make external PSTN calls through port 0/0/1 successfully

the cme1 & cme2 config are attached to this message

[Roger Kallberg]

I would suggestion these changes, at least if you have a reasonable recent version of IOS. If you have an older variant some of these would not work, but then you can use the legacy configuration as outlined in the document that I shared earlier.

**CME 1**
voice service voip
 no allow-connections h323 to h323
 no allow-connections h323 to sip
 no allow-connections sip to h323
!
voice class e164-pattern-map 1
 description E164 Pattern Map for calls to CME 2
 e164 [34]..$
 e164 9T
!
voice class uri CME2 sip
 host ipv4:192.168.100.2
!
dial-peer voice 400 voip
 description Outgoing dial peer to CME 2
 no destination-pattern 4..
 destination calling e164-pattern-map 1
 session protocol sipv2
 session target ipv4:192.168.100.2
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad
!
no dial-peer voice 300 voip
!
dial-peer voice 1 voip
 description Incoming dial peer from CME 2
 session protocol sipv2
 incoming uri from CME2
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad


**CME 2**
voice class e164-pattern-map 1
 description E164 Pattern Map for calls to CME 1
 e164 [12]..$
!
voice class uri CME1 sip
 host ipv4:192.168.100.1
!
dial-peer voice 100 voip
 description Outgoing dial peer to CME 1
 no destination-pattern 1..
 destination calling e164-pattern-map 1
 session protocol sipv2
 session target ipv4:192.168.100.1
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad
!
no dial-peer voice 200 voip
!
dial-peer voice 1 voip
 description Incoming dial peer from CME 1
 session protocol sipv2
 incoming uri from CME1
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad

[Roger Kallberg]

How did it go with this, where you able to get it working with the suggested configuration?

[DJAHIDCISCO]

good evening

I have just started the configuration that you proposed to me but unfortunately the version of the ios is old and the configuration is not supported by the router

f I understood correctly I must apply this example to my configuration

Could you help me on the commands of the second method mentionned on the documentation you sent to me

Thank's

[Roger Kallberg · Accepted solution]

What type of router do you use? Maybe it could be upgraded to a version of IOS that has support for the suggested configuration. If you use a ISR4K I’d recommend to use version 17.6.4 as it is stable and not ridiculously riddled with defects.

If you need to use legacy style configuration something along with this should work, mind you that you might need to adopt it to fit with your current configuration.

**CME 1**
voice service voip
 no allow-connections h323 to h323
 no allow-connections h323 to sip
 no allow-connections sip to h323
!
dial-peer voice 400 voip
 description Outgoing dial peer to CME 2 for internal calls
 destination-pattern [34]..$
 session protocol sipv2
 session target ipv4:192.168.100.2
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad
!
no dial-peer voice 300 voip
!
dial-peer voice 300 voip
 description Outgoing dial peer to CME 2 for PSTN calls
 destination-pattern 9T
 session protocol sipv2
 session target ipv4:192.168.100.2
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad
!
dial-peer voice 1 voip
 description Incoming dial peer from CME 2
 session protocol sipv2
 answer-address [34]..
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad


**CME 2**
dial-peer voice 100 voip
 description Outgoing dial peer to CME 1 for internal calls
 destination-pattern [12]..$
 session protocol sipv2
 session target ipv4:192.168.100.1
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad
!
no dial-peer voice 200 voip
!
dial-peer voice 1 voip
 description Incoming dial peer from CME 1
 session protocol sipv2
 answer-address [12]..
 dtmf-relay rtp-nte sip-kpml
 bind control source-interface GigabitEthernet0/2
 bind media source-interface GigabitEthernet0/2
 no vad

My configuration uses SIP, not H.323 as that is very legacy and not supported much longer.

[DJAHIDCISCO]

yes i prefer to use legacy style configuration since i am doing simulations at home

i think  this exemple look like the configuration i want to run is not it ???!!

execpt i replace

(dial-peer Voice 1 pots) by( Dial-peer Voice 1 Voip)     (CME1)

 Dial-peer voice 1 voip

 destinitaion-pattner 9T

 session target ipv4:192.168.100.2

because i have an ip phone not analog phone

[Roger Kallberg]

Did you look at what I suggested for legacy configuration? In my suggestion dial-peer 1 is used in the inbound direction on both CME and dial-peer 300 and 400 are used outbound from CME 1 and 100 is used outbound to CME 1 on CME 2. Your current outbound dial-peer to PSTN on CME 2 is untouched and should once you get the call to route from CME 1 to CME 2 and match the intended inbound dial-peer use your current outbound pots (PSTN) dial-peer.

I'm not sure where you found that picture and example, but it is quite poorly written. You do not put a port on an inbound dial-peer as that is used in the outbound direction. It is much better and clearer IMHO to split inbound and outbound directions into separate dial-peers as that makes it much easier to troubleshoot and see the direction of calls with show commands.

[DJAHIDCISCO]

okey finally i understand this suggestion

I have another question

if I want to allow telephone 100 to make external calls and the phone 200 nowhat do I do ?

[Roger Kallberg · Accepted solution]

You can do that with Class of Restriction (COR). I won't make a detailed suggestion on that as that is noting that I'd normally use. Please read this document and I'm sure that you with a little will and effort on your side can get it setup as you want it.
Configuring Class of Restrictions (COR)