IncomingCallNotification event

[izmoto]

Hi,

- i'm using sipeksdk_mobile.dll. BTW, i can't seem to be able to
retrieve the latest source; one that supports e.g
"pjsipStackProxy.Instance.ConfigMore.logLevel = 5;"
- i can make an outgoing call but can't get notified of incoming
calls; i suppose i have the wrong version of the mobile sdk but each
time i get the latest from the svn repo, the results are the same.
- just where are the latest sources?

Thanks.

[Georges]

Hello,

Receiving notification for incoming calls seems to be a frequent issue
and I am surprised that we have yet to obtain a clear, concise and
well defined solution, at least as a simple tutorial.
I myself am having troubles with having an incoming call callback
method being called.

Having read the available documentation and studied and reversed
engineered all available source code I am well aware of what I should
do but cannot, for some reason, make it work.
I have tried two approaches and failed at both:

1) Using CCallManager (my favoured approach):

/-------------------------------code sniplet - start
-------------------------------/

// Instance of incoming call
private IStateMachine _incall = null;

[...]

// Registering incoming call callback in the form's
constructor
CallManager.IncomingCallNotification += new
DIncomingCallNotification(CallManager_IncomingCallNotification);

[...]

// Implementation of the incoming call notification callback
method
void CallManager_IncomingCallNotification(int sessionId,
string number, string info)
{
_incall = CallManager.getCall(sessionId);
}

[...]

// Answer call button click
private void answerButton_Click(object sender, EventArgs e)
{
CallManager.onUserAnswer(_incall.Session);
}

/-------------------------------code sniplet - end
-------------------------------/




2) Using the pjsip wrapper:

/-------------------------------code sniplet - start
-------------------------------/
[DllImport("pjsipDll.dll")]
private static extern int onCallIncoming(OnCallIncoming cb);

[...]

// Declare delegate
delegate int OnCallIncoming(OnCallIncoming cb);

// Create delegate
static OnCallIncoming ocInc = new OnCallIncoming
(onCallIncoming);

[...]

// Registering via delegate incoming call callback method in
the form's constructor
onCallIncoming(ocInc);

[...]

// Implement callback method
private static int onCallIncoming(int callId, string sturi)
{
// The incoming call code...
return 0;
}

/-------------------------------code sniplet - end
-------------------------------/


On both cases the callback methods are never called.


SIPek Softphone uses approach number 1 but with a delegate defined and
invoke:

/-------------------------------code sniplet - start
-------------------------------/


delegate void DIncomingCall(int sessionId, string number,
string info);

[...]

void CallManager_IncomingCallNotification(int sessionId,
string number, string info)
{
if (InvokeRequired)
this.BeginInvoke(new DIncomingCall
(this.OnIncomingCall), new object[] { sessionId, number, info});
else
OnIncomingCall(sessionId, number, info);
}

[...]

private void OnIncomingCall(int sessionId, string number,
string info)
{
notifyIcon.ShowBalloonTip(30, "Sipek Softphone",
"Incoming call from " + number + "!", ToolTipIcon.Info);
}


/-------------------------------code sniplet - end
-------------------------------/

This third approach does not function for me either.
What could be the issue? What am I missing? Any suggestions?

Thanks and regards,

- Georges

[Georges]

OK, I persevered on this and got it to work.

I had built my own pjsipDll.dll library by downloading the pjsip
source (pjproject-1.1) and wrapping it with the pjsipDll library
source from the SVN trunk repository.
It turns out that using my own built pjsipDll.dll library was the
issue. I removed it and replaced it by the pre-built one (available at
http://code.google.com/p/sipeksdk/) and everything worked fine.

So, I either didn't properly build the pjsip and/or pjsipDll source or
there was a problem in the soruce code of the pjsipDll trunk at the
time of my checkout (which is why projects should have stable tagged
releases available for checkouts instead of just the trunk)

Anyhow, I hope this helps, for the record at least!

Cheers,

- Georges

[izmoto]

Hello Georges,

- I've tracked down the source of my trouble; CCallManager class.
- when the function 'OnIncomingCall(int sessionId, string number,
string info)' is invoked, the state machine is null so the function
returns.
- what could cause this?

Regards,
izmoto.

On Apr 2, 7:36 pm, Georges <Georges.Labre...@gmail.com> wrote:
> OK, I persevered on this and got it to work.
>
> I had built my own pjsipDll.dll library by downloading the pjsip
> source (pjproject-1.1) and wrapping it with the pjsipDll library
> source from the SVN trunk repository.
> It turns out that using my own built pjsipDll.dll library was the

