[asterisk-bugs] [Asterisk 0015048]: [patch] NT over PtMP for BRI
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon May 18 15:50:38 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15048
======================================================================
Reported By: vrban
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15048
Category: Channels/chan_dahdi/NewFeature
Reproducibility: N/A
Severity: feature
Priority: normal
Status: new
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-05-07 07:34 CDT
Last Modified: 2009-05-18 15:50 CDT
======================================================================
Summary: [patch] NT over PtMP for BRI
Description:
Ok, this patch is a naive test i made, but very very limited a bit is
allready working. You can call from one connected ISDN device (i used a
ISDN/analog adapter DeTeWe TA33) into chan_dadhi. That's all, nothing more.
You can't call from chan_dadi to the ISDN device or connect multiple isdn
devices.
Also chan_dadi jumps directly to the s-Extension when you lift up the
phone. And dont give you dial tone or wait for digits. But i was pleasantly
surprised that NT-ptmp is working anyway.
Let's start to work on this, to finally ditch bristuff and chan_misdn
======================================================================
----------------------------------------------------------------------
(0104970) vrban (reporter) - 2009-05-18 15:50
https://issues.asterisk.org/view.php?id=15048#c104970
----------------------------------------------------------------------
check attached file call_to_bristuff_ast_ok
The log when i call to an bristuffed *1.4 is working, and lokks a bit
diffrent:
the CONNECT ACKNOWLEDGE message we send now looks:
> Informational frame:
> SAPI: 63 C/R: 1 EA: 0 <---- SAPI should be 0? 63 is for TEI
management
> TEI: 064 EA: 1
> N(S): 003 0: 0 <---- What function this line have?
> N(R): 005 P: 0 <---- What function this line have?
> 4 bytes of data
Stopping T_203 timer
Starting T_200 timer
-- Restarting T200 timer
> Protocol Discriminator: Q.931 (8) len=4
> Call Ref: len= 1 (reference 3/0x3) (Originator)
> Message Type: CONNECT ACKNOWLEDGE (15)
And the call to mISDNuser:
> Informational frame:
> SAPI: 00 C/R: 1 EA: 0 <---- SAPI 0 here is good
> TEI: 064 EA: 1
> N(S): 000 0: 0 <---- What function this line have?
> N(R): 000 P: 0 <---- What function this line have?
> 4 bytes of data
Stopping T_203 timer
Starting T_200 timer
-- Restarting T200 timer
> Protocol Discriminator: Q.931 (8) len=4
> Call Ref: len= 1 (reference 2/0x2) (Originator)
> Message Type: CONNECT ACKNOWLEDGE (15)
Issue History
Date Modified Username Field Change
======================================================================
2009-05-18 15:50 vrban Note Added: 0104970
======================================================================
More information about the asterisk-bugs
mailing list