Discussion:
SIP TAPI no longer working?
Tony Graziano
2008-04-07 19:08:06 UTC
Permalink
Running v3.10.1 on FC6.

Since version 3.8x I've found SIP TAPI (Click2Dial) no longer seems to
work. I've gone through several client config variations, and only
recently had time to look into this.

Here is ar debug entries from sipXproxy.log of the failed transaction.

What else should I be doing to make this operate? I recall a post last
month about Click2dial not working, but have not seen anything else
about it.

What else should I be looking at or providing in order to find the
problem?


====BEGIN LOG===
"2008-04-07T18:55:56.289265Z":30:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.302416Z":31:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.315785Z":32:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.330127Z":33:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
content-length: 227 wrong setting to: 0"
===END LOG===

Thanks,

Tony
Porier, Jeremy M.
2008-04-07 19:47:29 UTC
Permalink
I haven't had time to troubleshoot it but it isn't working for us
either.

- Jeremy

________________________________

From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tony
Graziano
Sent: Monday, April 07, 2008 1:08 PM
To: sipx-***@list.sipfoundry.org
Subject: [sipx-users] SIP TAPI no longer working?


Running v3.10.1 on FC6.

Since version 3.8x I've found SIP TAPI (Click2Dial) no longer seems to
work. I've gone through several client config variations, and only
recently had time to look into this.

Here is ar debug entries from sipXproxy.log of the failed transaction.

What else should I be doing to make this operate? I recall a post last
month about Click2dial not working, but have not seen anything else
about it.

What else should I be looking at or providing in order to find the
problem?


====BEGIN LOG===
"2008-04-07T18:55:56.289265Z":30:SIP:WARNING:pbx.mydomain.com:SipRouter-
11:B6EDBB90:SipXProxy:"SipUserAgent::send INVITE request matches
existing transaction"
"2008-04-07T18:55:56.302416Z":31:SIP:WARNING:pbx.mydomain.com:SipRouter-
11:B6EDBB90:SipXProxy:"SipUserAgent::send INVITE request matches
existing transaction"
"2008-04-07T18:55:56.315785Z":32:SIP:WARNING:pbx.mydomain.com:SipRouter-
11:B6EDBB90:SipXProxy:"SipUserAgent::send INVITE request matches
existing transaction"
"2008-04-07T18:55:56.330127Z":33:SIP:WARNING:pbx.mydomain.com:SipRouter-
11:B6EDBB90:SipXProxy:"SipUserAgent::send INVITE request matches
existing transaction"
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClient
Udp-8:B7A5CB90:SipXProxy:"HttpMessage::getBytes content-length: 227
wrong setting to: 0"
===END LOG===

Thanks,

Tony
Dale Worley
2008-04-07 21:24:00 UTC
Permalink
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.

Dale
Tony Graziano
2008-04-07 21:43:47 UTC
Permalink
Hi Dale,

Thanks for the response. This is not sipxtapi.

http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlook%2C_CardScan%2C_ACT%21_using_SIP_TAPI

This is a TSP for SIP based systems. Works on pbxnsip, asterisk and a
host of thers too. Used to work on sipx, though I suspect something in
either the proxy or the cpp code for the http headers has changed that
alter the expected value from whatever was sent to "0". This is why I
sent the debugs in since I had captured the onformation.

Where would I ask about this in sipxecs?

Thanks,

Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.

Dale
Robert Joly
2008-04-07 22:22:19 UTC
Permalink
Gents,
I'm not a SIP TAPI user however I know that it does rely on REFER
messages. The handling of REFERs has changed in sipXecs 3.10 so that
REFERs without Replaces headers are challenged by the proxy (see
XECS-401 for grueling details) and I suspect that this is what is
causing trouble. Unless SIP TAPI has valid credentials to respond to a
challenged REFER, the call will fail. If you can take a network trace
using a tool like wireshark of the failing call, look for 407 - Proxy
Authentication Required messages.

