B-ACD pilot dail-peer question

Hi,

In configuration B-ACD dial-peer, if we have more than one incoming ports, must we make each ports a dail-peer, just as Cisco documents put it:

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

dial-peer voice 1000 pots

 service aa

 incoming called-number 8005550100

 port 1/1/0

 

dial-peer voice 1001 pots

 service aa

 incoming called-number 8005550100

 port 1/1/1

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

I am wondering since the incoming called-number is a same number for each port, why don't we just put it in ONLY one dial-peer? Like this:

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

dial-peer voice 1000 pots

service aa

incoming called-number 8005550100

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

Note that there is no specific "port x/x/x" above. By this all incoming calls with the called number 8005550100 will be handled through service aa no matter which port it comes from, even there are N ports that has incoming calls. Am I right?

Any idea? thanks.

Jordan

Comments

  • Jordan,

    Your configuration will work just fine. You do not have to have the port command to match for an inbound dial peer.
    (you do have to have port for an outbound dial peer to function however)
    Only time you need to have a port specified in a dial peer command is if you have multiple different ports that you want to perform some different inbound call routing function with (not just different DIDs - that you can still do with multiple dial peers with no port statement).

    Also something to note, if you want to trigger BACD for calls originating from either SIP or SCCP phones on a SRST or CUCME, or you want to trigger BACD for calls originating from a H.323 or SIP trunk - you need to have the call originate on an inbound direction (TCL / VXML scripts will NOT trigger on outbound dial peers - only inbound ones). This means that - let's say for example a call coming from a SCCP based ephone - that unless we want EVERY call that comes from that phone to go to BACD (not likely the case), then the inbound dial peer is a POTS dial peer for that ephone/ephone-dn combo, and that we can't place the BACD trigger there, so we need another place to do it. But every call leg ONLY has one inbound and one outbound call leg - so what to do? Well we can send the call out of the router (out the loopback int), thus completing the inbound/outbound requirement, and then since it went to the loopback int, well it Loops Back into the router, and we trigger the BACD there. Works great. 
    So why do I even bring that up since you didn't ask about SCCP/SIP/H.323 calls to BACD?
    Well, simply because you can use one dial peer that will meet every need for sending VoIP calls out of the router, bringing them back in to the router and subsequently triggering BACD, and making sure that every POTS call trying to trigger it will also be able to do so.

    dial-peer voice 5000 voip
     service aa  (triggers AA application on the ingress)
     incoming called-number 8005550100   (matches number for inbound calls from Loopback)
     destination-pattern 8005550100  (matches number for outbound calls)
     session-target ipv4:177.1.254.3  (sends outbound calls to Loopback)
     dtmf-relay h245-signal  (important if you want to be able to press any menu item :))
     no vad
     codec g711ulaw   (important if you want BACD to be able to play any prompts :))


    Then for any POTS inbound needs:

    dial-peer voice 1000 pots
     direct-inward-dial
     incoming called-number .

    HTH!




    On Nov 24, 2009, at 10:05 AM, Jordan wrote:

    Hi,

    In configuration B-ACD dial-peer, if we have more than one incoming ports, must we make each ports a dail-peer, just as Cisco documents put it:

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

    dial-peer voice 1000 pots

     service aa

     incoming called-number 8005550100

     port 1/1/0

     

    dial-peer voice 1001 pots

     service aa

     incoming called-number 8005550100

     port 1/1/1

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

    I am wondering since the incoming called-number is a same number for each port, why don't we just put it in ONLY one dial-peer? Like this:

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

    dial-peer voice 1000 pots

    service aa

    incoming called-number 8005550100

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

    Note that there is no specific "port x/x/x" above. By this all incoming calls with the called number 8005550100 will be handled through service aa no matter which port it comes from, even there are N ports that has incoming calls. Am I right?

    Any idea? thanks.

    Jordan




    Internetwork Expert - The Industry Leader in CCIE Preparation
    http://www.internetworkexpert.com

    Subscription information may be found at:
    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • Hi,Snow

    Your answer is great. Thank you! I'll take time to study your explanation and absord it completely.

    Thanks.


    2009/11/25 msnow <[email protected]>
    Jordan,


    Your configuration will work just fine. You do not have to have the port command to match for an inbound dial peer.

    (you do have to have port for an outbound dial peer to function however)

    Only time you need to have a port specified in a dial peer command is if you have multiple different ports that you want to perform some different inbound call routing function with (not just different DIDs - that you can still do with multiple dial peers with no port statement).





    Also something to note, if you want to trigger BACD for calls originating from either SIP or SCCP phones on a SRST or CUCME, or you want to trigger BACD for calls originating from a H.323 or SIP trunk - you need to have the call originate on an inbound direction (TCL / VXML scripts will NOT trigger on outbound dial peers - only inbound ones). This means that - let's say for example a call coming from a SCCP based ephone - that unless we want EVERY call that comes from that phone to go to BACD (not likely the case), then the inbound dial peer is a POTS dial peer for that ephone/ephone-dn combo, and that we can't place the BACD trigger there, so we need another place to do it. But every call leg ONLY has one inbound and one outbound call leg - so what to do? Well we can send the call out of the router (out the loopback int), thus completing the inbound/outbound requirement, and then since it went to the loopback int, well it Loops Back into the router, and we trigger the BACD there. Works great. 



    So why do I even bring that up since you didn't ask about SCCP/SIP/H.323 calls to BACD?

    Well, simply because you can use one dial peer that will meet every need for sending VoIP calls out of the router, bringing them back in to the router and subsequently triggering BACD, and making sure that every POTS call trying to trigger it will also be able to do so.





    dial-peer voice 5000 voip

     service aa  (triggers AA application on the ingress)

     incoming called-number 8005550100   (matches number for inbound calls from Loopback)

     destination-pattern 8005550100  (matches number for outbound calls)

     session-target ipv4:177.1.254.3  (sends outbound calls to Loopback)

     dtmf-relay h245-signal  (important if you want to be able to press any menu item :))

     no vad

     codec g711ulaw   (important if you want BACD to be able to play any prompts :))





    Then for any POTS inbound needs:



    dial-peer voice 1000 pots

     direct-inward-dial

     incoming called-number .



    HTH!










    On Nov 24, 2009, at 10:05 AM, Jordan wrote:

    Hi,

    In configuration B-ACD dial-peer, if we have more than one incoming ports, must we make each ports a dail-peer, just as Cisco documents put it:

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

    dial-peer voice 1000 pots

     service aa

     incoming called-number 8005550100

     port 1/1/0

     

    dial-peer voice 1001 pots

     service aa

     incoming called-number 8005550100

     port 1/1/1

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

    I am wondering since the incoming called-number is a same number for each port, why don't we just put it in ONLY one dial-peer? Like this:

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

    dial-peer voice 1000 pots

    service aa

    incoming called-number 8005550100

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

    Note that there is no specific "port x/x/x" above. By this all incoming calls with the called number 8005550100 will be handled through service aa no matter which port it comes from, even there are N ports that has incoming calls. Am I right?

    Any idea? thanks.

    Jordan




    Internetwork Expert - The Industry Leader in CCIE Preparation
    http://www.internetworkexpert.com

    Subscription information may be found at:


    http://www.ieoc.com/forums/ForumSubscriptions.aspx







    Internetwork Expert - The Industry Leader in CCIE Preparation
    http://www.internetworkexpert.com

    Subscription information may be found at:
    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • Hi,Snow

     

    According to your post, the inbound POTS seams to have no need to specify even both the called number(the pilot number) and the service aa, as if it is just a normal dial-peer. As you put it:

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

    Then for any POTS inbound needs:


    dial-peer voice 1000 pots
     direct-inward-dial
     incoming called-number .
    ---------------------------------------------------------

    I would Iike to know, why do you make this change? I mean, as the following configuration put:

     

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

    dial-peer voice 1000 pots
    service aa
    incoming called-number 8005550100

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

     

    Since you have admited that this would work when a inbound call from POTS would trigger B-CAD, so why and what is the use of your configuration? I mean, doesn't the POTS calls need to trigger B-ACD if we already have conguration that is used to trigger B-ACD for those SCCP or H323 calls? Or, you just meant that BOTH of the above configuration are needed in the configuration?



     

    Thanks,

    Jordan
  • Hi Jordan, 

    The inbound POTS simply takes the call and passes it to the digit analysis engine (direct-inward-dial) which then matches the outbound voip dial peer which sends it to the Loopback int and brings it back in the same Interface. 
    The only reason to do this is to simplify configuration and allow one dial peer to serve a "one size fits all" dial peer.  

    Mark Snow
    CCIE #14073 (Voice, Security)
    Instructor
    Internetwork Expert

    On Nov 24, 2009, at 22:28, Jordan <[email protected]> wrote:

    Hi,Snow

     

    According to your post, the inbound POTS seams to have no need to specify even both the called number(the pilot number) and the service aa, as if it is just a normal dial-peer. As you put it:

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

    Then for any POTS inbound needs:


    dial-peer voice 1000 pots
     direct-inward-dial
     incoming called-number .
    ---------------------------------------------------------

    I would Iike to know, why do you make this change? I mean, as the following configuration put:

     

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

    dial-peer voice 1000 pots
    service aa
    incoming called-number 8005550100

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

     

    Since you have admited that this would work when a inbound call from POTS would trigger B-CAD, so why and what is the use of your configuration? I mean, doesn't the POTS calls need to trigger B-ACD if we already have conguration that is used to trigger B-ACD for those SCCP or H323 calls? Or, you just meant that BOTH of the above configuration are needed in the configuration?



     

    Thanks,

    Jordan



    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
Sign In or Register to comment.