[asterisk-dev] asterisk-dev Digest, Vol 76, Issue 77
Scott McCrea
Scott.McCrea at MICHIGANCAT.com
Thu Nov 25 12:05:25 CST 2010
Please stop sending. I followed the unsubscribe directions but I still receive.
Scott
Sent from my smartphone.
On Nov 25, 2010, at 1:03 PM, "asterisk-dev-request at lists.digium.com" <asterisk-dev-request at lists.digium.com> wrote:
> Send asterisk-dev mailing list submissions to
> asterisk-dev at lists.digium.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> or, via email, send a message with subject or body 'help' to
> asterisk-dev-request at lists.digium.com
>
> You can reach the person managing the list at
> asterisk-dev-owner at lists.digium.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of asterisk-dev digest..."
>
>
> Today's Topics:
>
> 1. [Asterisk-Dev] Asterisk-1.8.0 compilation error (RAJNIKANT VANZA)
> 2. Re: [Asterisk-Dev] Asterisk-1.8.0 compilation error
> (Stefan Schmidt)
> 3. Generating Re-invite from asterisk (Alok Prasad)
> 4. Re: Libpri - Wrong hangup cause ( should read from B-channel
> but reads from D-channel ) ? (Abhinav Jha)
> 5. AST_DATA_IPADDR is broken (Simon Perreault)
> 6. Re: AST_DATA_IPADDR is broken (Eliel Sarda?ons)
> 7. Re: AST_DATA_IPADDR is broken (Simon Perreault)
> 8. Re: AST_DATA_IPADDR is broken (Eliel Sarda?ons)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 25 Nov 2010 12:51:39 +0530
> From: RAJNIKANT VANZA <rajnivanza at gmail.com>
> Subject: [asterisk-dev] [Asterisk-Dev] Asterisk-1.8.0 compilation
> error
> To: asterisk-dev at lists.digium.com
> Message-ID:
> <AANLkTi=46oz_u7sWGofXyj76AZqkCE76d8Hb+H03uuHr at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Hi all,
>
> I have written cdr_webservice.c module and its work on asterisk-1.6.2.6
> version on production server. but i want to upgrade asterisk-1.6.2.6 version
> to asterisk-1.8.0 version. Given as below asterisk compilation logs:
>
> # make
> [CC] cdr_webservice.c -> cdr_webservice.o
> In file included from
> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/cdr.h:31,
> from cdr_webservice.c:29:
>
> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:233: error:
> field ?AST_DATA_IPADDR? has incomplete type
> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:794: error:
> return type is an incomplete type
> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h: In function
> ?ast_data_retrieve_ipaddr?:
> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:799: warning:
> ?return? with a value, in function returning void
> make[1]: *** [cdr_webservice.o] Error 1
> make: *** [cdr] Error 2
>
> Help me for resolve this compilation errors.
>
> --
> Best Regards,
> Rajnikant Vanza
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20101125/fa3ce4c4/attachment.html
>
> ------------------------------
>
> Message: 2
> Date: Thu, 25 Nov 2010 08:36:46 +0100
> From: Stefan Schmidt <sst at sil.at>
> Subject: Re: [asterisk-dev] [Asterisk-Dev] Asterisk-1.8.0 compilation
> error
> To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Message-ID: <4CEE120E.5010509 at sil.at>
> Content-Type: text/plain; charset=windows-1252
>
> Am 25.11.10 08:21, schrieb RAJNIKANT VANZA:
>> Hi all,
>>
>> I have written cdr_webservice.c module and its work on asterisk-1.6.2.6
>> version on production server. but i want to upgrade asterisk-1.6.2.6 version
>> to asterisk-1.8.0 version. Given as below asterisk compilation logs:
>>
>> # make
>> [CC] cdr_webservice.c -> cdr_webservice.o
>> In file included from
>> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/cdr.h:31,
>> from cdr_webservice.c:29:
>>
>> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:233: error:
>> field ?AST_DATA_IPADDR? has incomplete type
>> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:794: error:
>> return type is an incomplete type
>> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h: In function
>> ?ast_data_retrieve_ipaddr?:
>> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:799: warning:
>> ?return? with a value, in function returning void
>> make[1]: *** [cdr_webservice.o] Error 1
>> make: *** [cdr] Error 2
>>
>> Help me for resolve this compilation errors.
>>
>>
> Hello,
>
> Cause of the IPv6 support of asterisk1.8 the part of ip and host
> adresses has changed a lot so you have to look how these types are now
> defined and can be used from your app.
> Do you know doxygen? (http://www.asterisk.org/doxygen/trunk/index.html)
> Its very easy to go through the code there and atleast see new structs
> and what have changed.
>
>
> best regards
>
> stefan
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 25 Nov 2010 16:12:25 +0530
> From: Alok Prasad <alok.prasad7 at gmail.com>
> Subject: [asterisk-dev] Generating Re-invite from asterisk
> To: asterisk-dev at lists.digium.com
> Message-ID:
> <AANLkTimWRtNVF6K09my4d3_DiP1UpVCBmG9tqge3MMXK at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I trying to implement call waiting feature by placing ongoing call on hold
> and accepting a new incoming call,
> For this i need to send re-invite to remote end.(in addition i dont want to
> play musiconhold file ).
>
> So to send the re-invite i am using AST_CONTROL_HOLD from my channel driver
> on HOOK Flash event
> But i dont see any reinvite being generated by the asterisk.(asterisk
> 1.6.2.4)
>
> I also tried setting various configuration options in sip.conf
> viz:
>
> 1.
> NAT=no
> canreinvite=yes
>
> &
>
> 2.
> NAT=no
> canreinvite=yes
> dtmfmode=info
>
> But none worked.
>
> Suggest how to intimate sip to send re-invite from my channel driver.?
>
>
> Thanks in Advance.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20101125/a8b0283c/attachment-0001.htm
>
> ------------------------------
>
> Message: 4
> Date: Thu, 25 Nov 2010 19:00:32 +0530
> From: Abhinav Jha <virolord at gmail.com>
> Subject: Re: [asterisk-dev] Libpri - Wrong hangup cause ( should read
> from B-channel but reads from D-channel ) ?
> To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Message-ID:
> <AANLkTi=nSXtKYfhStxbj5RxVfQzP9=g+z6Qz9h16irB0 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Thanks Richard,
>
> I think I misunderstood what inband information meant - thanks for
> clarifying.
>
> Abhinav
>
>
>> Am I wrong in thinking that it should connect to the B-channel and
>>> read the hangup cause in this case ?
>>
>> Are you thinking that libpri needs to listen to the B-channel and decode an
>> audio message?
>> The "inband information may now be available" code indicates that the
>> B-channel may contain an audio recording describing what happened that you
>> can listen to.
>>
>> Richard
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>> http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20101125/1684ac29/attachment-0001.htm
>
> ------------------------------
>
> Message: 5
> Date: Thu, 25 Nov 2010 08:41:38 -0500
> From: Simon Perreault <simon.perreault at viagenie.ca>
> Subject: [asterisk-dev] AST_DATA_IPADDR is broken
> To: asterisk-dev at lists.digium.com
> Message-ID: <4CEE6792.9090804 at viagenie.ca>
> Content-Type: text/plain; charset=windows-1252
>
> (Adding Mark Michelson in CC: to get his attention...)
>
> On 2010-11-25 02:21, RAJNIKANT VANZA wrote:
>> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:233: error:
>> field ?AST_DATA_IPADDR? has incomplete type
>
> This is a bug that was introduced by the port to IPv6. Sorry about that.
> I would encourage you to create a new entry in the bug tracker
> (http://issues.asterisk.org).
>
> Basically, we've broken AST_DATA_IPADDR. The breakage is caused by a
> missing #include, so it's easy to fix. But there's a deeper issue:
> AST_DATA_IPADDR can only represent IPv4 addresses. Should it be replaced
> by something that uses ast_sockaddr underneath? From what I can tell,
> AST_DATA_IPADDR is not used within Asterisk itself. This is why this bug
> was not noticed before.
>
> So I see three possibilities:
>
> a. Add the missing #include to make AST_DATA_IPADDR work and move on.
> b. Remove AST_DATA_IPADDR completely.
> c. Replace AST_DATA_IPADDR with AST_DATA_SOCKADDR.
>
> Anyone have an opinion?
>
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
> STUN/TURN server --> http://numb.viagenie.ca
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 25 Nov 2010 11:57:06 -0300
> From: Eliel Sarda?ons <eliels at gmail.com>
> Subject: Re: [asterisk-dev] AST_DATA_IPADDR is broken
> To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Message-ID: <4CEE7942.3070900 at gmail.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> What about having one for each kind of ip address?
>
> AST_DATA_IPADDR
> AST_DATA_IPADDR6
>
> On 11/25/2010 10:41 AM, Simon Perreault wrote:
>> (Adding Mark Michelson in CC: to get his attention...)
>>
>> On 2010-11-25 02:21, RAJNIKANT VANZA wrote:
>>
>>> /usr/src/asterisk-1.8/asterisk-1.8.0/include/asterisk/data.h:233: error:
>>> field ?AST_DATA_IPADDR? has incomplete type
>>>
>> This is a bug that was introduced by the port to IPv6. Sorry about that.
>> I would encourage you to create a new entry in the bug tracker
>> (http://issues.asterisk.org).
>>
>> Basically, we've broken AST_DATA_IPADDR. The breakage is caused by a
>> missing #include, so it's easy to fix. But there's a deeper issue:
>> AST_DATA_IPADDR can only represent IPv4 addresses. Should it be replaced
>> by something that uses ast_sockaddr underneath? From what I can tell,
>> AST_DATA_IPADDR is not used within Asterisk itself. This is why this bug
>> was not noticed before.
>>
>> So I see three possibilities:
>>
>> a. Add the missing #include to make AST_DATA_IPADDR work and move on.
>> b. Remove AST_DATA_IPADDR completely.
>> c. Replace AST_DATA_IPADDR with AST_DATA_SOCKADDR.
>>
>> Anyone have an opinion?
>>
>> Simon
>>
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 25 Nov 2010 10:00:23 -0500
> From: Simon Perreault <simon.perreault at viagenie.ca>
> Subject: Re: [asterisk-dev] AST_DATA_IPADDR is broken
> To: Eliel Sarda?ons <eliels at gmail.com>
> Cc: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Message-ID: <4CEE7A07.1000505 at viagenie.ca>
> Content-Type: text/plain; charset=windows-1252
>
> On 2010-11-25 09:57, Eliel Sarda?ons wrote:
>> What about having one for each kind of ip address?
>>
>> AST_DATA_IPADDR
>> AST_DATA_IPADDR6
>
> What about other kinds of addresses? An ast_sockaddr should be able to
> accomodate any kind of sockaddr.
>
>> From an API point of view, the user shouldn't have to care/know what
> kind of address is contained. An address is an address. Having different
> types creates the opportunity for bugs when you get the type wrong.
> Also, it introduced different code paths that would be very similar.
>
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
> STUN/TURN server --> http://numb.viagenie.ca
>
>
>
> ------------------------------
>
> Message: 8
> Date: Thu, 25 Nov 2010 12:04:25 -0300
> From: Eliel Sarda?ons <eliels at gmail.com>
> Subject: Re: [asterisk-dev] AST_DATA_IPADDR is broken
> To: Simon Perreault <simon.perreault at viagenie.ca>
> Cc: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Message-ID: <4CEE7AF9.40107 at gmail.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Not sure, if you look at the API, the idea is to specify the kind of
> data being stored,
> to make simple enough the information parsing.
>
> But, I also agree with your idea about calling it AST_DATA_SOCKADDR.
>
>
>
> On 11/25/2010 12:00 PM, Simon Perreault wrote:
>> On 2010-11-25 09:57, Eliel Sarda?ons wrote:
>>
>>> What about having one for each kind of ip address?
>>>
>>> AST_DATA_IPADDR
>>> AST_DATA_IPADDR6
>>>
>> What about other kinds of addresses? An ast_sockaddr should be able to
>> accomodate any kind of sockaddr.
>>
>> From an API point of view, the user shouldn't have to care/know what
>> kind of address is contained. An address is an address. Having different
>> types creates the opportunity for bugs when you get the type wrong.
>> Also, it introduced different code paths that would be very similar.
>>
>> Simon
>>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> AstriCon 2010 - October 26-28 Washington, DC
> Put in your talk proposal: http://www.bit.ly/speak-astricon2010
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
> End of asterisk-dev Digest, Vol 76, Issue 77
> ********************************************
More information about the asterisk-dev
mailing list