Cheers,
bob
-----Original Message-----
Tony Graziano
Sent: Monday, April 07, 2008 5:44 PM
Subject: Re: [sipx-users] SIP TAPI no longer working?
Hi Dale,
Thanks for the response. This is not sipxtapi.
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlo
ok%2C_CardScan%2C_ACT%21_using_SIP_TAPI
This is a TSP for SIP based systems. Works on pbxnsip,
asterisk and a host of thers too. Used to work on sipx,
though I suspect something in either the proxy or the cpp
code for the http headers has changed that alter the expected
value from whatever was sent to "0". This is why I sent the
debugs in since I had captured the onformation.
Where would I ask about this in sipxecs?
Thanks,
Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.
Dale
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
Porier, Jeremy M.
2008-04-08 14:08:41 UTC
Permalink
We're on 3.8.1 so I don't think that would be the issue for us.

- Jeremy

-----Original Message-----
From: Robert Joly [mailto:***@nortel.com]
Sent: Monday, April 07, 2008 4:22 PM
To: Tony Graziano; Porier, Jeremy M.; ***@pingtel.com
Cc: sipx-***@list.sipfoundry.org
Subject: RE: [sipx-users] SIP TAPI no longer working?

Gents,
I'm not a SIP TAPI user however I know that it does rely on REFER
messages. The handling of REFERs has changed in sipXecs 3.10 so that
REFERs without Replaces headers are challenged by the proxy (see
XECS-401 for grueling details) and I suspect that this is what is
causing trouble. Unless SIP TAPI has valid credentials to respond to a
challenged REFER, the call will fail. If you can take a network trace
using a tool like wireshark of the failing call, look for 407 - Proxy
Authentication Required messages.

Cheers,
bob
-----Original Message-----
Graziano
Sent: Monday, April 07, 2008 5:44 PM
Subject: Re: [sipx-users] SIP TAPI no longer working?
Hi Dale,
Thanks for the response. This is not sipxtapi.
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlo
ok%2C_CardScan%2C_ACT%21_using_SIP_TAPI
This is a TSP for SIP based systems. Works on pbxnsip, asterisk and a
host of thers too. Used to work on sipx, though I suspect something in
either the proxy or the cpp code for the http headers has changed that
alter the expected value from whatever was sent to "0". This is why I
sent the debugs in since I had captured the onformation.
Where would I ask about this in sipxecs?
Thanks,
Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.
Dale
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
Tony Graziano
2008-04-07 22:55:53 UTC
Permalink
It does use those credentials. It broke in 3.8.

I think the message length is the issue. Something in the proxy since
3.4 or 3.6 has changed the length being returned, resulting in no invite
being sent.

====BEGIN LOG===
"2008-04-07T18:55:56.289265Z":30:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.302416Z":31:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.315785Z":32:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.330127Z":33:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
content-length: 227 wrong setting to: 0"
===END LOG===

The last line is the most telling:

"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
content-length: 227 wrong setting to: 0"

This is more likely due to a cpp code change to handle a memory or sipx
constraint and was set a "0"? So just to let you know, sipxtapi is a TSP
used by many sip systems and it does include credentials and so froth.
It matches the transaction and it exists. The issue is in the http
message length returned from the proxy.

As such, the wiki probably needs to state it is no longer functional
after 3.6 anyway. There's an assumption that if you follow-the-wiki it
should work, when it obviously does not maybe an update is warranted?
Right now this is not functional and if noone wants to look at it then
maybe someone can update the wiki and say "not working since 3.6"?

http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlook%2C_CardScan%2C_ACT!_using_SIP_TAPI
Gents,
I'm not a SIP TAPI user however I know that it does rely on REFER
messages. The handling of REFERs has changed in sipXecs 3.10 so that
REFERs without Replaces headers are challenged by the proxy (see
XECS-401 for grueling details) and I suspect that this is what is
causing trouble. Unless SIP TAPI has valid credentials to respond to a
challenged REFER, the call will fail. If you can take a network trace
using a tool like wireshark of the failing call, look for 407 - Proxy
Authentication Required messages.