> issue. I removed it and replaced it by the pre-built one (available athttp://code.google.com/p/sipeksdk/) and everything worked fine.

[izmoto]

Hi sasa,

I've referenced the sipeksdk_mobile project directly and the problem
indicated to you earlier seems to be emanating form the function below
in the callmanager class;

private void OnIncomingCall(int sessionId, string number, string
info)
{

IStateMachine call = getCall(sessionId);

if (call.IsNull) return;

// inform automaton for incoming call
call.State.incomingCall(number, info);

// call callback
if ((IncomingCallNotification != null) &&
(call.DisableStateNotifications == false)) IncomingCallNotification
(sessionId, number, info);
}

- the state machine 'call' is always null [DisableStateNotifications
property is true] so the function returns and the event is never
raised. What could be the cause of this? (state machine is null).

Regards,

[izmoto]

On further inspection of :

private void OnIncomingCall(int sessionId, string number, string
info)
{
IStateMachine call = getCall(sessionId);

if (call.IsNull) return;

// inform automaton for incoming call
call.State.incomingCall(number, info);

// call callback
if ((IncomingCallNotification != null) &&
(call.DisableStateNotifications == false)) IncomingCallNotification
(sessionId, number, info);
}

getCall checks whether the call table (Dictionary<int, IStateMachine>)
contains the statemachine with the incoming session id; it doesn't
find it so it returns a NullStateMachine.

[Gitch]

Hi Everybody!,

I absolutely have the same problem as Georges, no call at all on
callback IncomingCallNotification. I used the CCallManager way by
declaring callback as above :

CallManager.IncomingCallNotification += new
DIncomingCallNotification(CallManager_IncomingCallNotification);

I add corresponding method and I wanted it to answer automaticaly
(last command)

void CallManager_IncomingCallNotification(int sessionId, string
number, string info)
{

Console.WriteLine("\n\n\n\nCallManager_IncomingCallNotification\n\n
\n");
// assign incoming call instance to member variable
incall = CallManager.getCall(sessionId);

CallManager.onUserAnswer(incall.Session);
}

but no calls on this callback.

I'm developping on Linux (Ubuntu) Monodevelop and I launch program in
command lines. In this situation, I can see every SIP message
transmitted and I see INVITE message incoming, but no reaction of my
side (normal, callback is neved called :-) )

Any solution ?

Thanks in advance for your answer !

Gitch

[Georges]

Hello izmoto,

I explicitly set the call state machine when the callback method is
executed, like so:

/---- code sniplet - start -----/

void CallManager_IncomingCallNotification(int sessionId,
string number, string info)
{
if (InvokeRequired)
this.BeginInvoke(new DIncomingCall
(this.OnIncomingCall), new object[] { sessionId, number, info });
else
OnIncomingCall(sessionId, number, info);
}

private void OnIncomingCall(int sessionId, string number,
string info)
{

//explicitly set the state machine
_call = CallManager.getCall(sessionId);
}

/---- code sniplet - end----/


And once it is set, I can use it to answer, like so:


/---- code sniplet - start -----/

private void answerButton_Click(object sender, EventArgs e)
{

CallManager.onUserAnswer(_call.Session);
}

/---- code sniplet - end -----/

Hope this helps, keep everyone posted!

On Apr 3, 9:02 am, izmoto <paul.mun...@gmail.com> wrote:
> log file:
>
>  15:53:58.000 sip_endpoint.c  Module "mod-pjsua-log" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-tsx-layer" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-stateful-util" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-ua" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-100rel" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-pjsua" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-invite" registered
>  15:53:58.000      pasound.c  PortAudio sound library initialized,
> status=0
>  15:53:58.000      pasound.c  PortAudio host api count=2
>  15:53:58.000      pasound.c  Sound device count=4
>  15:53:58.000          pjlib  select() I/O Queue created (003254F4)
>  15:53:58.000   conference.c  Creating conference bridge with 254
> ports
>  15:53:58.000   conference.c  Sound device successfully created for
> port 0
>  15:53:58.000 sip_endpoint.c  Module "mod-evsub" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-presence" registered
>  15:53:58.000        evsub.c  Event pkg "presence" registered by mod-
> presence
>  15:53:58.000 sip_endpoint.c  Module "mod-refer" registered
>  15:53:58.000        evsub.c  Event pkg "refer" registered by mod-
> refer
>  15:53:58.000 sip_endpoint.c  Module "mod-pjsua-pres" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-pjsua-im" registered
>  15:53:58.000 sip_endpoint.c  Module "mod-pjsua-options" registered
>  15:53:58.000   pjsua_core.c  1 SIP worker threads created
>  15:53:58.000   pjsua_core.c  pjsua version 1.0.1 for win32-wince
> initialized
>  15:53:58.000   pjsua_core.c  SIP UDP socket reachable at
> 192.168.1.3:5060
>  15:53:58.000    udp003312D0  SIP UDP transport started, published
> address is 192.168.1.3:5060
>  15:53:58.000    pjsua_acc.c  Account <sip:192.168.1.3:5060> added
> with id 0
>  15:53:58.000    tcplis:5060  SIP TCP listener ready for incoming
> connections at 192.168.1.3:5060
>  15:53:58.000    pjsua_acc.c  Account <sip:
> 192.168.1.3:5060;transport=TCP> added with id 1
>  15:53:58.000  pjsua_media.c  RTP socket reachable at 192.168.1.3:4000
>  15:53:58.000  pjsua_media.c  RTCP socket reachable at
> 192.168.1.3:4001
>  15:53:58.000  pjsua_media.c  RTP socket reachable at 192.168.1.3:4002
>  15:53:58.000  pjsua_media.c  RTCP socket reachable at
> 192.168.1.3:4003
>  15:53:58.000  pjsua_media.c  RTP socket reachable at 192.168.1.3:4004
>  15:53:58.000  pjsua_media.c  RTCP socket reachable at
> 192.168.1.3:4005
>  15:53:58.000  pjsua_media.c  RTP socket reachable at 192.168.1.3:4006
>  15:53:58.000  pjsua_media.c  RTCP socket reachable at
> 192.168.1.3:4007
>  15:53:58.000 sip_endpoint.c  Module "My-Module" registered
>  15:53:58.000    pjsua_acc.c  Account id 0 deleted
>  15:53:58.000    pjsua_acc.c  Account id 1 deleted
>  15:53:59.000 pjsipDll_mobil  dll_registerAccount: reguri='sip:
> 192.168.1.17'
>  15:53:59.000 pjsipDll_mobil  dll_registerAccount:
> id='sip:p...@192.168.1.17'
>  15:53:59.000    pjsua_acc.c  Account sip:p...@192.168.1.17 added with
> id 0
>  15:53:59.000       endpoint  Request msg REGISTER/cseq=14900
> (tdta00369400) created.
>  15:53:59.000    tsx0036A474  Transaction created for Request msg
> REGISTER/cseq=14901 (tdta00369400)
>  15:53:59.000    tsx0036A474  Sending Request msg REGISTER/cseq=14901
> (tdta00369400) in state Null
>  15:53:59.000  sip_resolve.c  Target '192.168.1.17:0' type=Unspecified
> resolved to '192.168.1.17:5060' type=UDP (UDP transport)
>  15:53:59.000   pjsua_core.c  TX 426 bytes Request msg REGISTER/
> cseq=14901 (tdta00369400) to UDP 192.168.1.17:5060:
> REGISTER sip:192.168.1.17 SIP/2.0
> Via: SIP/2.0/UDP
> 192.168.1.3:5060;rport;branch=z9hG4bKPjeAEYoTh9rbrsDvQp95DAmdEedDxWALG1
> Max-Forwards: 70
> From: <sip:p...@192.168.1.17>;tag=ASCcAodNIzMdb8cYG3z82Z9Lic-Bidb2
> To: <sip:p...@192.168.1.17>
> Call-ID: N8cTjtXkfjmnPqHHHUAEAOUlQl2WWtFS
> CSeq: 14901 REGISTER
> User-Agent: Sipek on PJSUA v1.0.1/win32-wince
> Contact: <sip:p...@192.168.1.3:5060>
> Expires: 300
> Content-Length:  0
>
> --end msg--
>  15:53:59.000    tsx0036A474  State changed from Null to Calling,
> event=TX_MSG
>  15:53:59.000    pjsua_acc.c  Registration sent
>  15:54:00.000    tsx0036A474  Retransmit timer event
>  15:54:00.000    tsx0036A474  Retransmiting Request msg REGISTER/
> cseq=14901 (tdta00369400), count=0, restart?=1
>  15:54:00.000   pjsua_core.c  TX 426 bytes Request msg REGISTER/
> cseq=14901 (tdta00369400) to UDP 192.168.1.17:5060:
> REGISTER sip:192.168.1.17 SIP/2.0
> Via: SIP/2.0/UDP
> 192.168.1.3:5060;rport;branch=z9hG4bKPjeAEYoTh9rbrsDvQp95DAmdEedDxWALG1
> Max-Forwards: 70
> From: <sip:p...@192.168.1.17>;tag=ASCcAodNIzMdb8cYG3z82Z9Lic-Bidb2
> To: <sip:p...@192.168.1.17>
> Call-ID: N8cTjtXkfjmnPqHHHUAEAOUlQl2WWtFS
> CSeq: 14901 REGISTER
> User-Agent: Sipek on PJSUA v1.0.1/win32-wince
> Contact: <sip:p...@192.168.1.3:5060>
> Expires: 300
> Content-Length:  0
>
> --end msg--
>  15:54:00.000 sip_endpoint.c  Processing incoming message: Response
> msg 100/REGISTER/cseq=14901 (rdata00331754)
>  15:54:00.000   pjsua_core.c  RX 468 bytes Response msg 100/REGISTER/
> cseq=14901 (rdata00331754) from UDP 192.168.1.17:5060:
> SIP/2.0 100 Trying
> Via: SIP/2.0/UDP
> 192.168.1.3:5060;branch=z9hG4bKPjeAEYoTh9rbrsDvQp95DAmdEedDxWALG1;received=192.168.1.3;rport=5060
> From: <sip:p...@192.168.1.17>;tag=ASCcAodNIzMdb8cYG3z82Z9Lic-Bidb2
> To: <sip:p...@192.168.1.17>
> Call-ID: N8cTjtXkfjmnPqHHHUAEAOUlQl2WWtFS
> CSeq: 14901 REGISTER
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Contact: <sip:p...@192.168.1.17>
> Content-Length: 0
>
> --end msg--
>  15:54:00.000    tsx0036A474  Incoming Response msg 100/REGISTER/
> cseq=14901 (rdata00331754) in state Calling
>  15:54:00.000    tsx0036A474  State changed from Calling to
> Proceeding, event=RX_MSG
>  15:54:00.000 sip_endpoint.c  Processing incoming message: Response
> msg 401/REGISTER/cseq=14901 (rdata00331754)
>  15:54:00.000   pjsua_core.c  RX 531 bytes Response msg 401/REGISTER/
> cseq=14901 (rdata00331754) from UDP 192.168.1.17:5060:
> SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP
> 192.168.1.3:5060;branch=z9hG4bKPjeAEYoTh9rbrsDvQp95DAmdEedDxWALG1;received=192.168.1.3;rport=5060
> From: <sip:p...@192.168.1.17>;tag=ASCcAodNIzMdb8cYG3z82Z9Lic-Bidb2
> To: <sip:p...@192.168.1.17>;tag=as7aee529c
> Call-ID: N8cTjtXkfjmnPqHHHUAEAOUlQl2WWtFS
> CSeq: 14901 REGISTER
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> WWW-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="74a8c8f9"
> Content-Length: 0
>
> --end msg--
>  15:54:00.000    tsx0036A474  Incoming Response msg 401/REGISTER/
> cseq=14901 (rdata00331754) in state Proceeding
>  15:54:00.000    tsx0036A474  State changed from Proceeding to
> Completed, event=RX_MSG
>  15:54:00.000    tsx0036C094  Transaction created for Request msg
> REGISTER/cseq=14902 (tdta00369400)
>  15:54:00.000    tsx0036C094  Sending Request msg REGISTER/cseq=14902
> (tdta00369400) in state Null
>  15:54:00.000  sip_resolve.c  Target '192.168.1.17:0' type=Unspecified
> resolved to '192.168.1.17:5060' type=UDP (UDP transport)
>  15:54:00.000   pjsua_core.c  TX 585 bytes Request msg REGISTER/
> cseq=14902 (tdta00369400) to UDP 192.168.1.17:5060:
> REGISTER sip:192.168.1.17 SIP/2.0
> Via: SIP/2.0/UDP
> 192.168.1.3:5060;rport;branch=z9hG4bKPj8MO4ZrusKdRT1Y1QsoFzXb0Htk9jBWfk
> Max-Forwards: 70
> From: <sip:p...@192.168.1.17>;tag=ASCcAodNIzMdb8cYG3z82Z9Lic-Bidb2
> To: <sip:p...@192.168.1.17>
> Call-ID: N8cTjtXkfjmnPqHHHUAEAOUlQl2WWtFS
> CSeq: 14902 REGISTER
> User-Agent: Sipek on PJSUA v1.0.1/win32-wince
> Contact: <sip:p...@192.168.1.3:5060>
> Expires: 300
> Authorization: Digest username="paul", realm="asterisk",
> nonce="74a8c8f9", uri="sip:192.168.1.17",
> response="777c868a3a3924262f5c40ff0d42d97b", algorithm=MD5
> Content-Length:  0
>
> --end msg--
>  15:54:00.000    tsx0036C094  State changed from Null to Calling,
> event=TX_MSG
>  15:54:00.000 sip_endpoint.c  Processing incoming message: Response
> msg 100/REGISTER/cseq=14902 (rdata00331754)
>  15:54:00.000   pjsua_core.c  RX 468 bytes Response msg 100/REGISTER/
> cseq=14902 (rdata00331754) from UDP 192.168.1.17:5060:
> SIP/2.0 100 Trying
> Via: SIP/2.0/UDP
> 192.168.1.3:5060;branch=z9hG4bKPj8MO4ZrusKdRT1Y1QsoFzXb0Htk9jBWfk;received=192.168.1.3;rport=5060
> From: <sip:p...@192.168.1.17>;tag=ASCcAodNIzMdb8cYG3z82Z9Lic-Bidb2
> To: <sip:p...@192.168.1.17>
> Call-ID: N8cTjtXkfjmnPqHHHUAEAOUlQl2WWtFS
> CSeq: 14902 REGISTER
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Contact: <sip:p...@192.168.1.17>
> Content-Length: 0
>
> --end msg--
>  15:54:00.000    tsx0036C094  Incoming Response msg 100/REGISTER/
> cseq=14902 (rdata00331754) in state Calling
>  15:54:00.000    tsx0036C094  State changed from Calling to
> Proceeding, event=RX_MSG
>  15:54:00.000 sip_endpoint.c  Processing incoming message: Response
> msg 200/REGISTER/cseq=14902 (rdata00331754)
>  15:54:00.000   pjsua_core.c  RX 546 bytes Response msg 200/REGISTER/
> cseq=14902 (rdata00331754) from UDP 192.168.1.17:5060:
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP
> 192.168.1.3:5060;branch=z9hG4bKPj8MO4ZrusKdRT1Y1QsoFzXb0Htk9jBWfk;received=192.168.1.3;rport=5060
> From: <sip:p...@192.168.1.17>;tag=ASCcAodNIzMdb8cYG3z82Z9Lic-Bidb2
> To: <sip:p...@192.168.1.17>;tag=as7aee529c
> Call-ID: N8cTjtXkfjmnPqHHHUAEAOUlQl2WWtFS
> CSeq: 14902 REGISTER
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Expires: 300
> Contact: <sip:p...@192.168.1.3:5060>;expires=300
> Date: Fri, 03 Apr 2009 12:56:29 GMT
> Content-Length: 0
>
> --end msg--
>  15:54:00.000    tsx0036C094  Incoming Response msg 200/REGISTER/
> cseq=14902 (rdata00331754) in state Proceeding
>  15:54:00.000    tsx0036C094  State changed from Proceeding to
> Completed, event=RX_MSG
>  15:54:00.000    pjsua_acc.c  sip:p...@192.168.1.17: registration
> success, status=200 (OK), will re-register in 300 seconds
>  15:54:00.000    pjsua_acc.c  Keep-alive timer started for acc 0,
> ...
>
> read more »

[izmoto]

Hi,

- My diagnosis for the [see thread title] problem in
(sipeksdk_mobile.dll) is as follows:

- the reason seems to be that the onCallStateChanged(int callId,
ESessionState callState) event is not being raised but the
onCallIncoming(int callId, string sturi) event is being raised; NB the
callbacks are in file pjsipCallWrapper.cs.

- for an incoming call, onCallStateChanged(...) event needs to be
raised first so as to set the state machine for the incoming call in
the call manager's table (a dictionary); then the onCallIncoming(...)
event is raised which then tries to retrieve the state machine for the
incoming call from the call manager's table; if it finds the state
machine it goes on to raise the incoming call notification event and
therefore updates the GUI, however, if it does not find the state
machine for the incoming call (as is the case now where it is
returning a NullStateMachine) then incoming call notification event is
never raised.

- i do not know for what reason pjsipdll_mobile.dll does not seem to
work yet pjsipdll.dll works very well.

- Mr. Sasa could you please help us all in this one.

Thank you for your reply,

izmoto.

[izmoto]

Hello Georges,

Your solution works like a charm.

Thanks.

[Sasa Coh]

Hello Guys,

I'm really sorry I couldn't get to you sooner. Now it seems you've solved the mysteries. There's quite a lot of information in the previous posts and now I'm a bit confused. In order to finaly close this issue I need some answers (confirmations):

• Do you use sources or prebuilt libraries (sipeksdk_mobile.dll and pjsip_mobile.dll)?
• Where do you take them from?
• Is the incoming notification problem in the mobile version only?
• What about the wrong order of notifications. Is this reproducible (always)? Btw. it never happens to me, otherwise I...
• Are there any other known problems I should fix?

Thanks for report (and explanations)!

Kind regards,
sasa

[Gitch]

Hi !,

I had the occasion to test 2 scenarios. First is the InstantSoftPhone
example published on SipekSDK website, with pre-build libraries. I had
the Incomingcall code, callback and everything needed. Compiled on
Visual Studio and executed on Windows Environnement, everything works
fine. The application automaticaly answers, exactly what I want for
begining.
Second scenario, based on libraries compiled by myself (libpjsipDll.so
and SipekSDK.dll). On these libraries, audio was disabled (--disable-
sound) because I'm working on Virtual Machine. The same code was
executed and no IncomingCallNotification event was raised. I still do
not know why. Could it be linked with the disable-sound option ? Could
the source code be "wrong" ?

Every help will be lovely accepted :-)

