Jump to content

TAPI problems Windows XP


catprotec

Recommended Posts

Hi @all,

 

I have some problems getting TAPI working on Windows XP

 

I've downloaded the latest TSP-Version, installed it and configured it like in the WIKI.

 

unfortunately no incoming calls are shown on my PC and i cannot make outgoing calls

 

no errors in the event protocol, no log entries on pbxnsip - I'm a bit confused ?!?!?

 

anyone here with similar problems ?

Link to comment
Share on other sites

i think it is registered ok:

...

SUBSCRIBE sip:localhost SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport

From: <sip:101@protec.intern>;tag=12218

To: <sip:101@protec.intern>;tag=989ffb3ab0

Call-ID: fw2d9x2zle2qqz00dp99

CSeq: 5 SUBSCRIBE

Max-Forwards: 70

Contact: <sip:101@127.0.0.1:8806>

Event: x-tapi

Accept: application/x-tapi

Expires: 3600

Content-Length: 0

 

 

[5] 2010/06/10 15:09:01: Last message repeated 2 times

[9] 2010/06/10 15:09:01: Resolve 362: aaaa udp 127.0.0.1 8806

[9] 2010/06/10 15:09:01: Resolve 362: a udp 127.0.0.1 8806

[9] 2010/06/10 15:09:01: Resolve 362: udp 127.0.0.1 8806

[5] 2010/06/10 15:09:01: SIP Tx udp:127.0.0.1:8806:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport=8806

From: <sip:101@protec.intern>;tag=12218

To: <sip:101@protec.intern>;tag=989ffb3ab0

Call-ID: fw2d9x2zle2qqz00dp99

CSeq: 5 SUBSCRIBE

User-Agent: pbxnsip-PBX/4.0.1.3499

WWW-Authenticate: Digest realm="protec.intern",nonce="441f16a4432449db3682cd1d100a41a4",domain="sip:localhost",algorithm=MD5

Content-Length: 0

 

 

[9] 2010/06/10 15:09:02: Resolve 363: aaaa udp 127.0.0.1 8806

[9] 2010/06/10 15:09:02: Resolve 363: a udp 127.0.0.1 8806

[9] 2010/06/10 15:09:02: Resolve 363: udp 127.0.0.1 8806

[5] 2010/06/10 15:09:02: SIP Tx udp:127.0.0.1:8806:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport=8806

From: <sip:101@protec.intern>;tag=12218

To: <sip:101@protec.intern>;tag=989ffb3ab0

Call-ID: fw2d9x2zle2qqz00dp99

CSeq: 5 SUBSCRIBE

User-Agent: pbxnsip-PBX/4.0.1.3499

WWW-Authenticate: Digest realm="protec.intern",nonce="0bef83bf5fe2aa43f363d575d0021a99",domain="sip:localhost",algorithm=MD5

Content-Length: 0

 

 

[5] 2010/06/10 15:09:02: SIP Rx udp:127.0.0.1:8806:

SUBSCRIBE sip:localhost SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport

From: <sip:101@protec.intern>;tag=12218

To: <sip:101@protec.intern>;tag=989ffb3ab0

Call-ID: fw2d9x2zle2qqz00dp99

CSeq: 6 SUBSCRIBE

Max-Forwards: 70

Contact: <sip:101@127.0.0.1:8806>

Event: x-tapi

Accept: application/x-tapi

Authorization: Digest realm="protec.intern",nonce="441f16a4432449db3682cd1d100a41a4",response="7c36bc3e056d768242ab1a1e820f07cf",username="101",uri="sip:localhost",algorithm=MD5

Expires: 3600

Content-Length: 0

...

 

and in the account under registration:

 

x-tapi 101 <sip:101@127.0.0.1:8806> (udp:127.0.0.1:8806) 135 check-sync

 

but if i try to call with dialer nothing is done, nothing is shown in the log of the pbx

 

if i try to call from outlook it says "no free line signal is found" even if i try to reach an internal account

Link to comment
Share on other sites

Maybe try Outlook first. The way the applications use TAPI might differ. If Outlook does not work, then we have a problem. Also, only outbound calls are supported with TAPI. Inbound calls were supposed to come later, but then CSTA entered the scene as a replacement technology.

Link to comment
Share on other sites

i tried from outlook:

 

5] 2010/06/10 16:43:33: SIP Rx udp:127.0.0.1:8806:

NOTIFY sip:localhost SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-8r6k1775xrgsquwzu79w;rport

From: <sip:101@protec.intern>;tag=12218

To: <sip:101@protec.intern>

Call-ID: fw2d9x2zle2qqz00dp99

CSeq: 20 NOTIFY

Max-Forwards: 70

Contact: <sip:101@127.0.0.1:8806>

Event: x-tapi

Content-Type: application/x-tapi

Content-Length: 50

 

Action: MakeCall

Line: 1

Call: 3

Address: 200

 

[5] 2010/06/10 16:43:33: SIP Tr udp:127.0.0.1:8806:

SIP/2.0 404 Not Available

Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-8r6k1775xrgsquwzu79w;rport=8806

From: <sip:101@protec.intern>;tag=12218

To: <sip:101@protec.intern>

Call-ID: fw2d9x2zle2qqz00dp99

