Re: [asterisk-users] Pickup problem

2014-07-11 Thread Massimo Nuvoli 

Il 11/07/2014 16:45, Rusty Newton ha scritto:

On Wed, Jul 9, 2014 at 3:55 PM, Massimo Nuvoli  wrote:

I found a very strange proble whit two asterisk servers in the same network.

Scenario

Asterisk A with extensions 5XX
Asterisk B with extensions 2XX

There is NO link between the two asterisks.

Call from 501 to 503, 503 ringing
Call from 201 to 203, 203 ringing

The 202 extension comand a pickup (i dont manage this Asterisk, i think with
the Pickup command).
The 202 answer the 501 call and not the 201.



Your description of the issue doesn't make any sense. You seem to be
describing an extension on one Asterisk system using call pickup to
pickup a call on another Asterisk system with no connection between
the two.

There is nowhere near enough information here to tell what is going on.

Can you post an Asterisk full log showing the extension performing a
call pickup? With that information someone may be able to help you.


I found the problem, and i want to share here :-)

The problem was.. that the two asterisks casually take a same ip address 
on a side subnet.


The only phone doing nasty things was on this subnet...

So this is why all things happens.

Really i cant figure this before a deep search of a reason, that was 
impossibile, and IS impossibile.


But... i found how is possibile to take up a phone call ringing on a 
asterisk server... very very very bad.


WOW

Thnks.


--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

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

[asterisk-users] DAHDI-Linux and DAHDI-Tools 2.9.2-rc2 Now Available

2014-07-11 Thread Asterisk Development Team 

The Asterisk Development Team has announced the releases of:
DAHDI-Linux-v2.9.2-rc2
DAHDI-Tools-v2.9.2-rc2
dahdi-linux-complete-2.9.2-rc2+2.9.2-rc2

This release is available for immediate download at:
http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete

This release is mostly stability patches affecting the xpp, wctc4xxp, and 
wcte43xp drivers. It also allows compilation against CentOS 5.5

-rc2 includes fixes for a crash when setting a tone zone on a channel currently playing a tone and spurious signaling bit transitions in wcte13xp and wcte43x drivers when running dahdi_cfg repeatedly.  


Shortlog of dahdi-linux changes since v2.9.1:
Doug Bailey (1):
  wct4xxp: AMI w/CAS errata applies to octal card as well.

Oron Peled (10):
  xpp: fix failed multi-PRI E1<->T1 transition
  xpp: new xbus attribute: dahdi_registration
  xpp: prevent double dahdi un-registration
  xpp: stability fixes - xusb mutex
  xpp: stability -- cleaner xpp_open/close
  xpp: stability -- better debug information
  xpp: stability -- deadlock in waitfor_xpds()
  xpp: stability -- better xbus shut down
  xpp: demote some NOTICE() to DBG()
  xpp: re-organize calls so worker_reset()

Shaun Ruffell (58):
  wcte13xp: Trivial. Remove duplicate pointer to "struct pci_dev".
  wcte13xp: Remove redundant call to synchronize_irq().
  wcte43xp: Close potential unbalanced call to enable_irq().
  dahdi: Define pf_fmt() globally in kernel.h
  wctc4xxp: Trivial. Remove unused timer_list from struct tcb.
  wcte43x: Trivial fix of 'source' in comment.
  wcte43x: Build against 2.6.18 and CentOS 5.5
  wctc4xxp: Make sure we call the pci_enable_mwi() function.
  wctc4xxp: Disable read-line and read-line-multiple PCI commands.
  wctc4xxp: Halt the card when an alert is received.
  wctc4xxp: Remove unused debug ioctl interface.
  wctc4xxp: Replace channel semaphore with channel mutex.
  wctc4xxp: Enable the fatal bus error interrupt.
  wctc4xxp: Always ack a response packet.
  wctc4xxp: Check for shutdown after acquiring the mutex lock.
  wctc4xxp: Do not need locks on the transcoder buffers.
  wctc4xxp: Do not allow duplicated sequence numbers to be received for the 