King regards,

Gitch

[izmoto]

Hello Sasa,

I'm very happy you found some time to reply to this post.
Now, I will submit some clarifications to you based on my own
experience using the sipek SDKs both windows-desktop and windows-
mobile versions:-

- Do you use sources or prebuilt libraries (sipeksdk_mobile.dll and
pjsip_mobile.dll)?

I use the sources for both sipeksdk_mobile.dll and
pjsipdll_mobile.dll.

- Where do you take them from?

I build the dlls myself: I get the sources from the SVN repo; sipeksdk
from [http://sipeksdk.googlecode.com/svn/trunk/SipekSdk] and
pjsipdll_mobile from [http://sipeksdk.googlecode.com/svn/trunk/
pjsipdll], for pjsip, i have downloaded pjproject-1.0.1.

- Is the incoming notification problem in the mobile version only?

Yes, the problem is in the mobile version only.

- What about the wrong order of notifications. Is this reproducible

(always)? Btw. it never happens to me, otherwise I...

Yes this is reproducible; i stepped through the source code for
sipeksdk (windows-desktop and windows-mobile versions) ,that is how i
managed to come up with the diagnosis i posted earlier. Here's a
summary: see file pjsipCallWrapper.cs 'Callbacks' region; for an
incoming call, onCallStateChanged(...) needs to be invoked so it can
set up the state machine for the incoming call in CallManager's table,
subsequently onCallIncoming(...) needs to be raised to retrieve the
state machine of the incoming call from CallManager's table, create a
session for the incoming call and notify the GUI. This sequence works
perfectly for the desktop version of the sdk but does not work for the
mobile version of the sdk [ onCallStateChanged(...) is never raised so
the state machine for the incoming call is never set up and when
onCallIncoming(...) is raised and tries to retrieve the state machine
for the incoming call, it never finds it and returns a
NullStateMachine so the GUI is never notified ]. To fix this, i
manually raise onCallStateChanged(...) when i get an incoming call and
all works as expected.

- Are there any other known problems I should fix?

I do not know of any other problems as of this writing; i should be
able to let you know as i continue consuming the gr8 SDKs!

I hope I have submitted my clarifications in a useful way; hopefully
you could get a permanent solution for this problem.

Cheers,
izmoto.

[Gitch]

On 6 avr, 11:20, izmoto <paul.mun...@gmail.com> wrote:
> ...
> izmoto.

Hi!
Just a question, I'm not sure. When you say "onCallStateChanged(...)

needs to be invoked so it can
set up the state machine for the incoming call in CallManager's

table ...", does it mean it's not implemented and it has to be ? Does
this mean code lines are missing ?

When you say "only in mobile version", I'm not agree. I compiled
myself libraries (libpjsipDll.so and SipekDll.dll) in Linux
environnement and no IncomingCallNotification event either. Could it
be the fact I'm using pjsipproject version 1.0.2 ? Could it be the
fact I disabled sound (--disable sound) in compilation ?

We will solve that problem, yes we can ! :-) :-)

Gitch

[Gitch]

I've made a test. I've put some messages in code to see exactly what
code was triggered on an effective incoming call. I've put messages on
there following methods :

pjsipCallWrapper.cs - onCallIncoming
pjsipDll.cpp - on_incoming_call

I've shown params of onCallIncoming (callId, sturi)

Started the application in debug mode, made an incoming call and
here's the result :


15:39:28.946 tcplis:5060 TCP listener 10.192.73.26:5060: got
incoming TCP connection from 10.192.73.27:37985, sock=14
15:39:28.946 tcps0x8584bc4 TCP server transport created
15:39:28.948 pjsua_core.c RX 1475 bytes Request msg INVITE/cseq=1
(rdata0x8584d60) from tcp 10.192.73.27:37985:
INVITE sip:50...@10.192.73.26:5060 SIP/2.0
Record-Route: <sip:10.192.73.27:5060;lr;sipXecs-rs=%2Afrom
%7EZWU3ODEyNGU%60.400_authrules%2Aauth%7E
%211bd2ca55f2ef538ca487176320f8c12b>
Max-Forwards: 16
Contact: <sip:50...@10.192.51.76:19856>
To: "5002"<sip:50...@10.192.73.27>
From: "5000"<sip:50...@10.192.73.27>;tag=ee78124e
Call-Id: YWExYTRiNTIyMGZlZGI1ZDdmMDFlOWJhZDljMTYxZGI.
Cseq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: X-Lite release 1100l stamp 47546
Content-Length: 422
Date: Mon, 06 Apr 2009 13:48:45 GMT
Via: SIP/2.0/TCP 10.192.73.27;branch=z9hG4bK-
sipXecs-237c1d0f0f1c3f6f54a89302c3b64b38fbda
Via: SIP/2.0/TCP 10.192.73.27;branch=z9hG4bK-
sipXecs-237997afdf783f72052cdb1812c393cc107b~09b700fcf2906e8f0095e757063ccd1d
Via: SIP/2.0/UDP 10.192.73.27;branch=z9hG4bK-
sipXecs-2373a11e0483dff24dd260e6a2350189ef5d~9cbc4870653fc2eaea3ebfe2752f8e3e
Via: SIP/2.0/UDP 10.192.51.76:19856;branch=z9hG4bK-d8754z-
cb2a557bb47ceb7c-1---d8754z-;rport=19856

v=0
o=- 6 2 IN IP4 10.192.51.76
s=CounterPath X-Lite 3.0
c=IN IP4 10.192.51.76
t=0 0
m=audio 48830 RTP/AVP 107 119 100 106 0 105 98 8 3 101
a=alt:1 1 : TJM3fXcT IjSyQ7Bk 10.192.51.76 48830
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:119 BV32-FEC/16000
a=rtpmap:100 SPEEX/16000
a=rtpmap:106 SPEEX-FEC/16000
a=rtpmap:105 SPEEX-FEC/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

--end msg--
15:39:28.957 pjsua_media.c Media index 0 selected for call 0
15:39:28.958 pjsua_core.c TX 788 bytes Response msg 100/INVITE/
cseq=1 (tdta0x85a8618) to tcp 10.192.73.27:37985:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.192.73.27;received=10.192.73.27;branch=z9hG4bK-
sipXecs-237c1d0f0f1c3f6f54a89302c3b64b38fbda
Via: SIP/2.0/TCP 10.192.73.27;branch=z9hG4bK-
sipXecs-237997afdf783f72052cdb1812c393cc107b~09b700fcf2906e8f0095e757063ccd1d
Via: SIP/2.0/UDP 10.192.73.27;branch=z9hG4bK-
sipXecs-2373a11e0483dff24dd260e6a2350189ef5d~9cbc4870653fc2eaea3ebfe2752f8e3e
Via: SIP/2.0/UDP 10.192.51.76:19856;rport=19856;branch=z9hG4bK-d8754z-
cb2a557bb47ceb7c-1---d8754z-
Record-Route: <sip:10.192.73.27:5060;lr;sipXecs-rs=*from~ZWU3ODEyNGU
%60.400_authrules*auth~!1bd2ca55f2ef538ca487176320f8c12b>
Call-ID: YWExYTRiNTIyMGZlZGI1ZDdmMDFlOWJhZDljMTYxZGI.
From: "5000" <sip:50...@10.192.73.27>;tag=ee78124e
To: "5002" <sip:50...@10.192.73.27>
CSeq: 1 INVITE
Content-Length: 0