CSeq: 20 NOTIFY

Content-Length: 0

 

 

[9] 2010/06/10 16:43:33: Message repetition, packet dropped

[5] 2010/06/10 16:43:50: SIP Rx udp:192.168.10.1:19828:

OPTIONS sip:192.168.10.60 SIP/2.0

Via: SIP/2.0/UDP 192.168.10.1:19828;branch=z9hG4bK-c47cd7cc-a0444733

From: <sip:192.168.10.60>;tag=-168875010--910284630

To: <sip:192.168.10.60>

Call-ID: 3310150421@00a05711fc12

CSeq: 1 OPTIONS

Max-Forwards: 70

Accept: application/sdp

Contact: <sip:192.168.10.1:19828>

Content-Length: 0

 

 

[9] 2010/06/10 16:43:50: Resolve 767: aaaa udp 192.168.10.1 19828

[9] 2010/06/10 16:43:50: Resolve 767: a udp 192.168.10.1 19828

[9] 2010/06/10 16:43:50: Resolve 767: udp 192.168.10.1 19828

[5] 2010/06/10 16:43:50: SIP Tx udp:192.168.10.1:19828:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.10.1:19828;branch=z9hG4bK-c47cd7cc-a0444733

From: <sip:192.168.10.60>;tag=-168875010--910284630

To: <sip:192.168.10.60>;tag=8d205e7c49

Call-ID: 3310150421@00a05711fc12

CSeq: 1 OPTIONS

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Content-Length: 0

 

 

[5] 2010/06/10 16:43:50: SIP Rx udp:192.168.10.1:31464:

OPTIONS sip:192.168.10.60 SIP/2.0

Via: SIP/2.0/UDP 192.168.10.1:31464;branch=z9hG4bK-23a0cfdf-8bb4a1be

From: <sip:192.168.10.60>;tag=973706721-1854632180

To: <sip:192.168.10.60>

Call-ID: 2401170090@00a05711fc12

CSeq: 1 OPTIONS

Max-Forwards: 70

Accept: application/sdp

Contact: <sip:192.168.10.1:31464>

Content-Length: 0

 

 

[9] 2010/06/10 16:43:50: Resolve 768: aaaa udp 192.168.10.1 31464

[9] 2010/06/10 16:43:50: Resolve 768: a udp 192.168.10.1 31464

[9] 2010/06/10 16:43:50: Resolve 768: udp 192.168.10.1 31464

[5] 2010/06/10 16:43:50: SIP Tx udp:192.168.10.1:31464:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.10.1:31464;branch=z9hG4bK-23a0cfdf-8bb4a1be

From: <sip:192.168.10.60>;tag=973706721-1854632180

To: <sip:192.168.10.60>;tag=884a622e58

Call-ID: 2401170090@00a05711fc12

CSeq: 1 OPTIONS

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Content-Length: 0

 

 

[5] 2010/06/10 16:43:50: SIP Rx udp:192.168.10.1:9680:

OPTIONS sip:192.168.10.60 SIP/2.0

Via: SIP/2.0/UDP 192.168.10.1:9680;branch=z9hG4bK-aca7df57-d61f5b55

From: <sip:192.168.10.60>;tag=-348868801-1214041537

To: <sip:192.168.10.60>

Call-ID: 1200585045@00a05711fc12

CSeq: 1 OPTIONS

Max-Forwards: 70

Accept: application/sdp

Contact: <sip:192.168.10.1:9680>

Content-Length: 0

 

 

[9] 2010/06/10 16:43:50: Resolve 769: aaaa udp 192.168.10.1 9680

[9] 2010/06/10 16:43:50: Resolve 769: a udp 192.168.10.1 9680

[9] 2010/06/10 16:43:50: Resolve 769: udp 192.168.10.1 9680

[5] 2010/06/10 16:43:50: SIP Tx udp:192.168.10.1:9680:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 192.168.10.1:9680;branch=z9hG4bK-aca7df57-d61f5b55

From: <sip:192.168.10.60>;tag=-348868801-1214041537

To: <sip:192.168.10.60>;tag=e13c4192e7

Call-ID: 1200585045@00a05711fc12

CSeq: 1 OPTIONS

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Content-Length: 0

 

 

is it a problem if the PBX is running on my machine and the TSP also registers from my machine and tries to start a call ?

Link to comment
Share on other sites

  • 2 weeks later...

ok - i started the next tests

 

setup a virtual machine with XP and outlook - Firewall is turned completely OFF

 

No Registration possible

 

setup a virtual machine with WIN7 and outlook - firewall completely turned off - IPv6 turned off

 

No Registration possible

 

I don't know how to solve this ?!?

 

I've always use the setting from the WIKI how to setup the TSP

 

means user 101, pass 101, domain localhost ( or sth. else ) PBX-Adress 192.168.10.14

 

no Firewall is active in our internal test network, nothing blocks the communication between the Client and the PBX

Link to comment
Share on other sites

Okay, personal firewall is off. That means there must be a packet going out of the computer (even if it is virtual). You should be able to capture the traffic with Wireshark, the TSP sends regular SIP traffic out. You must definitevely see SUBSCRIBE packets, that feature of the TSP was working from day 1.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...