[SIPForum-discussion] Cisco 3640 and SIP

Mostafa Ali mmostafa at nile-online.net
Thu Dec 7 18:53:23 UTC 2006


This can be done easily using Policy based routing 
Check this link :
http://www.cisco.com/warp/public/732/Tech/plicy_wp.htm
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/qos_c/qcpart1/qcpolicy.htm

Regards
  ----- Original Message ----- 
  From: Richards, Dick 
  To: Nelson Pereira ; discussion at sipforum.org 
  Sent: Wednesday, December 06, 2006 9:02 PM
  Subject: Re: [SIPForum-discussion] Cisco 3640 and SIP


  OK.  We have attempted to do something similar, and have been successful.  Cisco does not support logical SIP trunks over a common interface.  Everything is tied to the physical port.  There has been some discussions with Ciso Product Management about using a SIP Trunk ID attribute as part of dial peers, but they have not yet produced code to support this (that I am aware of).  Sorry I can be of more help.



------------------------------------------------------------------------------
  From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of Nelson Pereira
  Sent: Wednesday, December 06, 2006 5:54 AM
  To: discussion at sipforum.org
  Subject: Re: [SIPForum-discussion] Cisco 3640 and SIP


  We are not doing outbound to PSTN to sip, it's basically inbound SIP to PSTN, although the PSTN is not on the Cisco Router. We use primarely a AudioCodes MediaGateway for the actual SIP to PSTN. So the 3640 is only used to route traffic from WAN to LAN

  What I was inquiring about is how to setup the 3640 to route traffic comming from one specific Public IP ( the wan interface has 2 Public IP) to route it to a Specific LAN interface. So for visuals :

  Public IP 66.46.196.120    \                            ***********************    ------------ LAN ETH1 10.1.10.1
                                           | ----  WAN ETH1   **** Cisco 3640 *****        
  Public IP 66.46.196.121    /                            ***********************    ------------ LAN ETH2 10.1.11.1

  Our Provider has setup round robin on both Public IP address. We have 2 LAN interface for redundancy and to connect to the 2 Trunk Pack Module on the Mediagateway.

  I need to find a way to route traffic from a specific destination IP to a specific LAN interface.

  can this be done? If so, how?

  If all else fails and this can't be done, we'll need to go to a Softswitch scenerio which is 50+ G's which is something i would like to avoid at all cost if i can acheive this with the Cisco 3640 as I just installed 4 of them. 

  Regards,

  NP



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

    Subject: RE: [SIPForum-discussion] Cisco 3640 and SIP


    I have not done exactly what you are trying to do.    Cisco's IPIPGW is not very flexible, and is based on the same dial-peer based configurations as with a TDM-IP gateway.  The challange you will have is sourcing calls from one LAN FE to the appropriate WAN side IP.  I don't know of a way to do this.  Sorry!     



----------------------------------------------------------------------------
    From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of Nelson Pereira
    Sent: Tuesday, December 05, 2006 12:28 PM
    To: discussion at sipforum.org
    Subject: Re: [SIPForum-discussion] Cisco 3640 and SIP


    We are running flash:c3640-jk9o3s-mz.124-5a.bin
    so i guess we dont have this option then.

    So if i have my 3640 with 1 WAN FE and 2 LAN FE's
    How could I have 2 WAN IP's on the WAN FE, and then route each Public IP to a specific LAN FE?
    This way I could ask the Provider to do round-robin on there side at the Softswitch.

    thanks

    NP
          The content contained in this electronic message is not intended to
          constitute formation of a contract binding TWTC. TWTC will be
          contractually bound only upon execution, by an authorized officer, of
          a contract including agreed terms and conditions or by express
          application of its tariffs.

          This message is intended only for the use of the individual or entity
          to which it is addressed. If the reader of this message is not the
          intended recipient, or the employee or agent responsible for
          delivering the message to the intended recipient, you are hereby
          notified that any dissemination, distribution or copying of this
          message is strictly prohibited. If you have received this
          communication in error, please notify us immediately by replying to
          the sender of this E-Mail or by telephone.
         

        The content contained in this electronic message is not intended to
        constitute formation of a contract binding TWTC. TWTC will be
        contractually bound only upon execution, by an authorized officer, of
        a contract including agreed terms and conditions or by express
        application of its tariffs.

        This message is intended only for the use of the individual or entity
        to which it is addressed. If the reader of this message is not the
        intended recipient, or the employee or agent responsible for
        delivering the message to the intended recipient, you are hereby
        notified that any dissemination, distribution or copying of this
        message is strictly prohibited. If you have received this
        communication in error, please notify us immediately by replying to
        the sender of this E-Mail or by telephone.
       



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


  _______________________________________________
  This is the SIP Forum discussion mailing list
  TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
  Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20061207/ab8bf1c9/attachment-0001.html>


More information about the discussion mailing list