[cisco-nas] ISDN calls not making it to NM-6DM
joshd
jduffek at gmail.com
Mon Feb 2 08:51:54 EST 2015
So just O CONFREQs on each side then? You could look at the "sh int
se1/0:x"/b-channel, maybe you're getting input errors or something?
On Sat, Jan 31, 2015 at 1:38 PM, Tom Storey <tom at snnap.net> wrote:
> Played around with this a bit more, and Ive configured up my Se1/0:15
> interface with PPP et al, almost matches the Group-Async interface, so
> should be right.
>
> When the ISDN data call establishes (what looks to be successfully) I see
> both ends start TXing PPP LCP packets, which is a good sign, but neither
> end is receiving anything from the other side.
>
> Pitty I cant wireshark the B channels to see whats going back and forth.
> :-P
>
> On 31 January 2015 at 00:08, Mark Johnson (mljohnso) <mljohnso at cisco.com>
> wrote:
>
>> Yeah, the DM’s are only going to terminate analog calls. As Josh says
>> (long time, Josh!), configure the PRI (or use Legacy DDR or Dialer
>> Profiles) and you should be good.
>>
>> mark
>>
>> From: joshd <jduffek at gmail.com>
>> Date: Friday, January 30, 2015 at 3:52 PM
>> To: Tom Storey <tom at snnap.net>
>> Cc: Mark Johnson <mljohnso at cisco.com>, "cisco-nas at puck.nether.net" <
>> cisco-nas at puck.nether.net>
>> Subject: Re: [cisco-nas] ISDN calls not making it to NM-6DM
>>
>> If you just want to make it work, you can configure your IP stuff on
>> the serial1/0:15 interface and the call should terminate there. ISDN to
>> ISDN like.
>>
>> Not sure how you would simulate a real analog modem type call from the
>> 1841 side with what you have.
>>
>> I could be wrong though, been a while...
>>
>> jd.
>>
>> On Fri, Jan 30, 2015 at 5:32 PM, Tom Storey <tom at snnap.net> wrote:
>>
>>> Hi Mark, did not expect such a quick response!
>>>
>>> Indeed it is originating from the 1841 as 8890.
>>>
>>> I also re-configured the 1841 to do DoV, where the bearercap changed
>>> to 0x8090A3, and this was also seen as the incomming bearercap on the 3825.
>>>
>>> I was under the impression from my reading that the NM-xDM could also
>>> terminate ISDN data calls, or have I got that wrong?
>>>
>>> Cheers!
>>>
>>> On 30 January 2015 at 23:27, Mark Johnson (mljohnso) <mljohnso at cisco.com
>>> > wrote:
>>>
>>>> A bearer cap of 0x8890 means the call is digital, not analog, so the
>>>> call is not being passed to a modem. Your emulating network in between
>>>> must be mucking with the bearer cap (check out debug on the 1841 to verify
>>>> that it’s not originating at 8890).
>>>>
>>>> mark
>>>>
>>>> From: Tom Storey <tom at snnap.net>
>>>> Date: Friday, January 30, 2015 at 3:13 PM
>>>> To: "cisco-nas at puck.nether.net" <cisco-nas at puck.nether.net>
>>>> Subject: [cisco-nas] ISDN calls not making it to NM-6DM
>>>>
>>>> Hi everyone.
>>>>
>>>> Playing around with some old hardware in a lab, trying to get some
>>>> ISDN calls originated from an 1841 with a WIC-1B-S/T-V3 to be answered on a
>>>> 3825 with a NM-6D and NM-CE1T1-PRI.
>>>>
>>>> Heres my config:
>>>>
>>>> controller E1 1/0
>>>> pri-group timeslots 1-6,16
>>>> !
>>>> interface Serial1/0:15
>>>> no ip address
>>>> encapsulation ppp
>>>> isdn switch-type primary-net5
>>>> isdn incoming-voice modem 64
>>>> isdn bchan-number-order ascending
>>>> !
>>>> interface Group-Async0
>>>> ip unnumbered Loopback0
>>>> ip nat inside
>>>> ip virtual-reassembly in
>>>> encapsulation ppp
>>>> peer default ip address pool dialup
>>>> async mode interactive
>>>> no keepalive
>>>> ppp authentication chap callin
>>>> group-range 2/0 2/5
>>>> !
>>>> line 2/0 2/5
>>>> modem InOut
>>>> autoselect ppp
>>>> !
>>>>
>>>> And heres what I see when an ISDN call comes in:
>>>>
>>>> *Jan 30 23:31:24.963 UTC: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8
>>>> callref = 0x0183
>>>> Bearer Capability i = 0x8890
>>>> Standard = CCITT
>>>> Transfer Capability = Unrestricted Digital
>>>> Transfer Mode = Circuit
>>>> Transfer Rate = 64 kbit/s
>>>> Channel ID i = 0xA98381
>>>> Exclusive, Channel 1
>>>> Calling Party Number i = 0x80, '0733944124'
>>>> Plan:Unknown, Type:Unknown
>>>> Called Party Number i = 0x80
>>>> Plan:Unknown, Type:Unknown
>>>> *Jan 30 23:31:24.963 UTC: ISDN Se1/0:15 Q931: Received SETUP callref =
>>>> 0x8183 callID = 0x01E5 switch = primary-net5 interface = User
>>>> *Jan 30 23:31:24.971 UTC: %ISDN-6-CONNECT: Interface Serial1/0:0 is now
>>>> connected to 0733944124 N/A
>>>> *Jan 30 23:31:24.971 UTC: ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8
>>>> callref = 0x8183
>>>> Channel ID i = 0xA98381
>>>> Exclusive, Channel 1
>>>> *Jan 30 23:31:24.971 UTC: ISDN Se1/0:15 Q931: TX -> CONNECT pd = 8
>>>> callref = 0x8183
>>>> Channel ID i = 0xA98381
>>>> Exclusive, Channel 1
>>>> *Jan 30 23:31:24.979 UTC: ISDN Se1/0:15 Q931: RX <- CONNECT_ACK pd = 8
>>>> callref = 0x0183
>>>>
>>>> So as far as I can tell the call comes in and establishes fine, but
>>>> even with "debug modem" and a couple of other debugs on, I dont see any
>>>> activity regarding connection to a modem. When I dial in from an analogue
>>>> modem it works just fine.
>>>>
>>>> FWIW I am using the 3825 as a PSTN simulator as well. The 1841 is
>>>> connected to a VIC2-2BRI-NT/TE emulating network, and a dialpeer connects
>>>> calls to a VWIC2-2MTF-E1 which is also emulating network and is connected
>>>> to the NM-CE1T1-PRI.
>>>>
>>>> Wondering if any one can provide any pointers to help me out. Am I
>>>> missing something obvious?
>>>>
>>>> Let me know if you require more information.
>>>>
>>>> Thanks
>>>> Tom
>>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-nas mailing list
>>> cisco-nas at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nas
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-nas/attachments/20150202/7cea1365/attachment.html>
More information about the cisco-nas
mailing list