Cheers,
bob
-----Original Message-----
Tony Graziano
Sent: Monday, April 07, 2008 5:44 PM
Subject: Re: [sipx-users] SIP TAPI no longer working?
Hi Dale,
Thanks for the response. This is not sipxtapi.
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlo
ok%2C_CardScan%2C_ACT%21_using_SIP_TAPI
This is a TSP for SIP based systems. Works on pbxnsip,
asterisk and a host of thers too. Used to work on sipx,
though I suspect something in either the proxy or the cpp
code for the http headers has changed that alter the expected
value from whatever was sent to "0". This is why I sent the
debugs in since I had captured the onformation.
Where would I ask about this in sipxecs?
Thanks,
Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.
Dale
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
Scott Lawrence
2008-04-08 11:04:23 UTC
Permalink
Post by Tony Graziano
It does use those credentials. It broke in 3.8.
I think the message length is the issue. Something in the proxy since
3.4 or 3.6 has changed the length being returned, resulting in no invite
being sent.
Perhaps you could capture a trace?
--
Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:***@pingtel.com
sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/
http://www.pingtel.com/
Klaus Darilion
2009-06-09 13:40:46 UTC
Permalink
Sorry for picking up that old thread.

I have reviewed SIPTAPI (I am the author) and recent SIPTAPI version
0.2.6 should handle authentication of REFER correct.

Maybe someone can try again with SIPTAPI 0.2.6.

thanks
klaus
Post by Tony Graziano
It does use those credentials. It broke in 3.8.
I think the message length is the issue. Something in the proxy since
3.4 or 3.6 has changed the length being returned, resulting in no invite
being sent.
====BEGIN LOG===
"2008-04-07T18:55:56.289265Z":30:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.302416Z":31:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.315785Z":32:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.330127Z":33:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B6EDBB90:SipXProxy:"SipUserAgent::send
INVITE request matches existing transaction"
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
content-length: 227 wrong setting to: 0"
===END LOG===
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
content-length: 227 wrong setting to: 0"
This is more likely due to a cpp code change to handle a memory or sipx
constraint and was set a "0"? So just to let you know, sipxtapi is a TSP
used by many sip systems and it does include credentials and so froth.
It matches the transaction and it exists. The issue is in the http
message length returned from the proxy.
As such, the wiki probably needs to state it is no longer functional
after 3.6 anyway. There's an assumption that if you follow-the-wiki it
should work, when it obviously does not maybe an update is warranted?
Right now this is not functional and if noone wants to look at it then
maybe someone can update the wiki and say "not working since 3.6"?
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlook%2C_CardScan%2C_ACT!_using_SIP_TAPI
Gents,
I'm not a SIP TAPI user however I know that it does rely on REFER
messages. The handling of REFERs has changed in sipXecs 3.10 so that
REFERs without Replaces headers are challenged by the proxy (see
XECS-401 for grueling details) and I suspect that this is what is
causing trouble. Unless SIP TAPI has valid credentials to respond to a
challenged REFER, the call will fail. If you can take a network trace
using a tool like wireshark of the failing call, look for 407 - Proxy
Authentication Required messages.
Cheers,
bob
-----Original Message-----
Tony Graziano
Sent: Monday, April 07, 2008 5:44 PM
Subject: Re: [sipx-users] SIP TAPI no longer working?
Hi Dale,
Thanks for the response. This is not sipxtapi.
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlo
ok%2C_CardScan%2C_ACT%21_using_SIP_TAPI
This is a TSP for SIP based systems. Works on pbxnsip,
asterisk and a host of thers too. Used to work on sipx,
though I suspect something in either the proxy or the cpp
code for the http headers has changed that alter the expected
value from whatever was sent to "0". This is why I sent the
debugs in since I had captured the onformation.
Where would I ask about this in sipxecs?
Thanks,
Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.
Dale
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
heros
2009-07-03 15:42:57 UTC
Permalink
Hi Klaus, thank you for siptapi
I tested SIPTAPI 0.2.6 it on SIPX 4.01 and it works nicely for me. Is there
a version of siptapi available
for windows 64 bit systems?

