[cisco-voip] dial-peer E1 ISDN

Joel Perez tman701 at gmail.com
Tue Feb 8 12:32:19 EST 2011 

Ok that is a little better now with that description.
>From the looks of things your client is using an E1 as a voice E1, meaning
that its a PRI to his ISP.
Your E1 is setup as a "Data" E1 not voice "PRI".
You cant send calls to your client via your E1 unless you are both directly
connected to each other, which in this case doesnt seem to be, or his R2 has
an IP address that you can then send calls to using the "session target"
command in your dial-peer statement.
You cant specify a port in a dial-peer using the "Session target" command.
You need an IP address of the receving GW which in this case would be R2.

Your dial peer would need to look like this for it to work with your current
E1 configuration:
dial-peer voice 1 voip
destination-pattern 1000
session target ipv4:X.X.X.X  <--- X is the IP address of R2 that is
accepting inbound voice traffic.

Does your client use his E1(R2) for sending/receiving voice(calls) traffic
to/from his ISP currently? Or were these E1's setup in order for you and
your client to send voice traffic to each other exclusively?


On Tue, Feb 8, 2011 at 12:04 PM, Just Kennie <justkennie at gmail.com> wrote:

> *I think I need to show this with a diagram.*
>
>
>            *R1 (E1)--------------ISP
> (DEMAC)-----------------------------ISP (DEMAC)--------------------------
> (E1) R2---------------CUCM*
>
>    *My router is R1 (2811) and my client is R2(2600). We are connected
> with E1 interface through an ISP with two demac. The ideal is, I want to be
> able to call the phones in my client's place with extension 1000, but i need
> a connection from R1 to R2
>    My client is using an E1 interface with the following
> configuration......
> *
> *card type e1 1 1
> !
> network-clock-participate slot 1
> no network-clock-participate wic 0
> network-clock-select 2 E1 1/1
> !
> isdn switch-type primary-net5
> voice-card 1
> !
> !
> !
> voice rtp send-recv
> !
> !
> !
> voice class permanent 1
> signal timing oos timeout disabled
> signal keepalive 65535
> !
> !
> controller E1 1/0
> framing NO-CRC4
> pri-group timeslots 1-31 service mgcp
> !
> interface Serial1/0:15
> no ip address
> encapsulation hdlc
> isdn switch-type primary-net5
> isdn incoming-voice voice
> isdn bind-l3 ccm-manager
> no cdp enable
> !
> !
> voice-port 1/0:15
> cptone GB*
>
> *(No VOIP dial-peer as client is using MGCP GATEWAY)*
>
> * And below is my own configuration........*
>
> *
> controller E1 0/2/0
> framing NO-CRC4
> channel-group 15 timeslots 1-31
>
> !
> interface Serial0/2/0:15
> bandwidth 2048
> no ip address
> encapsulation hdlc
>
>
> dial-peer voice 1 pots
> destination-pattern 1000
> session target  port 0/2/0:15*  * ( Router is rejecting this command)*
>
> *THE CLIENT WONT ALTER HE'S INTERFACE CONFIGURATION, BUT I CAN ALTER MINE.
> I JUST WANT REACHABILITY BETWEEN THE TWO ROUTERS, SO THAT VOICE TRAFFIC FROM
> MY ROUTER CAN GO THROUGH  E1 INTERFACE TO MY CLIENT (R2).*
> *PLEASE TELL ME WHAT EVER I NEED TO CHANGE OR CONFIGURE ON MY ROUTER TO
> MAKE THIS WORK*.
>
>
>
>
>
>
> *Cheers,
> Idowu Kehinde
> TEL: 2348024017748
> BB:  30E8E5F9
> *
>
>
>
> On Tue, Feb 8, 2011 at 3:07 AM, Joel Perez <tman701 at gmail.com> wrote:
>
>> Ok i was under the impression that the E1 was a PRI for Voice.
>> If the E1 is just a data uplink to another GW somewhere else then you need
>> a voip dial peer and a "destination address" in that voip dial peer. The
>> "destination address" should be the IP of the receiving GW, not your own E1
>> interface.
>>
>> Can you sort of describe your intended call flow? If
>>
>>
>> On Mon, Feb 7, 2011 at 5:59 PM, Just Kennie <justkennie at gmail.com> wrote:
>>
>>> Sorry not ISDN, HDLC encapsulation on the s0/2/0:15 I mean. I guess I
>>> just explained the setup. Trying to route traffic through an E1 interface to
>>> a remote destination that all !
>>> I have written my present config out,and that all. Just need someone to
>>> help me with this, since the interface doesnt use an IP address.
>>>
>>>
>>> *Cheers,
>>> Idowu Kehinde
>>> TEL: 2348024017748
>>> BB:  30E8E5F9
>>> *
>>>
>>>
>>>
>>> On Mon, Feb 7, 2011 at 11:18 PM, Paul <asobihoudai at yahoo.com> wrote:
>>>
>>>> I'm not understanding your setup. If this is supposed to be ISDN PRI,
>>>> where is your PRI group? I've never heard or performed a G.703 ISDN
>>>> setup..<?>
>>>>
>>>> ------------------------------
>>>> *From:* Just Kennie <justkennie at gmail.com>
>>>> *To:* Joel Perez <tman701 at gmail.com>
>>>> *Cc:* Paul <asobihoudai at yahoo.com>; ccieid1ot at gmail.com;
>>>> cisco-voip at puck.nether.net
>>>> *Sent:* Mon, February 7, 2011 1:00:44 PM
>>>> *Subject:* Re: [cisco-voip] dial-peer E1 ISDN
>>>>
>>>> Cciedot1ot, I am using the E1 for voice, and its like an ISDN setup,
>>>> that's why there is no ipv4 address. its G.703.
>>>> Joel, I did what you said I should do...
>>>>
>>>> *controller E1 0/2/0
>>>>  framing NO-CRC4
>>>>  channel-group 15 timeslots 1-31
>>>>  description G703.E1.Connection to customer
>>>> !
>>>> interface Serial0/2/0:15
>>>>  description G703.E1.Connection to customer
>>>>  bandwidth 2048
>>>>  no ip address
>>>> !*
>>>> And see the below error when i want to map port to it.
>>>>
>>>> *dial-peer voice 1 pots
>>>>  destination-pattern 1000
>>>> **MY_ROUTER(config-dial-peer)#port 0/2/0:15
>>>>                                                           ^
>>>> % Invalid input detected at '^' marker.
>>>> *
>>>> In my own opinion, I guess "*port 0/2/0:15*" is trying used when
>>>> specifying an FSX/FSO port, but here, I want to specify the E1 interface for
>>>> the voice traffic destined for 1000 on a remote router.
>>>>
>>>> *REALLY NEED HELP !!!*
>>>>
>>>>
>>>>
>>>> *Cheers,
>>>> Idowu Kehinde
>>>> TEL: 2348024017748
>>>> BB:  30E8E5F9
>>>> *
>>>>
>>>>
>>>>
>>>> On Mon, Feb 7, 2011 at 8:04 PM, Joel Perez <tman701 at gmail.com> wrote:
>>>>
>>>>> If im understanding correctly what you are trying to do then you have a
>>>>> few things wrong.
>>>>>
>>>>> for E1's I use channel 15 for the D-channel:
>>>>> * *interface Serial0/2/0:15
>>>>>
>>>>> For the dial peers like it was pointed out it needs to be a POTS dial
>>>>> peer and also needs to point to D channel 15.
>>>>> port 0/2/0:15
>>>>>
>>>>> "session target" is used to send to an IPv4 address.
>>>>>
>>>>> Hope that helps,
>>>>>
>>>>> Joel P
>>>>>
>>>>> On Mon, Feb 7, 2011 at 1:40 PM, Just Kennie <justkennie at gmail.com>wrote:
>>>>>
>>>>>> Paul/ccieidot1,
>>>>>>
>>>>>> well I have a fsx voice-port of (but not in use)
>>>>>>
>>>>>> *voice-port 0/0/0
>>>>>> !
>>>>>> voice-port 0/0/1
>>>>>> !
>>>>>> voice-port 0/0/2*
>>>>>> !
>>>>>> *voice-port 0/0/3*
>>>>>> !
>>>>>> and an E1 interface of... (connected to remote router)
>>>>>>
>>>>>> *
>>>>>> controller E1 0/2/0
>>>>>>  framing NO-CRC4
>>>>>>  channel-group 0 timeslots 1-31
>>>>>>  !
>>>>>>  interface Serial0/2/0:0
>>>>>>  description G703.E1.Connection to Customer router
>>>>>>
>>>>>>  bandwidth 2048
>>>>>>  no ip address
>>>>>> encap HDLC*
>>>>>> !
>>>>>> I am using the E1 interface to connect to a remote router with E1
>>>>>> interface too at the other end with above config
>>>>>>
>>>>>> May challenge is, I want to configure a dial-peer that will route all
>>>>>> my voice traffic destined to 1000 through the E1 card, so i configure the
>>>>>> following....
>>>>>>
>>>>>>
>>>>>> *dial-peer voice 1 pots
>>>>>> destination-pattern 21232
>>>>>> session target port 0/0/0:0
>>>>>> !
>>>>>> *
>>>>>> but saw the following error....*
>>>>>>
>>>>>> MY_ROUTER(config-dial-peer)#session target port 0/2/0:0
>>>>>>
>>>>>>        ^
>>>>>> % Invalid input detected at '^' marker.
>>>>>>
>>>>>> *Also when I use *port 0/2/0:0* as advised by ccieidot1, I receive
>>>>>> the following message..*
>>>>>>
>>>>>> MY_ROUTER(config-dial-peer)#port 0/2/0:0
>>>>>>                                                              ^
>>>>>> % Invalid input detected at '^' marker.
>>>>>> !
>>>>>> *
>>>>>> Please assist, as what I want to achieve is to route all voice traffic
>>>>>> destined to 1000 at the remote site through the E1 interface.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Cheers,
>>>>>> Idowu Kehinde
>>>>>> TEL: 2348024017748
>>>>>> BB:  30E8E5F9
>>>>>> *
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 7, 2011 at 7:09 PM, Paul <asobihoudai at yahoo.com> wrote:
>>>>>>
>>>>>>> What is the label on your voice-port?
>>>>>>>
>>>>>>> I'm going to guess that your voice-port is also 0/2/0:0...I've never
>>>>>>> touched an E1 so I am a little bit confused when I don't see :31 at the end
>>>>>>> instead of the "0" you have there but..it looks like you're trying to send
>>>>>>> calls to a voice port that doesn't exist and you're trying to use session
>>>>>>> target when that's used for voip dial peers.
>>>>>>>
>>>>>>> You're looking for
>>>>>>> port 0/2/0:0 instead.
>>>>>>>
>>>>>>> ------------------------------
>>>>>>> *From:* Just Kennie <justkennie at gmail.com>
>>>>>>> *To:* cisco-voip at puck.nether.net
>>>>>>> *Sent:* Mon, February 7, 2011 10:00:42 AM
>>>>>>> *Subject:* [cisco-voip] dial-peer E1 ISDN
>>>>>>>
>>>>>>> Hi All,
>>>>>>> I am trying to configure my E1 card for ISDN connectivity for voice
>>>>>>> traffic, below is my config...
>>>>>>>
>>>>>>> *controller E1 0/2/0
>>>>>>>  framing NO-CRC4
>>>>>>>  channel-group 0 timeslots 1-31
>>>>>>> !
>>>>>>> interface Serial0/2/0:0
>>>>>>>  description G703.E1.Connection to Customer
>>>>>>>  bandwidth 2048
>>>>>>>  no ip address*
>>>>>>> *encapp HDLC*
>>>>>>> *!*
>>>>>>> Now I am trying to configure the Dial-peer, to forward 2123 calls
>>>>>>> through the E1 ISDN interface
>>>>>>> !
>>>>>>> *dial-peer voice 1 pots
>>>>>>> destination-pattern 21232
>>>>>>> session target port 0/0/0:0*
>>>>>>> !
>>>>>>> but its my 2811 voice gateway is not allowing the "session target
>>>>>>> port 0/0/0:0" command, please what should I do to forward my calls through
>>>>>>> the E1 ISDN interface.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *Cheers,
>>>>>>> Idowu Kehinde
>>>>>>> TEL: 2348024017748
>>>>>>> BB:  30E8E5F9
>>>>>>> *
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> cisco-voip mailing list
>>>>>>
>>>>>> cisco-voip at puck.nether.net
>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110208/d3e1617c/attachment.html>

More information about the cisco-voip mailing list