<HTML>
<HEAD>
<TITLE>Re: [asterisk-gui] Paging/intercom</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>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.<BR>
<BR>
Grandstream phones also need:<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:9pt'><B>exten => s,2,SIPAddHeader(Call-Info: answer-after=0)<BR>
</B></SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
<BR>
On 12/18/08 10:40 AM, "Ron Byer Jr." <<a href="ronb@netweave.com">ronb@netweave.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>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. <BR>
<BR>
I posted a note about paging and intercom support a few days ago :: I’ve been using an *<B>early</B>* asterisk-gui 2.0 version from, I’d say, 2 months ago .<BR>
<BR>
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. <BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'> <BR>
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. <BR>
<BR>
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<BR>
<BR>
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. <BR>
<BR>
[ext-paging]<BR>
; below works for snom phones... other phones may need flavor 2 (following)<BR>
exten => _XXX,1,Set(__SIPADDHEADER=Call-Info: Answer-After=0)<BR>
;exten = s,n,SIPAddHeader(Call-Info: <sip:${my-ip}>\;answer-after=0)<BR>
exten => _XXX,n,Set(__SIP_URI_OPTIONS=intercom=true)<BR>
exten => _XXX,n,Set(__ALERT_INFO=Ring Answer)<BR>
exten => _XXX,n,Dial(SIP/${EXTEN},20|pN)<BR>
<BR>
[macro-pagingintercom]<BR>
exten = s,1,SIPAddHeader(Alert-Info: ${PAGING_HEADER})<BR>
exten = s,n,Page(${ARG1}|${ARG2})<BR>
exten = s,n,Hangup<BR>
<BR>
<BR>
[page_an_extension]<BR>
exten = _#XXX,1,Macro(pagingintercom|Local/${EXTEN:1<B>}@ext-paging</B>|d)<BR>
<BR>
[pagegroups]<BR>
exten = 6400,1,Macro(pagingintercom|SIP/100@<B>ext-paging</B>&SIP/181@<B>ext-paging|d</B>)<BR>
<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'><IMG src="cid:3312442202_3319903" > <BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>