Hi,

Thanks for that suggestion.

I tried this, and actually noticed something funny. When trying to listen on some of the calls, the listen in signal was being sent to different SIP extensions, like so below:

> Channel SIP/2709-0000925d was answered.
> Launching ChanSpy(SIP/609,bq) on SIP/2709-0000925d

Asterisk is saying that it is listening on channel '609', when in fact in FOP2, I listened to an extension of '2702' which is totally different. I looked at my FreePBX config, and turns out, the 609 extension is a device that is attached the 2702 user in FREEPBX.

609 is a softphone app extension that I have attached to the 2702 user, so anytime the 2702 extension rings, the 609 does as well on the users BRIA softphone app. Anyways, it looks like FOP2 is sending the listen signal to the BRIA app vs the actual phone extension.

I am going to take off all the 60x devices I have created for the affected extensions, reload FreePBX + FOP2, and check the logs again, I will keep you posted..

Thanks again!

Neil.

Hi,

Thanks for this suggestion.

I tried this by running FOP2 in Run Level 3 on one of my extensions that is affected, and did a search for 'spy' and did not find anything in the capture.log file.

To me, it looks like that Chanspy is not even getting initiated, as I see nothing regarding to 'spy'.

However, I did try listening in on a call on my extensions that I know works, and this is what I got the capture.log:

127.0.0.1       -> Action: Originate
127.0.0.1       -> Channel: SIP/2709
127.0.0.1       -> CallerID: 2709
127.0.0.1       -> Application: ChanSpy
127.0.0.1       -> Data: SIP/2722,bq
127.0.0.1       -> ActionID: fop2spy!SIP/2722
127.0.0.1       -> Async: True

127.0.0.1       <- Response: Success
127.0.0.1       <- ActionID: fop2spy!SIP/2722
127.0.0.1       <- Message: Originate successfully queued
127.0.0.1       <- Server: 0

127.0.0.1       <- Event: RTPReceiverStat
127.0.0.1       <- Privilege: reporting,all
127.0.0.1       <- SSRC: 0
127.0.0.1       <- ReceivedPackets: 0
127.0.0.1       <- LostPackets: 0
127.0.0.1       <- Jitter: 0.0000
127.0.0.1       <- Transit: 0.0000
127.0.0.1       <- RRCount: 0
127.0.0.1       <- Server: 0

So there is definitely a log there for when the call monitoring worked.

My guess is that Chanspy is not being initiated. I read on a couple forums that Chanspy + call recording on extensions can be an issue, but then I realized that even listening on calls that have 'call recording' enabled, work so that can't be the problem?

Any other ideas? Greatly appreciated, thanks!

Neil

Hi Everyone,

I've come across a new issue. The listening in on the extensions works for about 85% of the extensions in my organization. There's very odd behavior occurring, where if I try to listen in on about three extensions, there is no audio coming back to my phone of the call I'm listening in to, it's just dead air.

This happens on the same three extensions every day, but basically about all the other extensions seem to work fine. I've checked / compared configuration on these affected extensions, and cannot find anything different. These three extensions are located locally here in the office, so a ping / speed issue should not be the case, but I guess that is always possible.

A restart of FOP2 plus comparing settings on an extension that does work in accordance to an extension that doesn't work did not help.

Any ideas?

Any help would be appreciated, thanks!

- Neil

Hi Nicolas,

Thanks for the reply.

It's funny, I tried reloading FOP2, via a service fop2 restart, and ever since then, every extension seems to ring back to my phone. I suspect that it maybe just required a restart to re-sync to the server as I had made quite bit of changes from the last fop2 restart, but I will definitely keep that troubleshooting method in mind for next time.

Thanks for your help!

- Neil

Hi,

I've noticed that when using FOP2 on our FreePBX installation to monitor calls, that some of the extensions in the FOP2 admin panel.

Basically, I have about 100 extensions in my organization. About 80% of the extensions you can click on on anytime and hit the "Listen" icon, and the phone will ring and you'd successfully be able to listen to a phone call. However, there are about 7-10 extensions that are not functional when you click on them to listen in on them.

Looking at the real time error logs, the only difference is, when issuing a 'listen' signal from FOP2 to extensions that listen in works on, the asterisk log shows a 'ChanSpy on ext xxxx' message. When hitting 'listen' and one of the affected extensions, I do not see any Asterisk ChanSpy message. Seems like the ChanSpy signal is not being sent. It seems like it is failing before even hitting the ChanSpy aspect of the process.