Thank you,
Heros


-----Messaggio originale-----
Da: Klaus Darilion [mailto:***@pernau.at]
Inviato: martedì 9 giugno 2009 15.41
A: Tony Graziano
Cc: ***@ccu.edu; sipx-***@list.sipfoundry.org; ***@pingtel.com
Oggetto: Re: [sipx-users] SIP TAPI no longer working?

Sorry for picking up that old thread.

I have reviewed SIPTAPI (I am the author) and recent SIPTAPI version
0.2.6 should handle authentication of REFER correct.

Maybe someone can try again with SIPTAPI 0.2.6.

thanks
klaus
Post by Tony Graziano
It does use those credentials. It broke in 3.8.
I think the message length is the issue. Something in the proxy since
3.4 or 3.6 has changed the length being returned, resulting in no invite
being sent.
====BEGIN LOG===
"2008-04-07T18:55:56.289265Z":30:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.302416Z":31:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.315785Z":32:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.330127Z":33:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-
8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
Post by Tony Graziano
content-length: 227 wrong setting to: 0"
===END LOG===
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-
8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
Post by Tony Graziano
content-length: 227 wrong setting to: 0"
This is more likely due to a cpp code change to handle a memory or sipx
constraint and was set a "0"? So just to let you know, sipxtapi is a TSP
used by many sip systems and it does include credentials and so froth.
It matches the transaction and it exists. The issue is in the http
message length returned from the proxy.
As such, the wiki probably needs to state it is no longer functional
after 3.6 anyway. There's an assumption that if you follow-the-wiki it
should work, when it obviously does not maybe an update is warranted?
Right now this is not functional and if noone wants to look at it then
maybe someone can update the wiki and say "not working since 3.6"?
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlook%2C_CardScan
%2C_ACT!_using_SIP_TAPI
Post by Tony Graziano
Gents,
I'm not a SIP TAPI user however I know that it does rely on REFER
messages. The handling of REFERs has changed in sipXecs 3.10 so that
REFERs without Replaces headers are challenged by the proxy (see
XECS-401 for grueling details) and I suspect that this is what is
causing trouble. Unless SIP TAPI has valid credentials to respond to a
challenged REFER, the call will fail. If you can take a network trace
using a tool like wireshark of the failing call, look for 407 - Proxy
Authentication Required messages.
Cheers,
bob
-----Original Message-----
Tony Graziano
Sent: Monday, April 07, 2008 5:44 PM
Subject: Re: [sipx-users] SIP TAPI no longer working?
Hi Dale,
Thanks for the response. This is not sipxtapi.
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlo
ok%2C_CardScan%2C_ACT%21_using_SIP_TAPI
This is a TSP for SIP based systems. Works on pbxnsip,
asterisk and a host of thers too. Used to work on sipx,
though I suspect something in either the proxy or the cpp
code for the http headers has changed that alter the expected
value from whatever was sent to "0". This is why I sent the
debugs in since I had captured the onformation.
Where would I ask about this in sipxecs?
Thanks,
Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.
Dale
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
heros
2009-07-06 09:07:11 UTC
Permalink
Sorry for the question. I disco verde there are binaries for 64 bit too.
I'll test it and provide feedback
Here on the users list

Heros


-----Messaggio originale-----
Da: heros [mailto:***@sidin.it]
Inviato: venerdì 3 luglio 2009 17.43
A: 'Klaus Darilion'
Cc: sipx-***@list.sipfoundry.org
Oggetto: [sipx-users] R: SIP TAPI no longer working?

