Aastra 6757 and FOP2 configuration?

nbainsnbains
in Support
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.

Comments

  • nicolasnicolas
    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.
  • nbainsnbains
    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?
  • nicolasnicolas
    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.
  • nbainsnbains
    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
Sign In or Register to comment.

© Asternic Corp 2024