How to play a "splash-tone" file as soon as posssible in the call sequence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



See pjsua_app.c for example on how to create player and connect to 
conference when call answers. It's all part of the --auto-play option in 
pjsua.

On 10/27/2014 10:35 AM, Brunner, Brian T. wrote:
> I'm puzzled why you need to see broken code in order to tell me 
> correct code?
>
> Given a call_id, how do I tell which conference port to connect to, in 
> order to send a wav file to the caller?  So far I've managed to 
> connect it to my sound hardware, which isn't much progress.
>
> I'm curious which call-back is the earliest point in the call sequence 
> wherein I'm able to tell which conference port to connect my player to 
> (which I mentioned I'd created).
>
> When we're agreed that my broken code is in the correct place (and 
> therefore it is the code that is broken, not its location) lets look 
> at broken code to see what I did wrong in the right place.
>
> Is there an example of this process (I haven't found one yet)?
> ------------------------------------------------------------------------
> *From:* pjsip [pjsip-bounces at lists.pjsip.org] on behalf of Bill 
> Gardner [billg at wavearts.com]
> *Sent:* Friday, October 24, 2014 3:47 PM
> *To:* pjsip at lists.pjsip.org
> *Subject:* Re: [pjsip] How to play a "splash-tone" file as soon as 
> posssible in the call sequence
>
> Creating a player and connecting to the conference should work, 
> perhaps you can share some code?
>
> On 10/24/2014 10:50 AM, Brunner, Brian T. wrote:
>>
>> My attempts (which have been many and unsuccessful) lead me to beg:
>> How can my SoftVoIPPhone pick up the call and play a "splash tone" or 
>> "please leave your message after the tone" file from the hard drive 
>> to the caller?
>>
>> I create a player, and I connect it to the conference, but clearly 
>> not the right way or right time.
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------------------------------------------------------------- 
>>
>>
>> Confidentiality Requirement: This communication, including any 
>> attachment(s), may contain confidential information and is for the 
>> sole use of the intended recipient(s). If you are not the intended 
>> recipient, you are hereby notified that you have received this 
>> communication in error and any unauthorized review, use, disclosure, 
>> dissemination, distribution or copying of it or its contents is 
>> strictly prohibited.  If you have received this communication in 
>> error, please notify the sender immediately by telephone or e-mail 
>> and destroy all copies of this communication and any attachments.
>>
>>
>>
>> _______________________________________________
>> Visit our blog:http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20141027/5253c35c/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux