< Previous by Date Date Index Next by Date >
  Thread Index  

Re: [sipxtapi-dev] sipxtapi-dev Digest, Vol 24, Issue 6


Hi All,
 
I am new to sipXtapi. I am trying to establish a sip connection and I did not find any detail sample on the site. Can anone help me in this regards. Or send me a dot net sample.
 
Kashif







From: sipxtapi-dev-request@xxxxxxxxxxxxxxxxxxx
Subject: sipxtapi-dev Digest, Vol 24, Issue 6
To: sipxtapi-dev@xxxxxxxxxxxxxxxxxxx
Date: Wed, 23 Jul 2008 12:00:01 -0500


Send sipxtapi-dev mailing list submissions to
sipxtapi-dev@xxxxxxxxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
https://list.sipfoundry.org/mailman/listinfo/sipxtapi-dev
or, via email, send a message with subject or body 'help' to
sipxtapi-dev-request@xxxxxxxxxxxxxxxxxxx

You can reach the person managing the list at
sipxtapi-dev-owner@xxxxxxxxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of sipxtapi-dev digest..."


--Forwarded Message Attachment--
From: Alexander.Chemeris@xxxxxxxxx
CC: sipxtapi-dev@xxxxxxxxxxxxxxxxxxx
To: joe.huddleston.news@xxxxxxxxx
Date: Wed, 23 Jul 2008 17:01:17 +0400
Subject: Re: [sipxtapi-dev] sipxCallConnect causing CALLSTATE_CAUSE_SMIME_FAILURE

Hi,

This looks very much like you don't have codecs' dlls in the reach of
sipXtapi.dll.
They normally should be in the current directory for sipXtapi to find them.
Try copying them from sipXmediaLib\bin to your current directory and see
whether this helps.

On Tue, Jul 15, 2008 at 12:14 AM, Joe Huddleston
<joe.huddleston.news@xxxxxxxxx> wrote:
> Ok, I got my test application to actually make the connection. Well,
> partially.
>
> I had to add the following call before trying to make the connection:
>
> sipxConfigSetAudioCodecByName(m_sipInfo.instance, "PCMU PCMA
> TELEPHONE-EVENT");
>
>
> Now the call goes through and my X-Lite client rings. However, as soon as
> the call goes through my test app starts throwing this exception:
>
> Unhandled exception at 0x100bcc90 in siptest2.exe: 0xC0000005: Access
> violation reading location 0x00000058.
>
>
> The exception only crops up when I make the sipxCallConnect() call, but
> given the kind of exception it is, I suppose it's possible the problem
> actually lies elsewhere.
>
> The last event I receive at my test app before the failure is
> MEDIA::REMOTE_START::AUDIO.
>
> Any ideas here? I'm comparing my code to the code for sipXezPhone, but as
> it so happens sipXezPhone is also throwing these exceptions.
>
> I found a message board post from someone having a similar problem with the
> PlaceCall application, and it was "fixed" by getting pre-compiled versions
> of PlaceCall and sipxtapi.dll from SipFoundry. However, I can't find
> pre-compiled versions on the site anymore.
>
> Thanks,
>
> Joe
>
>
>
> _______________________________________________
> sipxtapi-dev mailing list
> sipxtapi-dev@xxxxxxxxxxxxxxxxxxx
> List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
>



--
Regards,
Alexander Chemeris.

SIPez LLC.
SIP VoIP, IM and Presence Consulting
http://www.SIPez.com
tel: +1 (617) 273-4000



--Forwarded Message Attachment--
From: aw-sipxtapi-dev@xxxxxxxxxxx
To: sipxtapi-dev@xxxxxxxxxxxxxxxxxxx
Date: Wed, 23 Jul 2008 17:03:10 +0200
Subject: [sipxtapi-dev] Connection hangs on authenticated BYE

I'm using a recent sipXtapi version and get the following problem:

1. I successfully establish a connection.
2. I terminate the connection and the stack sends a BYE with a CSEQ
of e.g. 4711
3. The PBX sends back a status with 401 and indicates that the
request must be authenticated
4. The stack send an authenticated BYE with a new CSEQ of 4712 (using
incremet function of the SipMessage). This seems to complete the
transaction startet in point 2 and starts a new one.
5. The PBX sends back an OK but the stack does not accept it because
the mCSeqMgr of the SipConnection object is still at 4711. It
waits for ever for the response to the BYE.

I don't how and where I should update the current transaction. Can
anybody help?

Regards,
Andreas




--Forwarded Message Attachment--
From: dworley@xxxxxxxxxxx
CC: sipxtapi-dev@xxxxxxxxxxxxxxxxxxx
To: aw-sipxtapi-dev@xxxxxxxxxxx
Date: Wed, 23 Jul 2008 11:35:27 -0400
Subject: Re: [sipxtapi-dev] Connection hangs on authenticated BYE

On Wed, 2008-07-23 at 17:03 +0200, aw-sipxtapi-dev@xxxxxxxxxxx wrote:
> I'm using a recent sipXtapi version and get the following problem:
>
> 1. I successfully establish a connection.
> 2. I terminate the connection and the stack sends a BYE with a CSEQ
> of e.g. 4711
> 3. The PBX sends back a status with 401 and indicates that the
> request must be authenticated
> 4. The stack send an authenticated BYE with a new CSEQ of 4712 (using
> incremet function of the SipMessage). This seems to complete the
> transaction startet in point 2 and starts a new one.
> 5. The PBX sends back an OK but the stack does not accept it because
> the mCSeqMgr of the SipConnection object is still at 4711. It
> waits for ever for the response to the BYE.
>
> I don't how and where I should update the current transaction. Can
> anybody help?

This is a problem in core sipX, so I've forwarded your message to the
sipx-dev mailing list. (You should be getting a copy of that message.)

Dale





Time for vacation? WIN what you need. Enter Now!