From: Scott Morris (swm@emanon.com)
Date: Sat Dec 27 2003 - 02:45:46 GMT-3
You gotta specify "direct-inward-dial" as part of your pots dial-peer at
that point, otherwise as far as the router is concerned, all bets are
off.....
Scott
-----Original Message-----
From: Keyur Shah [mailto:kshah@hellocomputers.com]
Sent: Saturday, December 27, 2003 12:39 AM
To: 'swm@emanon.com'; Keyur Shah; 'Pun, Alec CL'; ccielab@groupstudy.com
Subject: RE: num-exp example
I have been using DID as stated in my first example.
-keyur shah-
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Friday, December 26, 2003 9:33 PM
To: 'Keyur Shah'; 'Pun, Alec CL'; ccielab@groupstudy.com
Subject: RE: num-exp example
Well, magically then, the IOS I have been using seems to have a
different set of logic associated with it. Based on debugs and show
dialplan commands, no matter what happens, the num-exp command will
ALWAYS be used BEFORE dial-peer matching. The only alternative to this
is when you are matching DID patterns which "forces" a jump in logic.
In either of the cases you listed below, try doing "show dialplan number
2123" and see what happens.
BRI-VoIP#sh dialplan number 2123
Macro Exp.: 5552123
No match, result=-2
Bummer about that. Nobody gets dialed.
And as a side note, we'll also have to assume those are FXS ports,
because otherwise you'd be sending no numbers out either (gotta do the
"forward-digits" thing!)...
In case it makes any difference, I'm running 12.2(2)T1
Scott
-----Original Message-----
From: Keyur Shah [mailto:kshah@hellocomputers.com]
Sent: Friday, December 26, 2003 9:46 PM
To: 'swm@emanon.com'; Keyur Shah; 'Pun, Alec CL'; ccielab@groupstudy.com
Subject: RE: num-exp example
Thanks Scott.
So are you agreeing to Alec's comment about destination peer should be
expanded number? Are you saying that, if router receives digits 2123, it
will first manipulates digits with num-exp and then match inbound
dial-peer?
Going back to two scenarios that Alec had mentioned from this page,
http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps1835/products
_configuration_guide_chapter09186a0080080aec.html#1244664
---case 1---
num-exp 2... 5552...
dial peer voice 1 pots
destination pattern 2123
In this case dialed digits are 2123 which will match dial peer 1 and
then expanded to 5552123 and sent out through outbound dial peer
matching 5552123 destination pattern.
---case 2---
num-exp 2123 5556611
dial peer voice 1 pots
destination pattern 2123
Quote from that example
"In this example, every time the device receives a call for extension
2123, the dialed digits will be replaced with 555-6611 and the call will
be forwarded to that telephone."
In this case when an inbound call is received for 2123, it will match
dial peer 1 first and then do the digit manipulation and convert it to
5556611 and then look for outbound dial peer to route it to voip/pots
dial peer matching expanded number 5556611.
Let me know if you think any other way. I have done debug dialpeer on
these scenarios many times.
-Keyur Shah-
QUAD CCIE# 4799 (Voice; Service Provider; Security; R/S)
CCSI, CISSP, Check Point CCSE Plus, MCSE
http://www.hellocomputers.com
"Say Hello To Your Future!"
1.877.79.HELLO
Hall of Fame@
http://www.hellocomputers.com/hellofame.html
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Friday, December 26, 2003 3:52 PM
To: 'Keyur Shah'; 'Pun, Alec CL'; ccielab@groupstudy.com
Subject: RE: num-exp example
Keyur,
Congrats on passing your Voice IE.... Welcome to the world of four. :)
However, I'm going to have to make you look back at your posting
here.... The destination pattern in a dial peer matches your EXPANDED
(eg. POST num-exp) number. So when a phone dials digits, or digits come
in, the num-exp happens first in terms of pattern matching. Then the
destination patterns in order to pass the number someplace else will
occur.
If you wish to manipulate your digits on the way to your Call Manager
(or other peer) after matching a dial peer's destination-pattern, you
will need to use the translation rules.
Take a look at the output from your debug commands and watch which part
gets matched on the way out, and you will find it is the
destination-pattern only after num-exp has taken place... The same thing
will be shown by using the 'show dialplan number (#)' where it first
lists the "Macro Exp" for your new expanded number, and then the dial
peers that are matched.
In the example that you gave, you did follow that same logic (dest
pattern 2... Is the POST translated address from num-exp command). Most
likely too much eggnog!
Otherwise, congrats! :)
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP, JNCIS, et al. IPExpert CCIE Program Manager IPExpert Sr.
Technical Instructor swm@emanon.com/smorris@ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Keyur Shah
Sent: Friday, December 26, 2003 5:49 PM
To: 'Pun, Alec CL'; ccielab@groupstudy.com
Subject: RE: num-exp example
Alec,
Num-exp digit manipulation takes place after matching dial peer.
Therefore dial peer must match first for inbound call leg and then
num-exp digit manipulation will take place. In first example dialed
digits are 2123, whereas in 2nd example received digits are 2123.
Say for example PSTN is sending you 10 digits and your incoming
dial-peer is configured with incoming called-number . It will match that
dial peer and let's say your voip dial peer is configured for session
target to CM with 2... Destination pattern, then you will need to use
num-exp 4084962... 2... ! Dial-peer voice 100 voip destination-pattern
2... Session target ipv4:CM_IP_Address !
-Keyur Shah-
QUAD CCIE# 4799 (Voice; Service Provider; Security; R/S)
CCSI, CISSP, Check Point CCSE Plus, MCSE http://www.hellocomputers.com
"Say Hello To Your Future!" 1.877.79.HELLO Hall of Fame@
http://www.hellocomputers.com/hellofame.html
-----Original Message-----
From: Pun, Alec CL [mailto:Alec.CL.Pun@pccw.com]
Sent: Thursday, December 25, 2003 2:57 AM
To: ccielab@groupstudy.com
Subject: num-exp example
Hi group,
The following examples are copied from Voice configuration guide. Isn't
that the destination pattern should be the expanded number ?
thanks
alec
Using a simple telephony-based example, suppose that John works in a
company where employees extensions are reached by dialing the last four
digits of the full E.164 telephone number. The E.164 telephone number is
555-2123; John's extension number is 2123. Suppose that every employee
on John's floor has a telephone number that begins with the same first
four digits: 5552. You could define each dial peer's destination pattern
using each extension number, and then use number expansion to prepend
the first four digits onto the extension. In this example, the router
could be configured as follows:
num-exp 2... 5552...
dial peer voice 1 pots
destination pattern 2123
Number expansion can also be used to replace a dialed number with
another number, as in the case of call forwarding. Suppose that for some
reason, John needs to have all of his telephone calls forwarded to
another number, 555-6611. In this example, you would configure the
router as follows:
num-exp 2123 5556611
dial peer voice 1 pots
destination pattern 2123
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:45 GMT-3