channels.
  wctc4xxp: Only capture commands once they are on the descriptor ring.
  wctc4xxp: We always want to ack the responses.
  wctc4xxp: Encode the function in the ACK.
  wctc4xxp: All the commands do not need to have completions embedded in 
them.
  wctc4xxp: Cleanup RTP for unopened channels.
  wctc4xxp: Trivial removal of the receiveprep function.
  wctc4xxp: Reduce the number of locks grabbed when sending commands
  wctc4xxp: Make sure csm_encaps commands are sent before RTP.
  wctc4xxp: Use hardware timer for polling and not kernel timer
  wctc4xxp: channel count does not need to be atomic.
  wctc4xxp: Allow the tx and rx descriptor rings to be different sizes
  wctc4xxp: Add debug option to print channel stats to kernel log.
  Add #include  to all files that call kzalloc|kmalloc|kfree.
  pciradio: interruptible_sleep_on_timeout() -> msleep_interruptible()
  wctc4xxp: Speed up channel setup / tear-down.
  wctc4xxp: Handle all known interrupts regardless of mask.
  wctc4xxp: Speed up the rate of polling.
  wctc4xxp: Fix the timestamp calculation for the RTP stream.
  wctc4xxp: Service tx ring in interrupt handler.
  wctc4xxp: Prevent exhausting memory in firmware.
  wctc4xxp: Trivial fix typo that was preventing firmware load.
  wctc4xxp: Reload the firmware if a fatal alert was received.
  wctc4xxp: Constrain RTP payload to 500 bytes.
  wctc4xxp: Trivial removal of unused structure members.
  wctc4xxp: Trivial reduction of indentation level in wctc4xxp_watchdog()
  wctc4xxp: spin_lock() -> spin_lock_irqsave() in wctc4xxp_watchdog()
  dahdi: Protect echocan creation/destruction with mutex.
  dahdi: dahdi_chan.ec_factory can be protected with the mutex.
  wct4xxp: Move bottom half processing from tasklet to workqueue.
  oct612x: Implement the SerializationObject callbacks.
  wct4xxp: Trivial kmalloc + memset -> kzalloc.
  wct4xxp: Remove unused open/close span_ops callbacks.
  tor2: Remove unused open/close callbacks.
  Do not call dahdi_span_ops.open with spinlock held.
  wcte13xp: Do not get stuck in "Not Open" state when DAHDI_CONFIG_NOTOPEN 
is set.
  wcte43x: Change span flags to atomic bitfield.
  wcte43x: Do not get stuck in "Not Open" state when DAHDI_CONFIG_NOTOPEN 
is set.
  wct4xxp: Report rx signalling bit changes after spanconfig.
  dahdi: Stop tones on channel when updating tone zone.
  wcte13xp: Do not reconfigure framer when span lineconfig is not changed.
  wcte43x: Do not

[asterisk-users] Send fax when asterisk is callee legs

2014-07-11 Thread Mojtaba 
Hello,
I have a simple ivr, In one submenu (such as 9), i want to send a fax.
so anybody call with server and then press 9 dtmf . should send a fax.
How can asterisk send fax for current channel? I use SendFax()
function in dialplan but when the application is run, the Asterisk CLI
closed and dont send fax.
I could send fax if asterisk works as caller legs but dont send fax if
asterisk was callee.How can i solve this problems?
With Regards.Mojtaba

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

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

Re: [asterisk-users] revesecharge and asterisk 11

2014-07-11 Thread Richard Mudgett 
On Fri, Jul 11, 2014 at 11:19 AM, Ethy H. Brito 
wrote:

>
> Hi All
>
> I installing a new S.O. (Ubuntu 14.04) and upgrading my asterisk 1.8. to
> Asterisk 11
>
> Asterisk 11 is not in production right now but is scheduled to be soon.
>
> From its logs (Asterisk 11) I read a lots of:
>
> [Jul 11 12:07:45] WARNING[24074][C-] func_channel.c: Unknown or
> unavailable item requested: 'reversecharge'
>
> One of the lines triggering the warning at extensions.conf is:
> exten => s,n,ExecIf($['${CHANNEL(reversecharge)}' =
> '1']?Set(COLLECT_CALL=1))
>
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+Function_CHANNEL
> says
> that nothing has changed from 1.8 to 11.
>
> What am I doing wrong? Why 'reversecharge' is an unavailable item now?
> Some missing library/package?
>