I have configured FreePBX extension config details between the extensions that work and don't and have not found anything outstanding.

I've tried creating multiple FOP users and different browsers, and all have proved to be unsuccessful.

Any ideas would be much appreciated, if you guys need more information regarding the problem, please let me know.

Thanks again,

Neil.

Hi Neil,

There are some phones that reject calls when the callerid is the same as their own. When fop2 originates a call for doing a dial, listen, whisper, or whatever action, it sets the callerid to your own number.

Perhaps you have this problem, and I think it is a bug in the phone. Why a phone would reject a call if the callerid matches your user/clid ? Perhaps there is a reason that I cannot understand, or perhaps there is some setting in the phone to disable such behavior.

Hi, thanks for the reply, I apologize for the late response.
If this is the case, is there a way I can change the incoming caller ID for the user?

I'm not too sure if that's the issue, it seems odd, because as well the Cisco 7940 phones issue the same callerID when the phone rings from FOP2.

So you think it's definitely a Aastra phone issue?

I do not have any aastra phone to test, but I had some other reports about the issue from some knowledgeable phone users, I do not remember if it were an aastra phone or some other brand. One way to cheat and make it work would be to create a custom context in your asterisk dialplan adding some prefix for your extensions, and then modifying the from-internal context in the buttons configuration file in fop2 to your custom context, and adding the prefix to all the extensions.. I quite complicated fix in configuration to avoid a problem in the phone sip stack (?).

The fop2 button configuration looks something like this

[SIP/100]
type=extension
extension=100
context=from-internal

extension and context are using for originating calls or redirecting calls, so you can modify the autoconfiguration script so it appends some prefix to the extension and points to a different context, so the config should look like

[SIP/100]
type=extension
extension=99100
context=from-internal-badphones

Then, in your extensions_custom.conf file if you use freepbx, create that context

[from-internal-badphones]
exten => _99X,1,Goto(from-internal,${EXTEN:2},1)

And include from-internal-badphones in your from-internal-custom context

So, when originating calls, the clid will be 99100 instead of 100 and perhaps the phone will be happy.

Hi, thank you for this suggestion.

I actually found out what the issue was by looking at the real time call logs.

It turned out, when initiating a 'listen in' or 'whisper' function from FOP2, the signal from FOP2 to the phone was going to the wrong phone extension.

I should have mentioned that the phone I was dealing with had multiple extensions, but I didn't think that would have mattered. Anytime that extension received a signal from FOP2, the signal was going to a different device rather than the device it was attended for.

Simple solution for this, is just to add a second line on to the phone, and create the FOP2 extension as that second extension, and thus will ring the phone when the FOP2 signal is sent out.

Thanks for all your help, a good win that we got it working.

Neil

Hi Neil,

There are some phones that reject calls when the callerid is the same as their own. When fop2 originates a call for doing a dial, listen, whisper, or whatever action, it sets the callerid to your own number.

Perhaps you have this problem, and I think it is a bug in the phone. Why a phone would reject a call if the callerid matches your user/clid ? Perhaps there is a reason that I cannot understand, or perhaps there is some setting in the phone to disable such behavior.

Hi, thanks for the reply, I apologize for the late response.
If this is the case, is there a way I can change the incoming caller ID for the user?

I'm not too sure if that's the issue, it seems odd, because as well the Cisco 7940 phones issue the same callerID when the phone rings from FOP2.

So you think it's definitely a Aastra phone issue?

Hello Everyone,

I am fairly new to the FOP2 module, we just implemented it about a month ago with our PBX in a flash / Asterisk system.

Basically short story short is, I have an Aastra 6757i phone sitting at my desk, and when I log into the FOP2 gui interface to perform functions such as listening + whispering in on calls, my Aastra phone does not ring, and FOP2 does not initiate my phone to perform these functions.

The weird thing is, I also have a Cisco 7940 phone thats upgraded to SIP. If I sign into FOP2 as the extension of the Cisco phone, I am able to perform functions such as listening and whispering in. I've even unplugged my Cisco phone at one my desks, re-placed it with an Aastra 6757i (same extension), and still, when clicking on any of the FOP2 buttons in the GUI, the Aastra phone does not ring.

Is there an option or some configuration within FOP2 that needs to be enabled or configured to get Aastra phones working with FOP2? My Cisco phones all seem to work OK with FOP2.

If any of you can provide any help it would be greatly appreciated.

Thanks,

Neil.