--end msg--
******** pjsipCallWrapper.cs - onCallIncoming
******** pjsipCallWrapper.cs - callId : 0
******** pjsipCallWrapper.cs - sturi : <sip:50...@10.192.51.76:19856>
******** pjsipDll.cpp - on_incoming_call 15:39:36.484 pjsua_core.c
RX 329 bytes Request msg CANCEL/cseq=1 (rdata0x8584d60) from tcp
10.192.73.27:37985:



We see clearly both methods are called. We arrive to the wrapper, we
arrive to SipekSDK code but, and probably like izmoto said, nothing
happens to the application and CallManager_IncomingCallNotification is
neved called.

I tried this just to check if it wasn't a problem on pjsip code, or
version. Sasa, you, the God creator :-), is that normal that the
application callback is neved called ?

Thank you in advance for your time,

Regards

Gitch

[izmoto]

Hi Gitch,

the CallManager (see file callManager.cs) has a dictionary
(Dictionary<int, IStateMachine> _calls) that maintains state machines;
if you review the function below located in file callManager.cs....

private void OnIncomingCall(int sessionId, string number, string
info)
{

IStateMachine call = getCall(sessionId);

if (call.IsNull) return;

// inform automaton for incoming call
call.State.incomingCall(number, info);

// call callback
if ((IncomingCallNotification != null) &&
(call.DisableStateNotifications == false)) IncomingCallNotification
(sessionId, number, info);
}

- you can see that a call is made to function getCall(...) to retrieve
the state machine for the incoming call; if you follow through that
function you will see that it returns a NullStateMachine IIF it does
not find the state machine identified by the sessionId. so by the time
the above function is called it is expected that the state machine for
the incoming call will be already available in the _calls dictionary.
For this to happen, the OnCallStateChanged(...) event in file
pjsipCallWrapper.cs needs to have been raised prior to raising the
onCallIncoming(...) event so that the state machine for the incoming
call can be 'manufactured'. this is where the problem is;
OnCallStateChanged(...) is not called so state machine is not
manufactured and when onCallIncoming(...) is called which in turn
calls the above pasted function, a call to getCall(...) returns a
NullStateMachine and the function breaks so the event is never raised
to the GUI.

The [temporary] solution now [sipeksdk_mobile.dll] is to manually
raise OnCallStateChanged(...) for incoming calls like shown below (see
comment named invoke callback) in file pjsipCallWrapper.cs :-

private static int onCallIncoming(int callId, string sturi)
{

string uri = sturi;
string display = "";
string number = "";

if (null != uri)
{
// get indices
int startNum = uri.IndexOf("<sip:");
int atPos = uri.IndexOf('@');
// search for number
if ((startNum >= 0) && (atPos > startNum))
{
number = uri.Substring(startNum + 5, atPos -
startNum - 5);
}

// extract display name if exists
if (startNum >= 0)
{
display = uri.Remove(startNum, uri.Length -
startNum).Trim();
}
else
{
int semiPos = display.IndexOf(';');
if (semiPos >= 0)
{
display = display.Remove(semiPos,
display.Length - semiPos);
}
else
{
int colPos = display.IndexOf(':');
if (colPos >= 0)
{
display = display.Remove(colPos,
display.Length - colPos);
}
}
}
}

// invoke callback
ICallProxyInterface.BaseCallStateChanged(callId,
ESessionState.SESSION_STATE_INCOMING, ""); // This is a hack, izmoto!
ICallProxyInterface.BaseIncomingCall(callId, number,
display);
return 1;
}

- at least, this works for me now but it is a hack; i hope we could
find a permanent solution.

- i hope you will find the information clear.

cheers,
izmoto.

On Apr 6, 4:52 pm, Gitch <ritchou...@gmail.com> wrote:
> I've made a test. I've put some messages in code to see exactly what
> code was triggered on an effective incoming call. I've put messages on
> there following methods :
>
> pjsipCallWrapper.cs - onCallIncoming
> pjsipDll.cpp - on_incoming_call
>
> I've shown params of onCallIncoming (callId, sturi)
>
> Started the application in debug mode, made an incoming call and
> here's the result :
>
>  15:39:28.946    tcplis:5060  TCP listener 10.192.73.26:5060: got
> incoming TCP connection from 10.192.73.27:37985, sock=14
>  15:39:28.946  tcps0x8584bc4  TCP server transport created
>  15:39:28.948   pjsua_core.c  RX 1475 bytes Request msg INVITE/cseq=1
> (rdata0x8584d60) from tcp 10.192.73.27:37985:

> INVITE sip:5...@10.192.73.26:5060 SIP/2.0

> Record-Route: <sip:10.192.73.27:5060;lr;sipXecs-rs=%2Afrom
> %7EZWU3ODEyNGU%60.400_authrules%2Aauth%7E
> %211bd2ca55f2ef538ca487176320f8c12b>
> Max-Forwards: 16

> Contact: <sip:5...@10.192.51.76:19856>
> To: "5002"<sip:5...@10.192.73.27>
> From: "5000"<sip:5...@10.192.73.27>;tag=ee78124e

> From: "5000" <sip:5...@10.192.73.27>;tag=ee78124e
> To: "5002" <sip:5...@10.192.73.27>

> CSeq: 1 INVITE
> Content-Length:  0
>
> --end msg--
> ******** pjsipCallWrapper.cs - onCallIncoming
> ******** pjsipCallWrapper.cs - callId : 0

> ******** pjsipCallWrapper.cs - sturi : <sip:5...@10.192.51.76:19856>

[Gitch]

Hi !

