Thank you very much for your answer.
I'm trying to solve this problem from last week (I work until the 3am every
night).

I just tried this code: 

        Sip = SipXTapiDotNet.SipxInstance.Create("sip:[EMAIL PROTECTED]", 060,
5060, tlsPort:=-1)
        Sip.Connect(True)
        Sip.Audio.SetInputDevice("Realtek AC97 Audio")
        Sip.Audio.SetOutputDevice("Realtek AC97 Audio")
        Config = SipXTapiDotNet.SipxConfig.Create(Sip)
        Sip.LineCreate()
        Sip.Lines(0).AddCreditial("108", "108", "[EMAIL PROTECTED]")
        Sip.Lines(0).Register()

But nothing changes.
As you can see below, the REGISTER message go without any Authorization
header.
How can I force sipXTapi to send this header to the pbx?

Thanks a lot for your help.

        Andrew




No.     Time        Source                Destination           Protocol
Info
      5 1.999862    192.168.0.10          192.168.0.1           SIP
Request: REGISTER sip:192.168.0.1

Frame 5 (464 bytes on wire, 464 bytes captured)
Ethernet II, Src: 00:02:3f:b7:76:f8, Dst: 00:13:d4:bf:ee:da
Internet Protocol, Src Addr: 192.168.0.10 (192.168.0.10), Dst Addr:
192.168.0.1 (192.168.0.1)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
    Source port: 5060 (5060)
    Destination port: 5060 (5060)
    Length: 430
    Checksum: 0x03ae (correct)
Session Initiation Protocol
    Request-Line: REGISTER sip:192.168.0.1 SIP/2.0
    Message Header
        From: sip:[EMAIL PROTECTED];tag=269c291a
        To: sip:[EMAIL PROTECTED]
        Call-Id: d960a0fc2350c8cbd14eaf9887159884
        Cseq: 1 REGISTER
        Contact: <sip:[EMAIL PROTECTED];LINEID=563c12019a4b>
        Expires: 3600
        Date: Thu, 23 Nov 2006 23:00:19 GMT
        Max-Forwards: 20
        User-Agent: sipX/1.3.0 (WinNT)
        Supported: replaces
        Via: SIP/2.0/UDP 192.168.0.10;branch=z9hG4bK-67be0b99a4e2;rport
        Content-Length: 0

No.     Time        Source                Destination           Protocol
Info
      6 2.078278    192.168.0.1           192.168.0.10          SIP
Status: 401 Unauthorized    (0 bindings)

Frame 6 (411 bytes on wire, 411 bytes captured)
Ethernet II, Src: 00:13:d4:bf:ee:da, Dst: 00:02:3f:b7:76:f8
Internet Protocol, Src Addr: 192.168.0.1 (192.168.0.1), Dst Addr:
192.168.0.10 (192.168.0.10)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
    Source port: 5060 (5060)
    Destination port: 5060 (5060)
    Length: 377
    Checksum: 0xbd75 (correct)
Session Initiation Protocol
    Status-Line: SIP/2.0 401 Unauthorized
    Message Header
        Via: SIP/2.0/UDP 192.168.0.10;branch=z9hG4bK-67be0b99a4e2;rport
        To: sip:[EMAIL PROTECTED]
        From: sip:[EMAIL PROTECTED];tag=269c291a
        Call-ID: d960a0fc2350c8cbd14eaf9887159884
        CSeq: 1 REGISTER
        User-Agent: Axon 1.09
        WWW-Authenticate: Digest
realm="[EMAIL PROTECTED]",nonce="v74859qaq22296w",opaque="",stale=FALSE,algorith
m=MD5
        Content-Length: 0


-----Messaggio originale-----
Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per
conto di Alexander Chemeris
Inviato: giovedì 23 novembre 2006 23.37
A: Andrea Fileccia
Cc: [email protected]
Oggetto: Re: [sipxtapi-dev] Help on sipXtapiDotNet

Hello,

On 11/24/06, Andrea Fileccia <[EMAIL PROTECTED]> wrote:
> I used ethereal to see the packets and I found that sipxtapi after the
> register request, don't reply to 401 unauthorized response with the second
> register request and the authentication string.
You should pass correct realm to AddCredential function to proceed
authentification. In your case realm is '[EMAIL PROTECTED]' - look into
WWW-Authenticate field of 401 message.

-- 
Regards,
Alexander Chemeris.
No.     Time        Source                Destination           Protocol Info
      5 1.999862    192.168.0.10          192.168.0.1           SIP      
Request: REGISTER sip:192.168.0.1

Frame 5 (464 bytes on wire, 464 bytes captured)
Ethernet II, Src: 00:02:3f:b7:76:f8, Dst: 00:13:d4:bf:ee:da
Internet Protocol, Src Addr: 192.168.0.10 (192.168.0.10), Dst Addr: 192.168.0.1 
(192.168.0.1)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
    Source port: 5060 (5060)
    Destination port: 5060 (5060)
    Length: 430
    Checksum: 0x03ae (correct)
Session Initiation Protocol
    Request-Line: REGISTER sip:192.168.0.1 SIP/2.0
    Message Header
        From: sip:[EMAIL PROTECTED];tag=269c291a
        To: sip:[EMAIL PROTECTED]
        Call-Id: d960a0fc2350c8cbd14eaf9887159884
        Cseq: 1 REGISTER
        Contact: <sip:[EMAIL PROTECTED];LINEID=563c12019a4b>
        Expires: 3600
        Date: Thu, 23 Nov 2006 23:00:19 GMT
        Max-Forwards: 20
        User-Agent: sipX/1.3.0 (WinNT)
        Supported: replaces
        Via: SIP/2.0/UDP 192.168.0.10;branch=z9hG4bK-67be0b99a4e2;rport
        Content-Length: 0

No.     Time        Source                Destination           Protocol Info
      6 2.078278    192.168.0.1           192.168.0.10          SIP      
Status: 401 Unauthorized    (0 bindings)

Frame 6 (411 bytes on wire, 411 bytes captured)
Ethernet II, Src: 00:13:d4:bf:ee:da, Dst: 00:02:3f:b7:76:f8
Internet Protocol, Src Addr: 192.168.0.1 (192.168.0.1), Dst Addr: 192.168.0.10 
(192.168.0.10)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
    Source port: 5060 (5060)
    Destination port: 5060 (5060)
    Length: 377
    Checksum: 0xbd75 (correct)
Session Initiation Protocol
    Status-Line: SIP/2.0 401 Unauthorized
    Message Header
        Via: SIP/2.0/UDP 192.168.0.10;branch=z9hG4bK-67be0b99a4e2;rport
        To: sip:[EMAIL PROTECTED]
        From: sip:[EMAIL PROTECTED];tag=269c291a
        Call-ID: d960a0fc2350c8cbd14eaf9887159884
        CSeq: 1 REGISTER
        User-Agent: Axon 1.09
        WWW-Authenticate: Digest realm="[EMAIL 
PROTECTED]",nonce="v74859qaq22296w",opaque="",stale=FALSE,algorithm=MD5
        Content-Length: 0
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to