ios - Native incoming call is killing my VOIP app's access to audio -


i'm developing voip app allows people make voip calls. whenever user in voip call , receives native call on phone audio of voip app stops working.

i've read 1 must reinitialize audiosession , i'm doing block of code not working. suggestions?

self.callcenter = [[ctcallcenter alloc] init]; [self handlecall];  - (void)handlecall {     avaudiosession *session = [avaudiosession sharedinstance];      self.callcenter.calleventhandler = ^(ctcall *call){      if ([call.callstate isequaltostring: ctcallstateconnected])     {     }     else if ([call.callstate isequaltostring: ctcallstatedialing])     {     }     else if ([call.callstate isequaltostring: ctcallstatedisconnected])     {       nslog(@"call ended");        dispatch_after(dispatch_time(dispatch_time_now, 2 * nsec_per_sec), dispatch_get_main_queue(), ^{          [session setactive:yes error:nil];        });     }     else if ([call.callstate isequaltostring: ctcallstateincoming])     {       nslog(@"call received");     }   }; }

i have worked on voip app sip library using. if using same library, while getting native call if voip call existed, native call terminate voip call audio session. so, while getting native call, make "mute" sip library , after ended native call, "unmute" thats it.

    pjsua_conf_adjust_rx_level(0 /* pjsua_conf_port_id slot*/, 0.0f); //for mute audio      pjsua_conf_adjust_rx_level(0 /* pjsua_conf_port_id slot*/, 1.0f); //for unmute audio.

i hope you.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more