thr3ads.net - asterisk users - [Asterisk-Users] Asterisk and a Meridian Nortell Release 11 [Aug 2005]

If this information is useful, please help other people find it:
Share via:

Alvaro Parres

2005-Aug-27 07:20 UTC

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

Hi, i have one Asterisk with a Digium E1 card, and a Meridian Nortel
Release 11.
I need to connect both of them. We are using MFC/R2 for this..

The Diagram:

[ NORTEL ] ( AMI ) ------------------------------------------------
(DIGIUM) [ ASTERISK]

we have green light at the digium card, and at asterisk we see all 31
channels as idle.

But when i want to recive a call from the Nortel to the Asterisk i get
at the Nortel only a empty sound, and after about 15 o 20 sec it's
hangup.

Any suggestion ?

The log at Asterisk is:

Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30      <- 0001  [1/       1/Idle          /Idle       
 ]
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Detected
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Making a new call with CRN 32769
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 1101  ->      [2/       2/Idle          /Idle       
 ]
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
Unicall/30 event Detected
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30      <- 0001  [1/       1/Idle          /Idle       
 ]
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Detected
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Making a new call with CRN 32769
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 1101  ->      [2/       2/Idle          /Idle       
 ]
Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
Unicall/30 event Detected
tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704
unicall_report: MFC/R2 UniCall/30      <- 1001  [2/       2/Seize ack 
   /Seize ack    ]
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Far end disconnected(cause=Normal, unspecified cause
[31]) - state 0x2
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
Unicall/30 event Far end disconnected
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:3198 handle_uc_event:
CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Call control(6)
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Drop call(cause=Normal Clearing [16])
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Call disconnected(cause=Normal, unspecified cause
[31]) - state 0x800
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
Unicall/30 event Drop call
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Call control(7)
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Release call
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 1001  ->      [1/    1000/Clear fwd     /Seize ack  
 ]
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30      <- 1001  [2/       2/Seize ack     /Seize ack  
 ]
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Far end disconnected(cause=Normal, unspecified cause
[31]) - state 0x2
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
Unicall/30 event Far end disconnected
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:3198 handle_uc_event:
CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Call control(6)
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Drop call(cause=Normal Clearing [16])
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Call disconnected(cause=Normal, unspecified cause
[31]) - state 0x800
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
Unicall/30 event Drop call
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Call control(7)
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Release call
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 1001  ->      [1/    1000/Clear fwd     /Seize ack  
 ]
tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704
unicall_report: MFC/R2 UniCall/30 Release guard expired
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Destroying call with CRN 32769
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Release guard expired
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
MFC/R2 UniCall/30 Destroying call with CRN 32769
tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865
handle_uc_event: Unicall/30 event Release call
    -- Unicall/30 released
Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
Unicall/30 event Release call
    -- Unicall/30 released

unicall.conf
[channels]
context=callin
usecallerid=yes
hidecallerid=no
callwaitingcallerid=yes
threewaycalling=no
transfer=no
cancallforward=no
callreturn=no
echocancel=no
echocancelwhenbridged=no
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
loglevel=1023
protocolclass=mfcr2
protocolvariant=mx,4,4
protocolend=cpe ;co
group = 3
channel => 1-31

zaptel.conf
span=1,0,0,cas,hdb3
cas=1-31:1101
defaultzone=us


Thanks.

Anthony Rodgers

2005-Aug-29 09:54 UTC

head link

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

Hi there,

We are using * with an Option 11C - we tried all of the various  
protocols and the only one we could get to work satisfactorily was  
5ESS, with the * as CO and the Nortel as remote. The one drawback of  
this approach is getting name information for caller ID - because the  
Nortel sees the * as CO, it won't send the name information.

/etc/zaptel.conf:

span=1,1,0,esf,b8zs
bchan=1-23
dchan=24
#clear=1-24
loadzone = us
defaultzone=us

/etc/asterisk/zapata.conf:

[trunkgroups]

[channels]

context=incoming
switchtype=5ess
usecallingpres=yes
echocancel=128
usecallerid=yes
echocancelwhenbridged=yes
echotraining=yes
echotraining=800

rxgain=-4.0
txgain=-6.0
group=1
callgroup=1
pickupgroup=1
signalling = pri_net
channel => 1-23

musiconhold=default

Any use?

Regards,
-- 
Anthony Rodgers
Business Systems Analyst
District of North Vancouver
Web: http://www.dnv.org
RSS Feed: http://www.dnv.org/rss.asp