Hi Klaus, thank you for siptapi
I tested SIPTAPI 0.2.6 it on SIPX 4.01 and it works nicely for me. Is there
a version of siptapi available
for windows 64 bit systems?

Thank you,
Heros


-----Messaggio originale-----
Da: Klaus Darilion [mailto:***@pernau.at]
Inviato: martedì 9 giugno 2009 15.41
A: Tony Graziano
Cc: ***@ccu.edu; sipx-***@list.sipfoundry.org; ***@pingtel.com
Oggetto: Re: [sipx-users] SIP TAPI no longer working?

Sorry for picking up that old thread.

I have reviewed SIPTAPI (I am the author) and recent SIPTAPI version
0.2.6 should handle authentication of REFER correct.

Maybe someone can try again with SIPTAPI 0.2.6.

thanks
klaus
Post by Tony Graziano
It does use those credentials. It broke in 3.8.
I think the message length is the issue. Something in the proxy since
3.4 or 3.6 has changed the length being returned, resulting in no invite
being sent.
====BEGIN LOG===
"2008-04-07T18:55:56.289265Z":30:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.302416Z":31:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.315785Z":32:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.330127Z":33:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-
8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
Post by Tony Graziano
content-length: 227 wrong setting to: 0"
===END LOG===
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-
8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
Post by Tony Graziano
content-length: 227 wrong setting to: 0"
This is more likely due to a cpp code change to handle a memory or sipx
constraint and was set a "0"? So just to let you know, sipxtapi is a TSP
used by many sip systems and it does include credentials and so froth.
It matches the transaction and it exists. The issue is in the http
message length returned from the proxy.
As such, the wiki probably needs to state it is no longer functional
after 3.6 anyway. There's an assumption that if you follow-the-wiki it
should work, when it obviously does not maybe an update is warranted?
Right now this is not functional and if noone wants to look at it then
maybe someone can update the wiki and say "not working since 3.6"?
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlook%2C_CardScan
%2C_ACT!_using_SIP_TAPI
Post by Tony Graziano
Gents,
I'm not a SIP TAPI user however I know that it does rely on REFER
messages. The handling of REFERs has changed in sipXecs 3.10 so that
REFERs without Replaces headers are challenged by the proxy (see
XECS-401 for grueling details) and I suspect that this is what is
causing trouble. Unless SIP TAPI has valid credentials to respond to a
challenged REFER, the call will fail. If you can take a network trace
using a tool like wireshark of the failing call, look for 407 - Proxy
Authentication Required messages.
Cheers,
bob
-----Original Message-----
Tony Graziano
Sent: Monday, April 07, 2008 5:44 PM
Subject: Re: [sipx-users] SIP TAPI no longer working?
Hi Dale,
Thanks for the response. This is not sipxtapi.
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlo
ok%2C_CardScan%2C_ACT%21_using_SIP_TAPI
This is a TSP for SIP based systems. Works on pbxnsip,
asterisk and a host of thers too. Used to work on sipx,
though I suspect something in either the proxy or the cpp
code for the http headers has changed that alter the expected
value from whatever was sent to "0". This is why I sent the
debugs in since I had captured the onformation.
Where would I ask about this in sipxecs?
Thanks,
Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.
Dale
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
Geoff Van Brunt
2009-07-08 16:10:17 UTC
Permalink
There is a 64 bit version available. I worked with Klaus prior to his announcement and tested it on Vista 64. It does work.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of heros
Sent: July-06-09 5:07 AM
To: 'Klaus Darilion'
Cc: sipx-***@list.sipfoundry.org
Subject: [sipx-users] R: R: SIP TAPI no longer working?

Sorry for the question. I disco verde there are binaries for 64 bit too.
I'll test it and provide feedback
Here on the users list

Heros


-----Messaggio originale-----
Da: heros [mailto:***@sidin.it]
Inviato: venerdì 3 luglio 2009 17.43
A: 'Klaus Darilion'
Cc: sipx-***@list.sipfoundry.org
Oggetto: [sipx-users] R: SIP TAPI no longer working?