Thank you for your message. It's really clear for me now :-) The only
thing I wanted to know was if it was a code problem (apparently it
definitely is). I will try your solution tomorrow and I'll keep you in
touch. I hope Sasa's already on the solution :-)

Greatest,

Gitch

[Georges]

Hi Sasa,

- Do you use sources or prebuilt libraries (sipeksdk_mobile.dll and
pjsip_mobile.dll)?

I had the "incoming callback method not being called" issue when
compiling the source of pjsipDll myself.
The problem is eliminated when I used the prebuilt
pjsipDll.dll_v0.3.108 library available here: http://code.google.com/p/sipeksdk/

Like I said, either there is an issue in my building process or in the
source currently available in the trunk.

Thanks and regards,

- Georges

On Apr 3, 6:29 pm, Sasa Coh <sasa...@gmail.com> wrote:
> Hello Guys,
>
> I'm really sorry I couldn't get to you sooner. Now it seems you've solved
> the mysteries. There's quite a lot of information in the previous posts and
> now I'm a bit confused. In order to finaly close this issue I need some
> answers (confirmations):
>

>    - Do you use sources or prebuilt libraries (sipeksdk_mobile.dll and
>    pjsip_mobile.dll)?
>    - Where do you take them from?
>    - Is the incoming notification problem in the mobile version only?
>    - What about the wrong order of notifications. Is this reproducible

>    (always)? Btw. it never happens to me, otherwise I...

>    - Are there any other known problems I should fix?

>
> Thanks for report (and explanations)!
>
> Kind regards,
> sasa
>

[Gitch]

Hi Everybody!

I had the occasion to test izmoto's solution and it does work.
IncomingCallNotification is now trigged in my application and call can
be started.
We agree it's probably not the nicest way to do it, but it does work
and really really thanks to you izmoto.

I'd really like an answer from Sasa about source code problem. Did we
something wrong or is there really a difference between source code
and pre-build library like Georges said and like I begin to believe ?

Greatest,

Gitch

[izmoto]

Hi Gitch!

good to hear the [temporary] solution does work for you as well;
however, i hope Sasa can give us all the way forward.

cheers,
izmoto.

[Sasa Coh]

Hello guys,

thanks a lot to clarify this. I'll take a look and get back to you ASAP. I hope I can test it on a simulator since I don't have a windows mobile device right now.

Kind regards,
sasa

[rahulja...@gmail.com]

Hi,

I was still unable to get the incomming call.

I have made the changes as Paul has mention on his post but still
fails to get the notification.
http://groups.google.com/group/sipek/browse_thread/thread/4f511799d8354a22/70c2a62e60e7c5c2#70c2a62e60e7c5c2
on sipek google group

I have also tested the CAB file given on the link
http://code.google.com/p/sipekmobile/downloads/list

and i have tested it on HTC P3450, this application is able to make
call but it also unable to receive any incoming call.

I have updated my pjsipdll along with sipeksdk

i have used pjsipdll from the link
http://sipeksdk.googlecode.com/svn/trunk/pjsipdll/

and sipeksdk from the link
http://sipeksdk.googlecode.com/svn/trunk/SipekSdk/

and i have used pjproject-1.0.2.zip from the link
http://www.pjsip.org/download.htm

and along with all these i have used Mobile example given on
http://code.google.com/p/sipekapps/source/browse/#svn/trunk/MobileExample

If i am using any thing wrong so please intimate me

Waiting for your reply.

Thanks & Regards,
Rahul

On Apr 8, 9:27 pm, Sasa Coh <sasa...@gmail.com> wrote:
> Hello guys,
>
> thanks a lot to clarify this. I'll take a look and get back to you ASAP. I
> hope I can test it on a simulator since I don't have a windows mobile device
> right now.
>
> Kind regards,
> sasa
>

> > > > To: "5002"<sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>>
> > > > From: "5000"<sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>

> > > > From: "5000" <sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>
> > >;tag=ee78124e
> > > > To: "5002" <sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>>

[Sasa Coh]

Hi,

One more question: Did you test it on the windows mobile emulator or on the "real" device?

FYI: I've reproduced the problem on the windows mobile emulator easily. And that's expected since the emulator has many problems with itself (especially network). Now I'm looking for someone to lend me the real windows mobile device for testing (could take some time).

kind regards,
sasa

[rahulja...@gmail.com]

Hi,

I have tested it on real device i.e HTC P-3450

Thanks,
Rahul

On Apr 15, 3:16 pm, Sasa Coh <sasa...@gmail.com> wrote:
> Hi,
>
> One more question: Did you test it on the windows mobile emulator or on the
> "real" device?
>
> FYI: I've reproduced the problem on the windows mobile emulator easily. And
> that's expected since the emulator has many problems with itself (especially
> network). Now I'm looking for someone to lend me the real windows mobile
> device for testing (could take some time).
>
> kind regards,
> sasa
>

> On Wed, Apr 8, 2009 at 6:27 PM, Sasa Coh <sasa...@gmail.com> wrote:
> > Hello guys,
>
> > thanks a lot to clarify this. I'll take a look and get back to you ASAP. I
> > hope I can test it on a simulator since I don't have a windows mobile device
> > right now.
>
> > Kind regards,
> > sasa
>

> >> > > To: "5002"<sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>>
> >> > > From: "5000"<sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>

> >> > > From: "5000" <sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>
> >> >;tag=ee78124e
> >> > > To: "5002" <sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>>

> >> > > CSeq: 1 INVITE
> >> > > Content-Length:  0
>
> >> > > --end msg--
> >> > > ******** pjsipCallWrapper.cs - onCallIncoming
> >> > > ******** pjsipCallWrapper.cs - callId : 0
> >> > > ******** pjsipCallWrapper.cs - sturi : <sip:5...@10.192.51.76:19856>
> >> > > ******** pjsipDll.cpp - on_incoming_call 15:39:36.484   pjsua_core.c
> >> > > RX 329 bytes Request msg CANCEL/cseq=1 (rdata0x8584d60) from tcp
> >> > > 10.192.73.27:37985:
>
> >> > > We see clearly both methods are called. We arrive to the wrapper, we
> >> > > arrive to SipekSDK code but, and probably like izmoto said, nothing
> >> > > happens to the application and CallManager_IncomingCallNotification is
> >> > > neved called.
>
> >> > > I tried this just to check if it wasn't
>

