Open Source Training Seminar FreePBX Paid Support

Ticket #1237 (closed Bugs: worksforme)

Opened 2 years ago

Last modified 1 year ago

Wrong headers for paging Aastra 480

Reported by: Krackd Assigned to: gregmac
Priority: trivial Milestone: 2.3
Component: Paging & Intercom Version: 2.3-branch
Keywords: intercom, paging Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description


Using Aastra 480i CT’s and Trixbox 1.2.3 with an upgraded FreePBX to 2.1.3, the following scenario doesn’t work appropriately:

Extension 104: Already on the phone with an inbound call from the PSTN.

Extension 101: Pages a Page Group that includes Extension 104.

Extension 104: When page comes in, the following happens: Line 2 illuminates (Line 1 was already illuminated) Both calls show as active(not on-hold). Page from Line 2 is combined with the conversation on Line 1, acting like a conference call.


I got the following fix from an engineer at Aastra:

First build the page group with the number of extensions that you want on the web tool for trixbox.

Then go to the extensions_additional.conf file.

It should look like this (if you had 400, 401 in the group):

[ext-paging]
include => ext-paging-custom
exten => PAGE401,1,Set(SIPADDHEADER=Call-Info: answer-after=0)
exten => PAGE401,n,Set(
ALERT_INFO=Ring Answer)
exten => PAGE401,n,Set(SIP_URI_OPTIONS=intercom=true)
exten => PAGE401,n,Dial(SIP/401,5)
exten => PAGE400,1,Set(
SIPADDHEADER=Call-Info: answer-after=0)
exten => PAGE400,n,Set(ALERT_INFO=Ring Answer)
exten => PAGE400,n,Set(
SIP_URI_OPTIONS=intercom=true)
exten => PAGE400,n,Dial(SIP/400,5)
exten => Debug,1,Noop(dialstr is LOCAL/PAGE401@ext-paging&LOCAL/PAGE400@ext-paging)
exten => 300,1,Page(LOCAL/PAGE401@ext-paging&LOCAL/PAGE400@ext-paging)
; end of [ext-paging]

Modify it to look like this for each extension in the list.

Save changes , update trixbox, youre done! It will now page all on the list , but not interrupt them!

[ext-paging]
include => ext-paging-custom
exten => PAGE401,1,Set(ALERT_INFO=info=alert-autoanswer)
exten => PAGE401,n,Dial(SIP/401,5)
exten => PAGE400,1,Set(
ALERT_INFO=info=alert-autoanswer)
exten => PAGE400,n,Dial(SIP/400,5)
exten => Debug,1,Noop(dialstr is LOCAL/PAGE401@ext-paging&LOCAL/PAGE400@ext-paging)
exten => 300,1,Page(LOCAL/PAGE401@ext-paging&LOCAL/PAGE400@ext-paging)
; end of [ext-paging]

Change History

10/30/06 13:33:19 changed by gregmac

  • owner set to gregmac.
  • summary changed from Issue with paging in 2.1.3 to Wrong headers for paging Aastra 480.

Can you clairify this post (as your code is malformed by the wiki markup)? See WikiFormatting#PreformattedText

Right now, paging creates:

exten => PAGE118,n,Set(__SIPADDHEADER=Call-Info: \;answer-after=0)
exten => PAGE118,n,Set(__ALERT_INFO=Ring Answer)
exten => PAGE118,n,Set(__SIP_URI_OPTIONS=intercom=true)

So, are you saying for the aastara's it needs:

exten => PAGE118,n,Set(__SIPADDHEADER=Call-Info: \;answer-after=0)
exten => PAGE118,n,Set(__ALERT_INFO=info: alert-autoanswer)
exten => PAGE118,n,Set(__SIP_URI_OPTIONS=intercom=true)

??

Does it work with the Call-Info and URI_OPTIONS headers?

11/05/06 17:30:05 changed by RobThomas

I tend to think that this is a bug with the aastra, but, I wrote paging with this in mind. When I get around to finishing it off (which we can now tie into the new hook stuff, so the 'device type' can appear on the extension page) I'll put this into paging (or someone else can do it? Feel free 8)

--Rob

11/22/06 02:17:16 changed by vgster

  • priority changed from crash to minor.

12/03/06 11:04:13 changed by p_lindheimer

  • milestone changed from 2.2 to 2.3.

if you make that change across the board, it will break most people's Polycom setups since Polycom is generally programmed to "Ring Answer". Polycom is programmable, so it may be able to take "info: alert-autoanswer" assuming that the Aastra is not programmable (or it should othersise conform to what is already there so that people are not forced to change existing configs).

As has been pointed out - paging just needs to get more 'smart' and figure out what type of phone so that it can send the right stuff headers/alertifno for each type of device.

(follow-up: ↓ 6 ) 01/02/07 10:10:58 changed by vgster

I've never had any problems with 9133i's is this the latest 480i firmware?

(in reply to: ↑ 5 ) 01/02/07 10:51:53 changed by Krackd

This is a known issue with the 480i CT phones only. Aastra is working on a firmware upgrade. No date is known for the release.

Replying to vgster:

I've never had any problems with 9133i's is this the latest 480i firmware?

01/02/07 14:22:45 changed by vgster

If this is a known firmware problem then isn't it better to wait until the firmware is corrected than to add a temporary measure to get around the problem.

01/02/07 14:27:53 changed by gregmac

I agree - if we do anything to change this, it should be to implement DevicesTakeTwo and send proper headers for the device being used. Until then, there's no sense breaking existing functionality with one device to support another.

01/03/07 03:16:16 changed by vgster

  • priority changed from minor to trivial.

01/08/07 11:46:49 changed by

  • milestone deleted.

Milestone 2.3 deleted

01/08/07 12:03:16 changed by vgster

  • milestone set to 2.3.

06/09/07 03:26:57 changed by vgster

  • engine_version changed.
  • svn_rev changed.

is this still the case with the 1.4.2 firmware?

06/20/07 11:46:47 changed by p_lindheimer

  • version changed from 2.1.3 to 2.3-branch.

06/30/07 09:03:38 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to worksforme.

paging/intercom needs a lot of work, but just tested on a 480CT with no changes and it works fine.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads