Thanks<br><br>
<div><span class="gmail_quote">On 5/9/06, <b class="gmail_sendername"><a href="mailto:asterisk-dev-request@lists.digium.com">asterisk-dev-request@lists.digium.com</a></b> <<a href="mailto:asterisk-dev-request@lists.digium.com">
asterisk-dev-request@lists.digium.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Send asterisk-dev mailing list submissions to<br> <a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com
</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>or, via email, send a message with subject or body 'help' to
<br> <a href="mailto:asterisk-dev-request@lists.digium.com">asterisk-dev-request@lists.digium.com</a><br><br>You can reach the person managing the list at<br> <a href="mailto:asterisk-dev-owner@lists.digium.com">
asterisk-dev-owner@lists.digium.com</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of asterisk-dev digest..."<br><br><br>Today's Topics:<br><br> 1. Re: outbound proxy (Kevin P. Fleming)
<br> 2. Re: outbound proxy (Mikael Magnusson)<br> 3. Re: ISUP over MGCP and/or SIP - A Project and, BOUNTY<br> (Ahmed Naji)<br> 4. Re: Re: ISUP over MGCP and/or SIP - A Project and, BOUNTY (Anton)<br> 5. There is Set, but is there Get? (Peter Beckman)
<br> 6. Hardwareless PCI Card Simulator (Hugo Saporetti Junior)<br> 7. Re: There is Set, but is there Get? (Tilghman Lesher)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1
<br>Date: Tue, 09 May 2006 04:12:03 -0500<br>From: "Kevin P. Fleming" <<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>><br>Subject: Re: [asterisk-dev] outbound proxy<br>To: Asterisk Developers Mailing List <
<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a>><br>Message-ID: <<a href="mailto:44605CE3.1040408@digium.com">44605CE3.1040408@digium.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1
<br><br>Raymond Chen wrote:<br>> I mean is the 2859 patch in the bug list<br>> <a href="http://bugs.digium.com/bug_view_page.php?bug_id=0002859">http://bugs.digium.com/bug_view_page.php?bug_id=0002859</a>, did it ever merge to
<br>> the current 1.2 version or trunk?<br><br>It's not noted in the bug notes, so I don't know that we know the answer<br>to that question.<br><br>Again, describe (on the proper mailing list, not this one) what you are
<br>trying to accomplish and somebody can help you determine whether it is<br>supported or not.<br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 09 May 2006 12:39:13 +0200<br>From: Mikael Magnusson <
<a href="mailto:mikma264@gmail.com">mikma264@gmail.com</a>><br>Subject: Re: [asterisk-dev] outbound proxy<br>To: Asterisk Developers Mailing List <<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com
</a>><br>Message-ID: <<a href="mailto:44607151.3000401@gmail.com">44607151.3000401@gmail.com</a>><br>Content-Type: text/plain; charset=us-ascii; format=flowed<br><br>Raymond Chen wrote:<br>> I mean is the 2859 patch in the bug list
<br>> <a href="http://bugs.digium.com/bug_view_page.php?bug_id=0002859">http://bugs.digium.com/bug_view_page.php?bug_id=0002859</a>, did it ever merge to<br>> the current 1.2 version or trunk?<br>><br>> thanks
<br>><br>> Ray<br>><br><br>"Initial per-peer in there (no docs yet) but not global outbound proxy."<br>(Note: 0017897)<br><br>Commited in r4383.<br><br>Mikael<br><br><br>------------------------------<br>
<br>Message: 3<br>Date: Tue, 09 May 2006 13:21:54 +0100<br>From: Ahmed Naji <<a href="mailto:worldentropy@yahoo.co.uk">worldentropy@yahoo.co.uk</a>><br>Subject: [asterisk-dev] Re: ISUP over MGCP and/or SIP - A Project
<br> and, BOUNTY<br>To: <a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br>Message-ID: <<a href="mailto:44608962.5090807@yahoo.co.uk">44608962.5090807@yahoo.co.uk</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
<br><br><a href="mailto:asterisk-dev-request@lists.digium.com">asterisk-dev-request@lists.digium.com</a> wrote:<br><br><SNIP><br>> Today's Topics:<br>><br>> 1. ISUP over MGCP and/or SIP - A Project and BOUNTY (Ahmed Naji)
<br>> 2. Re: ISUP over MGCP and/or SIP - A Project and BOUNTY<br>> (<a href="mailto:alex@pilosoft.com">alex@pilosoft.com</a>)<br><SNIP><br>><br>><br>> ----------------------------------------------------------------------
<br>><br>> Message: 1<br>> Date: Tue, 09 May 2006 00:37:56 +0100<br>> From: Ahmed Naji <<a href="mailto:worldentropy@yahoo.co.uk">worldentropy@yahoo.co.uk</a>><br>> Subject: [asterisk-dev] ISUP over MGCP and/or SIP - A Project and
<br>> BOUNTY<br>> To: <a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br>> Message-ID: <<a href="mailto:445FD654.2090109@yahoo.co.uk">445FD654.2090109@yahoo.co.uk</a>><br>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
<br>><br>> List,<br>><br>> I need to implement ISUP functionality by utilising Asterisk as a Call<br>> Agent (3PCC in case of SIP), and one ore more Cisco AS5350 or similar as<br>> media gateways.<br>>
<br>> The setup will be such that F-Links will be extracted from the PRI<br>> circuit(s) and handed over to Asterisk for call processing. The<br>> interface would be implemented as a channel (e.g. chan_mgcpisup), much
<br>> the same way as chan_ss7 is implemented. Where implementation is via<br>> SIP, Asterisk would implement 3rd Part Call Control to get the gateway<br>> to talk ISUP, and handle the signalling payload in a SIP-enveloped
<br>> message. The latter (i.e. SIP implementation is preferred).<br>><br>> I am thinking to handover the signalling in an H.225 payload, process it<br>> and hand it over back to the gateway the same way it came:
i.e.<br>> SCCP/MTP3/MTP2 ..etc.<br>><br>> Bounty wise, I am thinking $5,000 for a documented, demostrable version,<br>> with further bounties put on mile-stones.<br>><br>> Thanks,<br>><br>> Ahmed Naji
<br>> 5G Networks LTD<br>><br>><br>> ___________________________________________________________<br>> Switch an email account to Yahoo! Mail, you could win FIFA World Cup<br>> tickets. <a href="http://uk.mail.yahoo.com">
http://uk.mail.yahoo.com</a><br>><br>><br>> ------------------------------<br>><br>> Message: 2<br>> Date: Mon, 8 May 2006 20:06:34 -0400 (EDT)<br>> From: <a href="mailto:alex@pilosoft.com">alex@pilosoft.com
</a><br>> Subject: Re: [asterisk-dev] ISUP over MGCP and/or SIP - A Project and<br>> BOUNTY<br>> To: Asterisk Developers Mailing List <<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com
</a>><br>> Message-ID:<br>> <<a href="mailto:Pine.LNX.4.44.0605082003290.7535-100000@bawx.pilosoft.com">Pine.LNX.4.44.0605082003290.7535-100000@bawx.pilosoft.com</a>><br>> Content-Type: TEXT/PLAIN; charset=US-ASCII
<br>><br>> On Tue, 9 May 2006, Ahmed Naji wrote:<br>><br>>> The setup will be such that F-Links will be extracted from the PRI<br>>> circuit(s) and handed over to Asterisk for call processing. The<br>
>> interface would be implemented as a channel (e.g. chan_mgcpisup), much<br>>> the same way as chan_ss7 is implemented. Where implementation is via<br>>> SIP, Asterisk would implement 3rd Part Call Control to get the gateway
<br>>> to talk ISUP, and handle the signalling payload in a SIP-enveloped<br>>> message. The latter (i.e. SIP implementation is preferred).<br>>><br>>> I am thinking to handover the signalling in an
H.225 payload, process it<br>>> and hand it over back to the gateway the same way it came: i.e.<br>>> SCCP/MTP3/MTP2 ..etc.<br>>><br>>> Bounty wise, I am thinking $5,000 for a documented, demostrable version,
<br>>> with further bounties put on mile-stones.<br>> I think bounty is too low.<br>><br>> Also, possibly, a better idea is to enhance chan_ss7 to support (instead<br>> of zaptel) the SIGTRAN stack (from
<a href="http://openss7.org">openss7.org</a>). SCTP *is* a standardized<br>> protocol after all...<br>><br>Hi Alex,<br><br>Well .. SIGTRAN enhancement to chan_ss7 is indeed a good idea. Reference<br>the bounty, I don't particularly think it's too low, as this is only for
<br>the first mile-stone.<br><br>Thanks,<br><br>Ahmed.<br><br><br>___________________________________________________________<br>Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. <a href="http://uk.mail.yahoo.com">
http://uk.mail.yahoo.com</a><br><br><br>------------------------------<br><br>Message: 4<br>Date: Tue, 9 May 2006 17:28:29 +0500<br>From: Anton <<a href="mailto:anton.vazir@gmail.com">anton.vazir@gmail.com</a>><br>Subject: Re: [asterisk-dev] Re: ISUP over MGCP and/or SIP - A Project
<br> and, BOUNTY<br>To: Asterisk Developers Mailing List <<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a>><br>Message-ID: <<a href="mailto:200605091728.29463.anton.vazir@gmail.com">
200605091728.29463.anton.vazir@gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>asterisk-ss7 list is quite active now. Why not to post/ask<br>it there?<br><br>On 9 May 2006 17:21, Ahmed Naji wrote:
<br>> <a href="mailto:asterisk-dev-request@lists.digium.com">asterisk-dev-request@lists.digium.com</a> wrote:<br>><br>> <SNIP><br>><br>> > Today's Topics:<br>> ><br>> > 1. ISUP over MGCP and/or SIP - A Project and BOUNTY
<br>> > (Ahmed Naji) 2. Re: ISUP over MGCP and/or SIP - A<br>> > Project and BOUNTY (<a href="mailto:alex@pilosoft.com">alex@pilosoft.com</a>)<br>><br>> <SNIP><br>><br>> > -------------------------------------------------------
<br>> >---------------<br>> ><br>> > Message: 1<br>> > Date: Tue, 09 May 2006 00:37:56 +0100<br>> > From: Ahmed Naji <<a href="mailto:worldentropy@yahoo.co.uk">worldentropy@yahoo.co.uk</a>
><br>> > Subject: [asterisk-dev] ISUP over MGCP and/or SIP - A<br>> > Project and BOUNTY<br>> > To: <a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br>> > Message-ID: <
<a href="mailto:445FD654.2090109@yahoo.co.uk">445FD654.2090109@yahoo.co.uk</a>><br>> > Content-Type: text/plain; charset=ISO-8859-1;<br>> > format=flowed<br>> ><br>> > List,<br>> ><br>> > I need to implement ISUP functionality by utilising
<br>> > Asterisk as a Call Agent (3PCC in case of SIP), and one<br>> > ore more Cisco AS5350 or similar as media gateways.<br>> ><br>> > The setup will be such that F-Links will be extracted<br>> > from the PRI circuit(s) and handed over to Asterisk for
<br>> > call processing. The interface would be implemented as<br>> > a channel (e.g. chan_mgcpisup), much the same way as<br>> > chan_ss7 is implemented. Where implementation is via<br>> > SIP, Asterisk would implement 3rd Part Call Control to
<br>> > get the gateway to talk ISUP, and handle the signalling<br>> > payload in a SIP-enveloped message. The latter (i.e.<br>> > SIP implementation is preferred).<br>> ><br>> > I am thinking to handover the signalling in an
H.225<br>> > payload, process it and hand it over back to the<br>> > gateway the same way it came: i.e. SCCP/MTP3/MTP2<br>> > ..etc.<br>> ><br>> > Bounty wise, I am thinking $5,000 for a documented,
<br>> > demostrable version, with further bounties put on<br>> > mile-stones.<br>> ><br>> > Thanks,<br>> ><br>> > Ahmed Naji<br>> > 5G Networks LTD<br>> ><br>> ><br>> > _______________________________________________________
<br>> >____ Switch an email account to Yahoo! Mail, you could<br>> > win FIFA World Cup tickets. <a href="http://uk.mail.yahoo.com">http://uk.mail.yahoo.com</a><br>> ><br>> ><br>> > ------------------------------
<br>> ><br>> > Message: 2<br>> > Date: Mon, 8 May 2006 20:06:34 -0400 (EDT)<br>> > From: <a href="mailto:alex@pilosoft.com">alex@pilosoft.com</a><br>> > Subject: Re: [asterisk-dev] ISUP over MGCP and/or SIP -
<br>> > A Project and BOUNTY<br>> > To: Asterisk Developers Mailing List<br>> > <<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a>> Message-ID:<br>> > <<a href="mailto:Pine.LNX.4.44.0605082003290.7535-100000@bawx.pilosoft">
Pine.LNX.4.44.0605082003290.7535-100000@bawx.pilosoft</a>.<br>> >com> Content-Type: TEXT/PLAIN; charset=US-ASCII<br>> ><br>> > On Tue, 9 May 2006, Ahmed Naji wrote:<br>> >> The setup will be such that F-Links will be extracted
<br>> >> from the PRI circuit(s) and handed over to Asterisk<br>> >> for call processing. The interface would be<br>> >> implemented as a channel (e.g. chan_mgcpisup), much<br>> >> the same way as chan_ss7 is implemented. Where
<br>> >> implementation is via SIP, Asterisk would implement<br>> >> 3rd Part Call Control to get the gateway to talk ISUP,<br>> >> and handle the signalling payload in a SIP-enveloped<br>> >> message. The latter (
i.e. SIP implementation is<br>> >> preferred).<br>> >><br>> >> I am thinking to handover the signalling in an H.225<br>> >> payload, process it and hand it over back to the<br>> >> gateway the same way it came:
i.e. SCCP/MTP3/MTP2<br>> >> ..etc.<br>> >><br>> >> Bounty wise, I am thinking $5,000 for a documented,<br>> >> demostrable version, with further bounties put on<br>> >> mile-stones.
<br>> ><br>> > I think bounty is too low.<br>> ><br>> > Also, possibly, a better idea is to enhance chan_ss7 to<br>> > support (instead of zaptel) the SIGTRAN stack (from<br>> > <a href="http://openss7.org">
openss7.org</a>). SCTP *is* a standardized protocol after<br>> > all...<br>><br>> Hi Alex,<br>><br>> Well .. SIGTRAN enhancement to chan_ss7 is indeed a good<br>> idea. Reference the bounty, I don't particularly think
<br>> it's too low, as this is only for the first mile-stone.<br>><br>> Thanks,<br>><br>> Ahmed.<br>><br>><br>> _________________________________________________________<br>>__ Switch an email account to Yahoo! Mail, you could win
<br>> FIFA World Cup tickets. <a href="http://uk.mail.yahoo.com">http://uk.mail.yahoo.com</a><br>> _______________________________________________<br>> --Bandwidth and Colocation provided by <a href="http://Easynews.com">
Easynews.com</a> --<br>><br>> asterisk-dev mailing list<br>> To UNSUBSCRIBE or update options visit:<br>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev
</a><br><br><br>------------------------------<br><br>Message: 5<br>Date: Tue, 9 May 2006 13:17:52 -0400 (EDT)<br>From: Peter Beckman <<a href="mailto:beckman@purplecow.com">beckman@purplecow.com</a>><br>Subject: [asterisk-dev] There is Set, but is there Get?
<br>To: <a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br>Message-ID: <<a href="mailto:20060509131136.R7824@thermonuclear.org">20060509131136.R7824@thermonuclear.org</a>><br>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
<br><br>In documenting things, I'm realizing that many "Set..." commands were<br>replaced by "Set(varname=value)." However, there doesn't seem to be a<br>"Get" command to match. I assume this is because you can reference
<br>everything as a variable that you set.<br><br>So, effectively, AppendCDRUserField() is equivalent to:<br><br> Set(CDR(userfield)=${CDR(userfield)}value)<br><br>Please correct me if I'm wrong, or confirm that I'm right.
<br><br>Is the prefered usage to use the AppendCDRUserField function, or to use the<br>Set() application? Will AppendCDRUserField be deprecated at some point?<br><br>Beckman<br>---------------------------------------------------------------------------
<br>Peter Beckman Internet Guy<br><a href="mailto:beckman@purplecow.com">beckman@purplecow.com</a> <a href="http://www.purplecow.com/">http://www.purplecow.com/
</a><br>---------------------------------------------------------------------------<br><br><br>------------------------------<br><br>Message: 6<br>Date: Tue, 9 May 2006 14:28:51 -0300<br>From: Hugo Saporetti Junior <<a href="mailto:hugos@inatel.br">
hugos@inatel.br</a>><br>Subject: [asterisk-dev] Hardwareless PCI Card Simulator<br>To: <a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br>Message-ID:<br> <<a href="mailto:18E6815BB347BE43894F742F38D0F8CA0441DDE2@hertz.local.inatel.br">
18E6815BB347BE43894F742F38D0F8CA0441DDE2@hertz.local.inatel.br</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>Hello<br><br><br><br> I would like to know if there's any software to simulate a PCI
<br>WCFXO card. If so, where could I download it? I want to use it with<br>Zaptel/Asterisk. Regards<br><br><br><br>_____<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="http://lists.digium.com/pipermail/asterisk-dev/attachments/20060509/44d457d8/attachment-0001.htm">
http://lists.digium.com/pipermail/asterisk-dev/attachments/20060509/44d457d8/attachment-0001.htm</a><br><br>------------------------------<br><br>Message: 7<br>Date: Tue, 9 May 2006 13:15:20 -0500<br>From: Tilghman Lesher <
<a href="mailto:tilghman@mail.jeffandtilghman.com">tilghman@mail.jeffandtilghman.com</a>><br>Subject: Re: [asterisk-dev] There is Set, but is there Get?<br>To: Asterisk Developers Mailing List <<a href="mailto:asterisk-dev@lists.digium.com">
asterisk-dev@lists.digium.com</a>><br>Message-ID: <<a href="mailto:200605091315.21510.tilghman@mail.jeffandtilghman.com">200605091315.21510.tilghman@mail.jeffandtilghman.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"
<br><br>On Tuesday 09 May 2006 12:17, Peter Beckman wrote:<br>> In documenting things, I'm realizing that many "Set..." commands were<br>> replaced by "Set(varname=value)." However, there doesn't seem to be
<br>> a "Get" command to match. I assume this is because you can reference<br>> everything as a variable that you set.<br><br>That is correct.<br><br>> Is the prefered usage to use the AppendCDRUserField function, or to
<br>> use the Set() application? Will AppendCDRUserField be deprecated at<br>> some point?<br><br>Set, and yes.<br><br>--<br>Tilghman<br><br><br>------------------------------<br><br>_______________________________________________
<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">
http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br><br><br>End of asterisk-dev Digest, Vol 22, Issue 25<br>********************************************<br></blockquote></div><br>