Chanspy or zapbarge with manager


#1

How is it possible to do a chanspy or a zapbarge with the manager ?

I tried something, but didn’t work very well.

In my dial plan, I have something resuming to :

exten => _*666.,1,ChanSpy(IAX2/${EXTEN:4} exten => _888Z,1,ZapBarge(${EXTEN:3})

With my phone (exten 300), I can do :

  • *666100 : to chanspy IAX2/100
  • 8881 : to zapbarge Zap/1

This works very well if I call directly.

with manager, I do :

Action: originate Channel: Local/300 WaitTime: 30 CallerId: "Web Call" <*666100> Exten: *666100 Context: from-internal Priority: 1

That’s almost work, but on the extension 100, I have on “music on hold” during about 20 seconds.
Logs :

-- Called 300 -- Call accepted by 192.168.0.1 (format gsm) -- Format for call is gsm -- IAX2/300-8 is ringing -- Started music on hold, class 'default', on channel 'IAX2/100-5' -- Playing 'pbx-transfer' (language 'fr')

For zapbarge, I do :

Action: originate Channel: Local/300 WaitTime: 30 CallerId: "Web Call" <8881> Exten: 8881 Context: from-internal Priority: 1

But, doesn’t work at all, it tries to make a transfer…

It seems I can’t do that with “originate”, but is there another solution please ?
Thanks.

As you can see, I use AMP.


#2

What about these:

Action: originate
Channel: Local/300
WaitTime: 30
CallerId: “Web Call” <8881>
Application: ChanSpy
Data: IAX2/100
Async: yes

Action: originate
Channel: Local/300
WaitTime: 30
CallerId: “Web Call” <8881>
Application: ZapBarge
Data: Zap/1
Async: yes

You can try with non-Local channel of your extension like SIP/300 or IAX2/300


#3

You’re right, it’s really more simple…

I just had to use “1” instead of “Zap/1” for ZapBarge.
thank you very much.

But, It doesn’t work each time.
Sometimes (about 1/5), when I do a chanspy, the other side can hear a message saying that transfer is not possible, the first one get MOH during a few seconds, and finaly, I get my chanspy. I suppose it’s an asterisk issue (bug?). I’ll see when I’ll upgrade.

In this way, is it possible to know exactly what to change in a dialplan when we upgrade ? One day, I tried to upgrade from 1.2.4 to 1.2.5, but my AGI at hangup didn’t work anymore. I came back to 1.2.4 immediatly…


#4

Maybe you should add ‘|q’ in the 'Data: ’ fielad
so you use

Data: IAX2/100|q

instead of

Data: IAX2/100

i have problem with chanspy too
i miss the clear voice of the zapbarge
sometime voice from chanspay is too bad


#5

[quote=“meon”]Maybe you should add ‘|q’ in the 'Data: ’ fielad
so you use

Data: IAX2/100|q

instead of

Data: IAX2/100[/quote]

Thanks, but I already use it…

[quote=“meon”]i have problem with chanspy too
i miss the clear voice of the zapbarge
sometime voice from chanspay is too bad[/quote]

I have no problem in this way.


#6

[quote=“novazur”]But, It doesn’t work each time.
Sometimes (about 1/5), when I do a chanspy, the other side can hear a message saying that transfer is not possible, the first one get MOH during a few seconds, and finaly, I get my chanspy. I suppose it’s an asterisk issue (bug?). I’ll see when I’ll upgrade.[/quote]

Upgrade from 1.2.4 to 1.2.7 and I always have the same problem.