On 27-Aug-05, at 7:20 AM, Alvaro Parres wrote:
> Hi, i have one Asterisk with a Digium E1 card, and a Meridian Nortel
> Release 11.
> I need to connect both of them. We are using MFC/R2 for this..
>
> The Diagram:
>
> [ NORTEL ] ( AMI ) ------------------------------------------------
> (DIGIUM) [ ASTERISK]
>
> we have green light at the digium card, and at asterisk we see all 31
> channels as idle.
>
> But when i want to recive a call from the Nortel to the Asterisk i get
> at the Nortel only a empty sound, and after about 15 o 20 sec it's
> hangup.
>
> Any suggestion ?
>
> The log at Asterisk is:
>
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30      <- 0001  [1/       1/Idle          /Idle
>  ]
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Detected
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Making a new call with CRN 32769
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 1101  ->      [2/       2/Idle          /Idle
>  ]
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> Unicall/30 event Detected
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30      <- 0001  [1/       1/Idle          /Idle
>  ]
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Detected
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Making a new call with CRN 32769
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 1101  ->      [2/       2/Idle          /Idle
>  ]
> Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> Unicall/30 event Detected
> tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704
> unicall_report: MFC/R2 UniCall/30      <- 1001  [2/       2/Seize ack
>    /Seize ack    ]
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Far end disconnected(cause=Normal, unspecified cause
> [31]) - state 0x2
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> Unicall/30 event Far end disconnected
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:3198 handle_uc_event:
> CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Call control(6)
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Drop call(cause=Normal Clearing [16])
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Call disconnected(cause=Normal, unspecified cause
> [31]) - state 0x800
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> Unicall/30 event Drop call
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Call control(7)
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Release call
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 1001  ->      [1/    1000/Clear fwd     /Seize ack
>  ]
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30      <- 1001  [2/       2/Seize ack     /Seize ack
>  ]
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Far end disconnected(cause=Normal, unspecified cause
> [31]) - state 0x2
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> Unicall/30 event Far end disconnected
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:3198 handle_uc_event:
> CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Call control(6)
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Drop call(cause=Normal Clearing [16])
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Call disconnected(cause=Normal, unspecified cause
> [31]) - state 0x800
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> Unicall/30 event Drop call
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Call control(7)
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Release call
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 1001  ->      [1/    1000/Clear fwd     /Seize ack
>  ]
> tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704
> unicall_report: MFC/R2 UniCall/30 Release guard expired
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Destroying call with CRN 32769
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Release guard expired
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> MFC/R2 UniCall/30 Destroying call with CRN 32769
> tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865
> handle_uc_event: Unicall/30 event Release call
>     -- Unicall/30 released
> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> Unicall/30 event Release call
>     -- Unicall/30 released
>
> unicall.conf
> [channels]
> context=callin
> usecallerid=yes
> hidecallerid=no
> callwaitingcallerid=yes
> threewaycalling=no
> transfer=no
> cancallforward=no
> callreturn=no
> echocancel=no
> echocancelwhenbridged=no
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> immediate=no
> loglevel=1023
> protocolclass=mfcr2
> protocolvariant=mx,4,4
> protocolend=cpe ;co
> group = 3
> channel => 1-31
>
> zaptel.conf
> span=1,0,0,cas,hdb3
> cas=1-31:1101
> defaultzone=us
>
>
> Thanks.
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
>
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

Damon Estep

2005-Aug-29 11:40 UTC

head link

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

Where does the CNAM originate, is it sent to the Nortel from the PSTN
and then passed on to *, or does it originate on the Nortel?