> ...
>
> read more »

[izmoto]

Hi Sasa,

One more question: Did you test it on the windows mobile emulator or
on the

"real" device? -

- I tested on both; the IncomingCallNotification event was not being
raised in either (before the slight hack), but now it works.

Cheers.
izmoto.

On Apr 15, 1:16 pm, Sasa Coh <sasa...@gmail.com> wrote:
> Hi,
>
> One more question: Did you test it on the windows mobile emulator or on the
> "real" device?
>
> FYI: I've reproduced the problem on the windows mobile emulator easily. And
> that's expected since the emulator has many problems with itself (especially
> network). Now I'm looking for someone to lend me the real windows mobile
> device for testing (could take some time).
>
> kind regards,
> sasa
>

> On Wed, Apr 8, 2009 at 6:27 PM, Sasa Coh <sasa...@gmail.com> wrote:
> > Hello guys,
>
> > thanks a lot to clarify this. I'll take a look and get back to you ASAP. I
> > hope I can test it on a simulator since I don't have a windows mobile device
> > right now.
>
> > Kind regards,
> > sasa
>

> >> > > To: "5002"<sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>>
> >> > > From: "5000"<sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>

> >> > > From: "5000" <sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>
> >> >;tag=ee78124e
> >> > > To: "5002" <sip:5...@10.192.73.27 <sip%3A5...@10.192.73.27>>

> >> > > CSeq: 1 INVITE
> >> > > Content-Length:  0
>
> >> > > --end msg--
> >> > > ******** pjsipCallWrapper.cs - onCallIncoming
> >> > > ******** pjsipCallWrapper.cs - callId : 0
> >> > > ******** pjsipCallWrapper.cs - sturi : <sip:5...@10.192.51.76:19856>
> >> > > ******** pjsipDll.cpp - on_incoming_call 15:39:36.484   pjsua_core.c
> >> > > RX 329 bytes Request msg CANCEL/cseq=1 (rdata0x8584d60) from tcp
> >> > > 10.192.73.27:37985:
>
> >> > > We see clearly both methods are called. We arrive to the wrapper, we
> >> > > arrive to SipekSDK code but, and probably like izmoto said, nothing
> >> > > happens to the application and CallManager_IncomingCallNotification is
> >> > > neved called.
>
> >> > > I tried this just to check if it wasn't
>

> ...
>
> read more »

[rahulja...@gmail.com]

Hi Izmoto,

I have tested it on both emulator as well as on device i.e HTC P3450
even i have made the changes as u have mention above in your post
but i was unable to get any notification

Can u provide me the source code where i have to make changes.

It will be really great to me if u do so

Waiting for your reply

Thanks
Rahul

> ...
>
> read more »

[rahulja...@gmail.com]

Hi,

I am still waiting for the reply.

Please help me out from this serious problem
Your help will be highly appreciable

Thanks

[gokulakrishnan]

Hi ,

 

       R U enable your stun server in registration part ., you are not enable the Stun please enable that one  ,otherwise

give like this..

 

public loginform()

{

InitializeComponent();

_config =

new PhoneConfig(this);

CallManager.StackProxy =

pjsipStackProxy.Instance;

CallManager.Config = Config;

pjsipStackProxy.Instance.Config = Config;

pjsipRegistrar.Instance.Config = Config;

// register event for registration status change

pjsipRegistrar.Instance.AccountStateChanged += new DAccountStateChanged(proxy_AccountStateChanged);

pjsipStackProxy.Instance.ConfigMore.stunServer = "stun.siol.net";

pjsipStackProxy.Instance.initialize();

CallManager.Initialize();

pjsipStackProxy.Instance.MessageWaitingIndication += new DMessageWaitingNotification(Instance_MessageWaitingIndication);

}

 i hope this will help U..

 

regards,

 

gokul.,

[rahulja...@gmail.com]

Hi Sasa,

Finally i got the success in incoming notification.

Thanks for the co-operation

Regards,
Rahul

On May 4, 3:14 pm, rahuljaiswa...@gmail.com wrote:
> Hi Sasa,
>
> I am still waiting your reply for the notification if u find something
> new then please help me.
>
> Any help from u will be highly appreciable.
>
> Thanks
> Rahul

>
> On Apr 22, 4:34 pm, gokulakrishnan <alagudr...@gmail.com> wrote:
>
> > Hi ,
>
> >        R U enable your stun server in registration part ., you are not
> > enable the Stun please enable that one  ,otherwise
> > give like this..
>
> > public loginform()
>
> > {
>
> > InitializeComponent();
>
> > _config = new PhoneConfig(this);
>
> > CallManager.StackProxy = pjsipStackProxy.Instance;
>
> > CallManager.Config = Config;
>
> > pjsipStackProxy.Instance.Config = Config;
>
> > pjsipRegistrar.Instance.Config = Config;
>
> > // register event for registration status change
>
> > pjsipRegistrar.Instance.AccountStateChanged += new DAccountStateChanged
> > (proxy_AccountStateChanged);
>
> > pjsipStackProxy.Instance.ConfigMore.stunServer = "stun.siol.net";
>
> > pjsipStackProxy.Instance.initialize();
>
> > CallManager.Initialize();
>
> > pjsipStackProxy.Instance.MessageWaitingIndication += new
> > DMessageWaitingNotification(Instance_MessageWaitingIndication);
>
> > }
>
> >  i hope this will help U..
>
> > regards,
>
> > gokul.,
>

> ...
>
> read more »

[rahulja...@gmail.com]

Hi Sasa,

I am able to get the incoming call when the device is connected to
internet through GPRS but when i try to connect it with wifi again the
same notification problem arises.

Can u please help me why is this so happens.

Thanks in advance

Regards,
Rahul

> ...
>
> read more »

[tash...@gmail.com]

I try write sipphone using vb.net sipeksdk but i have 2 questions
1) how can i see what extension have incoming call (i have 2 extension)
2) how can i record answered call

Thank you for your answer