cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Walkthrough Wednesdays
2969
Views
0
Helpful
4
Replies
sarahr202
Contributor

dial peers on cme for registered ipphones.

Hi everybody.

Please consider the following set up.

( extension 1001) Ipphone1---------SW-------CME(router)--------SW-----Ipphone2( Extention: 1002      

Both ipphones have successfully registered with the CME above. Both can make calls to each other.

Do we need to configure dial peers or do we need dial peers on CME for these ipphones ?

This is my understanding;

After IPphones registered with CME, CME has the all the pertinent information specially extensions and their corresponding ip addresses. for e.g

CME knows extension 1001--------201.201.201.1 ( the ip address of ipphone1)

                                 1002 ------201.201.201.2( the ip address of ipphone2)

Now if we have these two ip phones in different regions , we still should not need dial peers. for example:

(newyork)(IPphone1)-----sw-----CME---Router---Wan-----Router----SW----Ipphone2(london)

As long as ipphones are able to register successfully with CME, CME will know how to reach them for setting up the calls between them without diial  peers.

I just want to confirm my understanding.

thanks and have a great day.    

3 ACCEPTED SOLUTIONS

Accepted Solutions
Harmit Singh
Cisco Employee

Hi Sarah,

Once IP Phones (Ephones) register to the CME, depending on your ephone configuration, the ephone-dn(s) get mapped to the buttons on that phone. These ephone-dn(s) are nothing but virtual dial-peers. You can see these with the help of the following commands:

show telephony-service ephone-dn

show telephony-service dial-peer

show dial-peer voice summary

That is why you dont need any additional config like dial-peer configs to have one ip phone call another within the same CME system.

HTH.

Regards,

Harmit.

View solution in original post

Hi Sarah,

An ephone-dn is very similar to how you configure / map a number to an FXS port. For FXS ports, you're really just creating a pots dialpeer and mapping it to the port. Similarly,an ephone-dn has two components:

A virtual POTS dial peer for directing calls to the phone

A virtual voice port

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/dialplan.html#wp1075395

HTH.

Regards,

Harmit.

View solution in original post

The virtual dial-peers created in CCME when you configure an ephone-dn is a POTS dial-peer...

An ephone-dn has two components:

•A virtual POTS dial peer for directing calls to the phone


•A virtual voice port


--------------------------------------------------------------------------------


Note The voice ports and dial peers automatically generated by ephone-dns do not appear on the Cisco Unified CME running configuration. They can be seen only using more specific show commands.


--------------------------------------------------------------------------------


The following example shows the definition on an ephone-dn and its associated POTS dial peer and
voice port.


router# show running-config


ephone-dn 1

number 3001

description User1

name User1

call-forward busy 3105

call-forward noan 3105 timeout 10

!

router# show telephony-service dial-peer


dial-peer voice 20001 pots

destination-pattern 3001

huntstop

call-forward busy 3105

call-forward noan 3105

!

router# show telephony-service voice-port


voice-port 50/0/1

station-id number 3001

station-id name User1

timeout ringing 10

progress_ind setup enable 3

port 50/0/1

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

Please rate all useful posts

View solution in original post

4 REPLIES 4
Harmit Singh
Cisco Employee

Hi Sarah,

Once IP Phones (Ephones) register to the CME, depending on your ephone configuration, the ephone-dn(s) get mapped to the buttons on that phone. These ephone-dn(s) are nothing but virtual dial-peers. You can see these with the help of the following commands:

show telephony-service ephone-dn

show telephony-service dial-peer

show dial-peer voice summary

That is why you dont need any additional config like dial-peer configs to have one ip phone call another within the same CME system.

HTH.

Regards,

Harmit.

View solution in original post

Thanks Harmit.

ipphone1 ( 20001)--------sw-------CME----Sw----ipphone2(20002)

above both ip phones are successfully registered with CME. I can see dial peers when I used " show dial-peer voice summmary" as you suggested. But I also see the type as " pots" even though both ipphones are cisco 7940.

(see below)

would you please explain that?

Router#show dial-peer voice summary

dial-peer hunt 0

             AD                                    PRE PASS                OUT

TAG    TYPE  MIN  OPER PREFIX    DEST-PATTERN      FER THRU SESS-TARGET    STAT

PORT

20001  pots  up   up             20001$             0

50/0/1

20002 pots  up   up             20002$             0

Thanks

Hi Sarah,

An ephone-dn is very similar to how you configure / map a number to an FXS port. For FXS ports, you're really just creating a pots dialpeer and mapping it to the port. Similarly,an ephone-dn has two components:

A virtual POTS dial peer for directing calls to the phone

A virtual voice port

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/dialplan.html#wp1075395

HTH.

Regards,

Harmit.

View solution in original post

The virtual dial-peers created in CCME when you configure an ephone-dn is a POTS dial-peer...

An ephone-dn has two components:

•A virtual POTS dial peer for directing calls to the phone


•A virtual voice port


--------------------------------------------------------------------------------


Note The voice ports and dial peers automatically generated by ephone-dns do not appear on the Cisco Unified CME running configuration. They can be seen only using more specific show commands.


--------------------------------------------------------------------------------


The following example shows the definition on an ephone-dn and its associated POTS dial peer and
voice port.


router# show running-config


ephone-dn 1

number 3001

description User1

name User1

call-forward busy 3105

call-forward noan 3105 timeout 10

!

router# show telephony-service dial-peer


dial-peer voice 20001 pots

destination-pattern 3001

huntstop

call-forward busy 3105

call-forward noan 3105

!

router# show telephony-service voice-port


voice-port 50/0/1

station-id number 3001

station-id name User1

timeout ringing 10

progress_ind setup enable 3

port 50/0/1

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

Please rate all useful posts

View solution in original post

Content for Community-Ad

Spotlight Awards 2021