Probably Asterisk was not compiled with libpri configured.  The
reversecharge
option is handled by chan_dahdi when libpri support is available and when
libpri version has the reverse charging feature.

Richard
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

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

[asterisk-users] revesecharge and asterisk 11

2014-07-11 Thread Ethy H. Brito 

Hi All

I installing a new S.O. (Ubuntu 14.04) and upgrading my asterisk 1.8. to
Asterisk 11

Asterisk 11 is not in production right now but is scheduled to be soon.

>From its logs (Asterisk 11) I read a lots of:

[Jul 11 12:07:45] WARNING[24074][C-] func_channel.c: Unknown or
unavailable item requested: 'reversecharge'

One of the lines triggering the warning at extensions.conf is:
exten => s,n,ExecIf($['${CHANNEL(reversecharge)}' = '1']?Set(COLLECT_CALL=1))

https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+Function_CHANNEL says
that nothing has changed from 1.8 to 11.

What am I doing wrong? Why 'reversecharge' is an unavailable item now?
Some missing library/package?

Regards

Ethy

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

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

Re: [asterisk-users] Pickup problem

2014-07-11 Thread Rusty Newton 
On Wed, Jul 9, 2014 at 3:55 PM, Massimo Nuvoli  wrote:
> I found a very strange proble whit two asterisk servers in the same network.
>
> Scenario
>
> Asterisk A with extensions 5XX
> Asterisk B with extensions 2XX
>
> There is NO link between the two asterisks.
>
> Call from 501 to 503, 503 ringing
> Call from 201 to 203, 203 ringing
>
> The 202 extension comand a pickup (i dont manage this Asterisk, i think with
> the Pickup command).
> The 202 answer the 501 call and not the 201.


Your description of the issue doesn't make any sense. You seem to be
describing an extension on one Asterisk system using call pickup to
pickup a call on another Asterisk system with no connection between
the two.

There is nowhere near enough information here to tell what is going on.

Can you post an Asterisk full log showing the extension performing a
call pickup? With that information someone may be able to help you.
https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

-- 
Rusty Newton
Digium, Inc. | Community Support Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
direct: +1 256 428 6200

Check us out at: http://digium.com & http://asterisk.org

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

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

Re: [asterisk-users] CDR(dst) not set in AEL macro

2014-07-11 Thread Rusty Newton 
On Fri, Jul 11, 2014 at 8:38 AM, Rafael dos Santos Saraiva <
rafaels...@gmail.com> wrote:

> Hi
>
> I'm using a macro to dial in a AEL dialplan. The problem is the macro do
> not set the field  CDR(dst), showing only ~~s~~.
>
> I tried various configurations, but without solutions.
>
>
Please don't post new duplicate threads in such a short time span. You
posted this already yesterday. You'll have to be patient and wait for
someone to respond.

Thanks,

-- 

Rusty Newton
Digium, Inc. | Community Support Manager445 Jan Davis Drive NW -
Huntsville, AL 35806 - USdirect: +1 256 428 6200
Check us out at: http://digium.com & http://asterisk.org
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

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

[asterisk-users] CDR(dst) not set in AEL macro

2014-07-11 Thread Rafael dos Santos Saraiva 
Hi

I'm using a macro to dial in a AEL dialplan. The problem is the macro do
not set the field  CDR(dst), showing only ~~s~~.

I tried various configurations, but without solutions.

This is the macro:
macro dial-out(destno,dialstring,route_descr,interno) {
__TRANSFER_CONTEXT=ipbx;
if(${interno} = 1) {
Set(__PICKUPMARK=${destno});
 if(${ODBC_verify_user(${CALLERID(num)})} > 0) {
t = tT;
} else {
 t = t;
}
} else {
t = T;
}
Dial(${dialstring}/${destno},30,${t});
return;
}

Thank's.

Att,
*Rafael dos Santos Saraiva*

-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

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