Hi Klaus, thank you for siptapi
I tested SIPTAPI 0.2.6 it on SIPX 4.01 and it works nicely for me. Is there
a version of siptapi available
for windows 64 bit systems?

Thank you,
Heros


-----Messaggio originale-----
Da: Klaus Darilion [mailto:***@pernau.at]
Inviato: martedì 9 giugno 2009 15.41
A: Tony Graziano
Cc: ***@ccu.edu; sipx-***@list.sipfoundry.org; ***@pingtel.com
Oggetto: Re: [sipx-users] SIP TAPI no longer working?

Sorry for picking up that old thread.

I have reviewed SIPTAPI (I am the author) and recent SIPTAPI version
0.2.6 should handle authentication of REFER correct.

Maybe someone can try again with SIPTAPI 0.2.6.

thanks
klaus
Post by Tony Graziano
It does use those credentials. It broke in 3.8.
I think the message length is the issue. Something in the proxy since
3.4 or 3.6 has changed the length being returned, resulting in no invite
being sent.
====BEGIN LOG===
"2008-04-07T18:55:56.289265Z":30:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.302416Z":31:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.315785Z":32:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.330127Z":33:SIP:WARNING:pbx.mydomain.com:SipRouter-11:B
6EDBB90:SipXProxy:"SipUserAgent::send
Post by Tony Graziano
INVITE request matches existing transaction"
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-
8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
Post by Tony Graziano
content-length: 227 wrong setting to: 0"
===END LOG===
"2008-04-07T18:55:56.338035Z":34:HTTP:WARNING:pbx.mydomain.com:SipClientUdp-
8:B7A5CB90:SipXProxy:"HttpMessage::getBytes
Post by Tony Graziano
content-length: 227 wrong setting to: 0"
This is more likely due to a cpp code change to handle a memory or sipx
constraint and was set a "0"? So just to let you know, sipxtapi is a TSP
used by many sip systems and it does include credentials and so froth.
It matches the transaction and it exists. The issue is in the http
message length returned from the proxy.
As such, the wiki probably needs to state it is no longer functional
after 3.6 anyway. There's an assumption that if you follow-the-wiki it
should work, when it obviously does not maybe an update is warranted?
Right now this is not functional and if noone wants to look at it then
maybe someone can update the wiki and say "not working since 3.6"?
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlook%2C_CardScan
%2C_ACT!_using_SIP_TAPI
Post by Tony Graziano
Gents,
I'm not a SIP TAPI user however I know that it does rely on REFER
messages. The handling of REFERs has changed in sipXecs 3.10 so that
REFERs without Replaces headers are challenged by the proxy (see
XECS-401 for grueling details) and I suspect that this is what is
causing trouble. Unless SIP TAPI has valid credentials to respond to a
challenged REFER, the call will fail. If you can take a network trace
using a tool like wireshark of the failing call, look for 407 - Proxy
Authentication Required messages.
Cheers,
bob
-----Original Message-----
Tony Graziano
Sent: Monday, April 07, 2008 5:44 PM
Subject: Re: [sipx-users] SIP TAPI no longer working?
Hi Dale,
Thanks for the response. This is not sipxtapi.
http://sipx-wiki.calivia.com/index.php/Click-to-Dial_for_Outlo
ok%2C_CardScan%2C_ACT%21_using_SIP_TAPI
This is a TSP for SIP based systems. Works on pbxnsip,
asterisk and a host of thers too. Used to work on sipx,
though I suspect something in either the proxy or the cpp
code for the http headers has changed that alter the expected
value from whatever was sent to "0". This is why I sent the
debugs in since I had captured the onformation.
Where would I ask about this in sipxecs?
Thanks,
Tony
Post by Porier, Jeremy M.
I haven't had time to troubleshoot it but it isn't working for us
either.
You should probably ask on the sipx-tapi mailing list.
Dale
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Loading...