There may be another way, but without more info I do not wan to peak out
of context.
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-
> bounces@lists.digium.com] On Behalf Of Anthony Rodgers
> Sent: Monday, August 29, 2005 10:54 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] Asterisk and a Meridian Nortell Release
11> 
> Hi there,
> 
> We are using * with an Option 11C - we tried all of the various
> protocols and the only one we could get to work satisfactorily was
> 5ESS, with the * as CO and the Nortel as remote. The one drawback of
> this approach is getting name information for caller ID - because the
> Nortel sees the * as CO, it won't send the name information.
> 
> /etc/zaptel.conf:
> 
> span=1,1,0,esf,b8zs
> bchan=1-23
> dchan=24
> #clear=1-24
> loadzone = us
> defaultzone=us
> 
> /etc/asterisk/zapata.conf:
> 
> [trunkgroups]
> 
> [channels]
> 
> context=incoming
> switchtype=5ess
> usecallingpres=yes
> echocancel=128
> usecallerid=yes
> echocancelwhenbridged=yes
> echotraining=yes
> echotraining=800
> 
> rxgain=-4.0
> txgain=-6.0
> group=1
> callgroup=1
> pickupgroup=1
> signalling = pri_net
> channel => 1-23
> 
> musiconhold=default
> 
> Any use?
> 
> Regards,
> --
> Anthony Rodgers
> Business Systems Analyst
> District of North Vancouver
> Web: http://www.dnv.org
> RSS Feed: http://www.dnv.org/rss.asp
> 
> 
> On 27-Aug-05, at 7:20 AM, Alvaro Parres wrote:
> 
> > Hi, i have one Asterisk with a Digium E1 card, and a Meridian Nortel
> > Release 11.
> > I need to connect both of them. We are using MFC/R2 for this..
> >
> > The Diagram:
> >
> > [ NORTEL ] ( AMI ) ------------------------------------------------
> > (DIGIUM) [ ASTERISK]
> >
> > we have green light at the digium card, and at asterisk we see all
31> > channels as idle.
> >
> > But when i want to recive a call from the Nortel to the Asterisk i
get> > at the Nortel only a empty sound, and after about 15 o 20 sec it's
> > hangup.
> >
> > Any suggestion ?
> >
> > The log at Asterisk is:
> >
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30      <- 0001  [1/       1/Idle          /Idle
> >  ]
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Detected
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Making a new call with CRN 32769
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 1101  ->      [2/       2/Idle          /Idle
> >  ]
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> > Unicall/30 event Detected
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30      <- 0001  [1/       1/Idle          /Idle
> >  ]
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Detected
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Making a new call with CRN 32769
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 1101  ->      [2/       2/Idle          /Idle
> >  ]
> > Aug 27 09:16:20 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> > Unicall/30 event Detected
> > tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704
> > unicall_report: MFC/R2 UniCall/30      <- 1001  [2/       2/Seize
ack> >    /Seize ack    ]
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Far end disconnected(cause=Normal, unspecified
cause> > [31]) - state 0x2
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> > Unicall/30 event Far end disconnected
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:3198 handle_uc_event:
> > CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Call control(6)
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Drop call(cause=Normal Clearing [16])
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Call disconnected(cause=Normal, unspecified cause
> > [31]) - state 0x800
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> > Unicall/30 event Drop call
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Call control(7)
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Release call
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 1001  ->      [1/    1000/Clear fwd     /Seize
ack
> >  ]
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30      <- 1001  [2/       2/Seize ack     /Seize
ack
> >  ]
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Far end disconnected(cause=Normal, unspecified
cause> > [31]) - state 0x2
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> > Unicall/30 event Far end disconnected
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:3198 handle_uc_event:
> > CRN 32769 - far disconnected cause=Normal, unspecified cause [31]
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Call control(6)
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Drop call(cause=Normal Clearing [16])
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Call disconnected(cause=Normal, unspecified cause
> > [31]) - state 0x800
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> > Unicall/30 event Drop call
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Call control(7)
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Release call
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 1001  ->      [1/    1000/Clear fwd     /Seize
ack
> >  ]
> > tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704
> > unicall_report: MFC/R2 UniCall/30 Release guard expired
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Destroying call with CRN 32769
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Release guard expired
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:704 unicall_report:
> > MFC/R2 UniCall/30 Destroying call with CRN 32769
> > tel2*CLI> Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865
> > handle_uc_event: Unicall/30 event Release call
> >     -- Unicall/30 released
> > Aug 27 09:16:36 WARNING[6496]: chan_unicall.c:2865 handle_uc_event:
> > Unicall/30 event Release call
> >     -- Unicall/30 released
> >
> > unicall.conf
> > [channels]
> > context=callin
> > usecallerid=yes
> > hidecallerid=no
> > callwaitingcallerid=yes
> > threewaycalling=no
> > transfer=no
> > cancallforward=no
> > callreturn=no
> > echocancel=no
> > echocancelwhenbridged=no
> > rxgain=0.0
> > txgain=0.0
> > group=1
> > callgroup=1
> > pickupgroup=1
> > immediate=no
> > loglevel=1023
> > protocolclass=mfcr2
> > protocolvariant=mx,4,4
> > protocolend=cpe ;co
> > group = 3
> > channel => 1-31
> >
> > zaptel.conf
> > span=1,0,0,cas,hdb3
> > cas=1-31:1101
> > defaultzone=us
> >
> >
> > Thanks.
> > _______________________________________________
> > --Bandwidth and Colocation sponsored by Easynews.com --
> >
> > Asterisk-Users mailing list
> > Asterisk-Users@lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> 
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
> 
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

Jerry Geis

2005-Aug-29 12:51 UTC

head link

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

Sir,

Can you turn off Multipart SDP headers?

That was the problem I had.

jerry

Alvaro Parres

2005-Aug-31 15:27 UTC

head link

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

In witch part... at Nortell or at Asterisk ??

and how to do this ?


On 8/29/05, Jerry Geis <geisj@pagestation.com>
wrote:> 
> Sir,
> 
> Can you turn off Multipart SDP headers?
> 
> That was the problem I had.
> 
> jerry
> 
> 
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com
<http://Easynews.com>--
> 
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050831/086459d0/attachment.htm

Jerry Geis

2005-Aug-31 16:10 UTC

head link

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

Turn of multipart SDP headerson nortel as asterisk does not yet support it.

Jerry

Apparently Analagous Threads

Search for more apparently analagous threads

asterisk users - Aug 2005 - Asterisk and a Meridian Nortell Release 11

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

[Asterisk-Users] Asterisk and a Meridian Nortell Release 11

Apparently Analagous Threads