thr3ads.net - asterisk users - [asterisk-users] Unicall + MFC/R2 line dropped immediately after connect [Jun 2007]

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

Peter Gubis

2007-Jun-14 14:50 UTC

[asterisk-users] Unicall + MFC/R2 line dropped immediately after connect

Hi,

I am trying to set up an E1 line with CAS signaling using available
unicall patches with libmfcr2 implementation. Inbound calls works well,
I am able to get DNIS and ANI from incoming call, but I am still not
able to make an outbound call with our local carrier.

After tweaking of protocolvariant parameter in unicall.conf I was able
to find proper values for inbound and outbound calls, but when outbound
connection is created, it is immediately dropped by opposite side
immediately after connection is made. I think, that we're receiving
billing pulses on the line and they're interpreted as a cleaning request.
I found similar problem in the list before:
http://lists.digium.com/pipermail/asterisk-users/2006-June/156732.html.
Steve suggested to use some kind of timeout to workaround this problem.
I've tried to change many timeouts in libmfcr2 library, without any
success. Can somebody help me to go around this line drop-down problem?

Relevant part of debug log file:

Jun  9 15:19:27 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 6 off [2/      40/Group I       /DNIS]
Jun  9 15:19:27 WARNING[19398]: chan_unicall.c:2644 handle_uc_event: Unicall/21
event Alerting
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0101  [1/     200/Await answer  /DNIS]
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:2644 handle_uc_event: Unicall/21
event Connected
  -- UniCall/21-1 answered UniCall/55-1
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:1411 unicall_answer: Answer Call
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Call control(5)
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Answer call
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 0101  ->      [1/      20/Group B       /Accepted Paid]
    -- Attempting native bridge of UniCall/55-1 and UniCall/21-1
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:1620 unicall_bridge:
unicall_bridge called
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:2644 handle_uc_event: Unicall/55
event Answered
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0001  [1/     400/Answered      /DNIS]
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 R2 prot. err. [1/     400/Answered      /DNIS] cause 32773 -
Unexpected CAS bit pattern
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:2644 handle_uc_event: Unicall/21
event Protocol failure
 -- Unicall/21 protocol error. Cause 32773
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 Channel gains
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 Channel switching
 -- Hungup 'UniCall/21-1'
  == Spawn extension (from_merlin, 87, 1) exited non-zero on
'UniCall/55-1'
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Channel gains
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Channel switching
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Call control(6)
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Drop call(cause=Normal Clearing [16])
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 1101  ->      [1/     400/Answer        /Accepted Paid]
    -- Hungup 'UniCall/55-1'
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0101  [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 R2 prot. err. [1/       1/Idle          /Idle] cause 32773 -
Unexpected CAS bit pattern
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:2644 handle_uc_event: Unicall/21
event Protocol failure
    -- Unicall/21 protocol error. Cause 32773
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 1001  [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]



Many thanks and best regards,
Peter.

Oscar Carriles

2007-Jun-14 15:30 UTC

head link

[asterisk-users] Unicall + MFC/R2 line dropped immediately afterconnect

Hi,

Clearback signal due to billing pulses normally drops calls after a fixed
amount of time 2 minutes or so, Can you stablish an outbound call and after
a while it drops? Or it never succeds?


-----Mensaje original-----
De: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] En nombre de Peter Gubis
Enviado el: jueves, 14 de junio de 2007 18:50
Para: asterisk-users@lists.digium.com
Asunto: [asterisk-users] Unicall + MFC/R2 line dropped immediately
afterconnect

Hi,

I am trying to set up an E1 line with CAS signaling using available unicall
patches with libmfcr2 implementation. Inbound calls works well, I am able to
get DNIS and ANI from incoming call, but I am still not able to make an
outbound call with our local carrier.

After tweaking of protocolvariant parameter in unicall.conf I was able to
find proper values for inbound and outbound calls, but when outbound
connection is created, it is immediately dropped by opposite side
immediately after connection is made. I think, that we're receiving billing
pulses on the line and they're interpreted as a cleaning request.
I found similar problem in the list before:
http://lists.digium.com/pipermail/asterisk-users/2006-June/156732.html.
Steve suggested to use some kind of timeout to workaround this problem.
I've tried to change many timeouts in libmfcr2 library, without any success.
Can somebody help me to go around this line drop-down problem?

Relevant part of debug log file:

Jun  9 15:19:27 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 6 off [2/      40/Group I       /DNIS]
Jun  9 15:19:27 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Alerting
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0101  [1/     200/Await answer  /DNIS]
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Connected
  -- UniCall/21-1 answered UniCall/55-1
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:1411 unicall_answer: Answer
Call Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/55 Call control(5) Jun  9 15:19:41 WARNING[19398]:
chan_unicall.c:627 unicall_report: MFC/R2 UniCall/55 Answer call
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 0101  ->      [1/      20/Group B       /Accepted Paid]
    -- Attempting native bridge of UniCall/55-1 and UniCall/21-1 Jun  9
15:19:41 WARNING[19398]: chan_unicall.c:1620 unicall_bridge: unicall_bridge
called Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/55 event Answered
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0001  [1/     400/Answered      /DNIS]
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 R2 prot. err. [1/     400/Answered      /DNIS] cause 32773 -
Unexpected CAS bit pattern
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Protocol failure
 -- Unicall/21 protocol error. Cause 32773 Jun  9 15:19:42 WARNING[19398]:
chan_unicall.c:627 unicall_report: MFC/R2 UniCall/21 Channel gains Jun  9
15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 Channel switching
 -- Hungup 'UniCall/21-1'
  == Spawn extension (from_merlin, 87, 1) exited non-zero on
'UniCall/55-1'
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Channel gains Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627
unicall_report: MFC/R2 UniCall/55 Channel switching Jun  9 15:19:42
WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/55 Call
control(6) Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627
unicall_report: MFC/R2 UniCall/55 Drop call(cause=Normal Clearing [16])
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 1101  ->      [1/     400/Answer        /Accepted Paid]
    -- Hungup 'UniCall/55-1'
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0101  [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 R2 prot. err. [1/       1/Idle          /Idle] cause 32773 -
Unexpected CAS bit pattern
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Protocol failure
    -- Unicall/21 protocol error. Cause 32773
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 1001  [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]



Many thanks and best regards,
Peter.


_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Oscar Carriles

2007-Jun-14 15:38 UTC

head link

[asterisk-users] Unicall + MFC/R2 line dropped immediately afterconnect

Please read the link from steve from softswitch

He report a problem at Brazilian setups regarding metering pulses.
Try:

mfcr2->clear_back_persistence_check = 300;
In your mfcr2.c

We have a similar patch that seems to work in Argentine variant
At www.eolix.com.ar/descargas/patches/mfcr2
 

-----Mensaje original-----
De: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] En nombre de Peter Gubis
Enviado el: jueves, 14 de junio de 2007 18:50
Para: asterisk-users@lists.digium.com
Asunto: [asterisk-users] Unicall + MFC/R2 line dropped immediately
afterconnect

Hi,

I am trying to set up an E1 line with CAS signaling using available unicall
patches with libmfcr2 implementation. Inbound calls works well, I am able to
get DNIS and ANI from incoming call, but I am still not able to make an
outbound call with our local carrier.

After tweaking of protocolvariant parameter in unicall.conf I was able to
find proper values for inbound and outbound calls, but when outbound
connection is created, it is immediately dropped by opposite side
immediately after connection is made. I think, that we're receiving billing
pulses on the line and they're interpreted as a cleaning request.
I found similar problem in the list before:
http://lists.digium.com/pipermail/asterisk-users/2006-June/156732.html.
Steve suggested to use some kind of timeout to workaround this problem.
I've tried to change many timeouts in libmfcr2 library, without any success.
Can somebody help me to go around this line drop-down problem?

Relevant part of debug log file:

Jun  9 15:19:27 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 6 off [2/      40/Group I       /DNIS]
Jun  9 15:19:27 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Alerting
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0101  [1/     200/Await answer  /DNIS]
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Connected
  -- UniCall/21-1 answered UniCall/55-1
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:1411 unicall_answer: Answer
Call Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report:
MFC/R2 UniCall/55 Call control(5) Jun  9 15:19:41 WARNING[19398]:
chan_unicall.c:627 unicall_report: MFC/R2 UniCall/55 Answer call
Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 0101  ->      [1/      20/Group B       /Accepted Paid]
    -- Attempting native bridge of UniCall/55-1 and UniCall/21-1 Jun  9
15:19:41 WARNING[19398]: chan_unicall.c:1620 unicall_bridge: unicall_bridge
called Jun  9 15:19:41 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/55 event Answered
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0001  [1/     400/Answered      /DNIS]
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 R2 prot. err. [1/     400/Answered      /DNIS] cause 32773 -
Unexpected CAS bit pattern
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Protocol failure
 -- Unicall/21 protocol error. Cause 32773 Jun  9 15:19:42 WARNING[19398]:
chan_unicall.c:627 unicall_report: MFC/R2 UniCall/21 Channel gains Jun  9
15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 Channel switching
 -- Hungup 'UniCall/21-1'
  == Spawn extension (from_merlin, 87, 1) exited non-zero on
'UniCall/55-1'
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 Channel gains Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627
unicall_report: MFC/R2 UniCall/55 Channel switching Jun  9 15:19:42
WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2 UniCall/55 Call
control(6) Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627
unicall_report: MFC/R2 UniCall/55 Drop call(cause=Normal Clearing [16])
Jun  9 15:19:42 WARNING[19398]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/55 1101  ->      [1/     400/Answer        /Accepted Paid]
    -- Hungup 'UniCall/55-1'
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 0101  [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 R2 prot. err. [1/       1/Idle          /Idle] cause 32773 -
Unexpected CAS bit pattern
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:2644 handle_uc_event:
Unicall/21 event Protocol failure
    -- Unicall/21 protocol error. Cause 32773
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21      <- 1001  [1/       1/Idle          /Idle]
Jun  9 15:19:42 WARNING[19390]: chan_unicall.c:627 unicall_report: MFC/R2
UniCall/21 1001  ->      [1/       1/Idle          /Idle]



Many thanks and best regards,
Peter.


_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reasonably Related Threads

Search for more possibly parallel threads

asterisk users - Jun 2007 - Unicall + MFC/R2 line dropped immediately after connect

[asterisk-users] Unicall + MFC/R2 line dropped immediately after connect

[asterisk-users] Unicall + MFC/R2 line dropped immediately afterconnect

[asterisk-users] Unicall + MFC/R2 line dropped immediately afterconnect

Reasonably Related Threads