[asterisk-gui] Paging/intercom
Brent Vrieze
bvrieze at cimsoftware.com
Thu Dec 18 13:15:56 CST 2008
OOOOPS, a top post, just following the patter.
I think that sounds good too. I also would not mind this in the Ring
Groups area as I have set some of my ring groups to an alternate ring
tone that I use
header info to trigger.
Josh Thomas wrote:
> Maybe on the settings page for the page we can have an option for
> Alert-info or Call-Info. As this is the case for my phones as well.
>
> Grandstream phones also need:
> *exten => s,2,SIPAddHeader(Call-Info: answer-after=0)
> *
>
>
> On 12/18/08 10:40 AM, "Ron Byer Jr." <ronb at netweave.com> wrote:
>
> The next time I post a query on this list, I will be sure to
> download the latest/greatest version and check it out first.
>
> I posted a note about paging and intercom support a few days ago
> :: I’ve been using an **early** asterisk-gui 2.0 version from, I’d
> say, 2 months ago .
>
> When I received the note back from Pari saying he had made a
> change, I updated and took a look – and found a whole panel
> dedicated to paging/intercom. At that point I felt a bit like a
> horse’s hindquarters. Thanks guys, I should have RTFC’ed before
> bothering the list.
>
>
> That being said. I have another (hopefully better informed)
> question. I have it working fine now, using the paging/intercom
> panel. I had to make one change to the standard macro being
> generated. I recognize that I could make the change in the java
> script that generates the standard macro ,but wonder if it would
> be better done more generally.
>
> The following is the section from extensions.conf. Of the four
> contexts, the first I provided, and the last three were generated.
> In order for this to work properly, I needed to add the
> “@ext-paging” context to the macro-pagingintercom invocation in
> the [page_an_extension] and [pagegroups] contexts
>
> My question is, would it be best for the GUI to prompt the user
> for the Page context (in this case the ext-paging context) – I
> don’t think that the GUI should generate this context, because it
> will need to be meddled with. By asking the user to enter the Page
> context, it will also clue them as to the need for it.
>
> [ext-paging]
> ; below works for snom phones... other phones may need flavor 2
> (following)
> exten => _XXX,1,Set(__SIPADDHEADER=Call-Info: Answer-After=0)
> ;exten = s,n,SIPAddHeader(Call-Info: <sip:${my-ip}>\;answer-after=0)
> exten => _XXX,n,Set(__SIP_URI_OPTIONS=intercom=true)
> exten => _XXX,n,Set(__ALERT_INFO=Ring Answer)
> exten => _XXX,n,Dial(SIP/${EXTEN},20|pN)
>
> [macro-pagingintercom]
> exten = s,1,SIPAddHeader(Alert-Info: ${PAGING_HEADER})
> exten = s,n,Page(${ARG1}|${ARG2})
> exten = s,n,Hangup
>
>
> [page_an_extension]
> exten = _#XXX,1,Macro(pagingintercom|Local/${EXTEN:1*}@ext-paging*|d)
>
> [pagegroups]
> exten =
> 6400,1,Macro(pagingintercom|SIP/100@*ext-paging*&SIP/181@*ext-paging|d*)
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-gui mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-gui
More information about the asterisk-gui
mailing list