cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
987
Views
0
Helpful
3
Replies

POTS dial-peer testing question

ricardo1831
Level 1
Level 1

Hi all,

Does a POTS dial-peer require the E1 interface to be up and and connected in order to be selected when testing?

The problem I'm having is the POTS dial peer is not being matched even though the Called number clearly matches dial-peer 200. Instead it defaults to dial-peer 202 which is the outbound. As mentioned the E1/voice port interface is not currently up and connected. See attached show dial-peer voice summary.

Suggestions appreciated before I try this in live environment.

Called Number: 51007035

dc1rtr01#sh run | s dial-peer
dial-peer voice 200 pots
 description Calls from PSTN to Deep cygnus PBX
 destination-pattern 5100703[5-9]
translate-outgoing called 7000

 incoming called-number .
 direct-inward-dial
 port 0/0/0:15
 forward-digits 0
dial-peer voice 201 pots
 description Calls from PSTN to Deep Cygnus PBX
 destination-pattern 5100704[0-4]
 translate-outgoing called 7000
 incoming called-number .
 direct-inward-dial
 port 0/0/0:15
 forward-digits 10
dial-peer voice 202 voip
 description Calls from Deep cygnus PBX to PSTN (via HCC)
 destination-pattern .T
 translate-outgoing calling 5000
 translate-outgoing called 4000
 session target ipv4:10.0.75.204
 dtmf-relay cisco-rtp h245-alphanumeric
 fax rate 9600
 no vad
dc1rtr01#

 

Thanks,

Ric

 

 

1 Accepted Solution

Accepted Solutions

I would say because the E1 is not up it hunts thru the dial-peers to get one that is working I am sure if you take away the VOIP dial peer you will get a busy tone or something.

 

What you can do is to play around with the "dial-peer hunt" command.

UC520(config)#dial-peer hunt ?
  <0-7>  Dial-peer hunting choices, listed in hunting order within each choice:
  0 - Longest match in phone number, explicit preference, random selection.
  1 - Longest match in phone number, explicit preference, least recent use.
  2 - Explicit preference, longest match in phone number, random selection.
  3 - Explicit preference, longest match in phone number, least recent use.
  4 - Least recent use, longest match in phone number, explicit preference.
  5 - Least recent use, explicit preference, longest match in phone number.
  6 - Random selection.
  7 - Least recent use.

 

 

Best Regards

View solution in original post

3 Replies 3

I would say because the E1 is not up it hunts thru the dial-peers to get one that is working I am sure if you take away the VOIP dial peer you will get a busy tone or something.

 

What you can do is to play around with the "dial-peer hunt" command.

UC520(config)#dial-peer hunt ?
  <0-7>  Dial-peer hunting choices, listed in hunting order within each choice:
  0 - Longest match in phone number, explicit preference, random selection.
  1 - Longest match in phone number, explicit preference, least recent use.
  2 - Explicit preference, longest match in phone number, random selection.
  3 - Explicit preference, longest match in phone number, least recent use.
  4 - Least recent use, longest match in phone number, explicit preference.
  5 - Least recent use, explicit preference, longest match in phone number.
  6 - Random selection.
  7 - Least recent use.

 

 

Best Regards

sirkalliemarie,

Thanks for your response. Just to conclude this thread I can confirm the solution worked when implemented in production environment. 

Hm,

even though closed, one of 2 destpatterns in POTS peers was not a typo? I see a last digit in 2 ranges 0-4 and 5-9, however digit before them is 3 or 4 in POTS peers. Normally it should a single same number.. anyway, everyone inc me is happy here it works for you in live operation :-)

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: