This is the last time I'll post this specific request to this list.
I'm just giving it one more shot in case it catches someone's eye
this time :)
I've been working with Polycom to get their Spectralink wifi phones
working properly with Sipx (post 4.0.4 - they used to work
properly).
I have worked with polycom and tested several new firmwares and we
have troubleshot together. We have made a ton of progress.
The only remaining issue I still have (if I get this resolved, I
could find more) is transfers with external calls. The work below is
on 4.2.1, but they seem to behave the same on 4.4 as well.
The 2 wireshark captures reference below can be downloaded here:
http://www.dsi-corp.com/mk/captures.zip
*****You must follow these steps to be able to view the capture:
The pcap is encrypted with WPA2 and will need to be decrypted within
Wireshark (I don’t know of any way to save a decrypted capture). The
ssid is DSI-VOIP and the passphrase is ‘adadadadad’. So you should
be able to enter ‘wpa-pwd:adadadadad:DSI-VOIP’ as the key under
Edit/Preferences/Protocols/IEEE 802.11 in Wireshark and enable
decryption.
Polycom engineers have a few questions below. I am simply not good
enough with sip traces yet to intelligently answer their questions.
I know there are others that have an interest in getting these
working. Can anyone help me with their questions? If I don't have
any luck with this post, I will open a paid sipx support ticket.
Thanks as always,
Matthew
In both captures, a call was placed form the Spectralink 8020 to
615-500-8073 and a transfer was attempted from the Spectralink 8020.
In one, it was an attempt to transfer to 0/IVR. In the other, it was
to a Soundpoint 550 at extension 0142.
Both transfers fail.
Here is more information:
Slink 8020 - 10.87.20.223 ext. 9999
Sipx pbx - 10.87.20.5
Verizon VOIP servers - 172.x.x.x
Call from Slink 8020 => 6155008073
Polycom engineer comments/questions:
transfertoext032211.pcap: "has exactly the same problem. The PBX
never seems to get the ACK from the phone for the first INVITE. It
appears to ignore the second INVITE so the phone cannot do the
transfer."
transfertozero032211.pcap:
shows packets between phone (20.220) and PBX (205)
3329 sends INVITE 102
(gets 407s and acks them)
3376 sends INVITE 103 to 95008073
3383 recvs 100 Trying
4508 recvs 183 Session progress
5025 recvs 200 OK to INVITE 103
5138 sends ACK 103
(now SHOULD BE in call with 95008073 - the phone thinks it is call
because it
got the 200 OK and it sent the ACK. However, the PBX does not seem
to think so).
5191 recvs 200 OK to INVITE 103 again <------------------------
5249 sends ACK 103 again
5460 recvs 200 OK to INVITE 103 again <------------------------
5528 sends ACK 103 again
6026 recvs 200 OK to INVITE 103 again <------------------------
6081 sends ACK 103 again
7147 recvs 200 OK to INVITE 103 again <------------------------
7141 sends ACK 103 again
7241 sends INVITE 104 to 95008073 with sendonly (to put this call on
hold)
7250 recvs 100 Trying
7926 recvs 200 OK to INVITE 103 again <------------------------
7945 sends ACK 103 again
8620 recvs 200 OK to INVITE 103 again <------------------------
8649 sends ACK 103 again
8710 sends BYE
1. The phone never receives the 200 OK for INVITE 104 so it can't
put the
original call on hold. The phone has to fail the transfer operation.
2. The PBX keeps sending the 200 OK for INVITE 103 as if it is not
getting the ACK
that is sent by the phone.
-------- Original Message --------
Did you try this part?
The ssid is DSI-VOIP and the passphrase is ‘adadadadad’. So you can
enter ‘wpa-pwd:adadadadad:DSI-VOIP’ as the key under
Edit/Preferences/Protocols/IEEE 802.11 in Wireshark and enable
decryption.
Are you not able to open it all? I"m attaching it again to this
email. Thank you!
On 3/21/2011 11:48 AM, Michael Picher wrote:
wireshark really doesn't like this pcap for some
reason...
On Mon, Mar 21, 2011 at 12:39 PM, Matthew
Kitchin (public/usenet) <[email protected]>
wrote:
* Polite bump request.
*
If there is anyone who could please help me with the issue
below, I would greatly appreciate it. I can open a paid
support ticket if that is a possible route.
-------- Original Message --------
| Subject:
|
Re: Spectralink 8020 up and running - need some
help |
| Date:
|
Thu, 17 Mar 2011 10:41:07 -0500 |
| From:
|
Matthew Kitchin (public/usenet) <[email protected]> |
| To:
|
sipx-users <[email protected]> |
The wireshark capture can be downloaded here:
http://www.dsi-corp.com/mk/transfer030811.zip
On 3/17/2011 10:33 AM, Matthew Kitchin (public/usenet)
wrote:
I post the email below 2 days ago,
but I'm thinking it didn't make it to the list because the
size was 710 kb. Is there anyone out there who will give
me a hand with this? I think it could be helpful for many
who are looking to use these phones. I will try and find a
place to upload the the file.
-------- Original Message --------
| Subject:
|
Re: [sipx-users] Spectralink 8020 up and running |
| Date:
|
Tue, 15 Mar 2011 13:33:58 -0500 |
| From:
|
Matthew Kitchin (public/usenet) <[email protected]> |
| To:
|
Discussion list for users of sipXecs software <[email protected]> |
Update, and I need some help.
I have been working with polycom and tested several new
firmwares and we have troubleshot together. The only
remaining issue I still have is transfers with external
calls.
Their preferred method of diagnosing is wireshark to
capture at the wifi level (yes, that has made it a little
more tedious for us). That is what I am attaching, because
that is what their notes below refer too.
I'm showing them that blind transfers work with other
phones, especially Polycom Soundpoint phones, but they
still asked if I could shed some lite on their
observations.
They are being extremely helpful, responsive, interested,
and turning out updated firmware within a day or 2 every
time I give more captures of what went wrong. We have at
least fixed it so these phones do work (obviously with the
exception of transfers) with sipx 4.2.1.
In the attached pcap file, it encrypted with WPA2 and will
need to be decrypted within Wireshark (I don’t know of any
way to save a decrypted capture). The ssid is DSI-VOIP and
the passphrase is ‘adadadadad’. So you can enter
‘wpa-pwd:adadadadad:DSI-VOIP’ as the key under
Edit/Preferences/Protocols/IEEE 802.11 in Wireshark and
enable decryption.
The info for the call is:
Spectralink 8020: Ext 9999, IP=10.82.20.223
Sipx 4.2.1 server: 10.87.20.5
Verizon Voip, sipxbridge, No IP NAT
The capture is an outbound call placed from the
Spectralink 8020 and then a failed transfer/
If anyone can help me explain what is or isn't happening,
I would greatly appreciate it and I am confident we can
get a wifi phone that is 100% compatible with sipx and
made by polycom.
Thanks,
Matthew
Polycom Spectralink engineer notes:
This looks like a problem with the SIPX server.
Basically, the SIPX is never sending us the 200 OK for the
transfer (INVITE 104):
2152 send INVITE 102 from 9999 to 95171139 gets 407 and
Acks that (gets another and Acks that too)
2195 send INVITE 103 from 9999 to 95171139
2203 recv 100 to INVITE 103
2653 recv 183 to INVITE 103
3652 recv 200 ok for INVITE 103
3747 send ACK 103
<initial setup for call from 9999 to 95171139 SHOULD BE
done here>
3795 recv another 200 ok for INVITE 103
3859 send another ACK 103
4074 recv another 200 ok for INVITE 103
4139 send another ACK 103
4636 recv another 200 ok for INVITE 103
4697 send another ACK 103
5690 recv another 200 ok for INVITE 103
5749 send another ACK 103
6046 send INVITE 104 from 9999 to to 95171139 with
sendonly
6054 recv 100 to INVITE 104
6512 recv another 200 ok for INVITE 103
6524 send another ACK 103
7202 recv another 200 ok for INVITE 103
7227 send another ACK 103
7287 recv BYE 1
7299 send 200 ok to BYE 1
Do you have a SIPX contact you can escalate this to?
On 2/24/2011 2:36 PM, Matthew Kitchin (public/usenet)
wrote:
This was their response as far as
me sharing the firmware:
"Excellent news. Let me know what you find on the
transfer issue.
Now that we have confirmation of the fix we will be
rolling this into our next GA release. Feel free to let
the user group know that a fix is available, but direct
them to Polycom support to obtain it for the time
being."
The Polycom support ticket realted to this is 'Case#
1-103152086'
If anyone has any trouble getting the firmware before it
is released, let me know.
I will be glad to write a wiki article on how to get
these up and running.
On 2/24/2011 1:57 PM, Matthew Kitchin (public/usenet)
wrote:
Success. I got an updated
firmware from Polycom, and the problem of calls to the
PSTN crashing is resolved.
Per their notes:
"The one caveat with this software is that we were
never able to reproduce the problem. However we saw
in the trace one part of the message header was larger
than we had buffer space for, which was causing memory
overwrites, and the fix increases that buffer size.
Give it a test and let me know."
I am waiting to see if they are going to publish the
firmware or if they mind if I post it here.
I am having one issue that was occurring before this
fix, but I haven't dug into it yet. I can't do
transfers involving the PSTN. I can do internal
transfers fine. I will start digging into that next.
I'm going to play with some codec settings, and maybe
try 4.4 since several other transfer related issues I
experience with Verizon are resolved/fixed/or
something similar in 4.4.
On 2/21/2011 11:03 AM, Matthew Kitchin (public/usenet)
wrote:
I believe there are a few
other interested in this. I asked for an update
today, and I have some hope based on the response:
"We have a good idea of where the bug is and are
working on a software fix. Our
offices are closed today, but I should be able to
get a status update for you tomorrow. "
On 2/17/2011 10:27 AM, Matthew Kitchin
(public/usenet) wrote:
For what it is worth, there
is a group of Polycom engineers all working on
this. I have sent them wireshark captures, crash
dumps from the phone, and various other pieces of
information. They have been very quick to respond,
ask more questions, and seem eager to work on
this. Hopefully it will go somewhere.
On 2/15/2011 1:23 PM, Matthew Kitchin
(public/usenet) wrote:
It looks like I'm having
this exact problem:
http://www.mail-archive.com/[email protected]/msg14035.html
On 2/15/2011 1:04 PM, Matthew Kitchin
(public/usenet) wrote:
Yeah, I am am having
some issues after all. I'm getting no audio
under certain situations.
I'm assuming this is the option that causes
the reboots
Time to get the engineer back on the phone.
On 2/15/2011 12:32 PM, Tony Graziano wrote:
What I have seen is issues with the phones rebooting or not transferring
calls when being used with "certain ITSP's".
You might do yourself a favor and ensure transfers and other scenarios work
with your different gateways to see if you have the same problems.
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: [email protected]
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
----- Original Message -----
From: [email protected]
<[email protected]>
To: Discussion list for users of sipXecs software
<[email protected]>
Sent: Tue Feb 15 13:30:17 2011
Subject: [sipx-users] Spectralink 8020 up and running (was: Cisco
WIP310 -wifiissues)
I am up and running with a Polycom Spectralink 8020.
I had tried this model once before but gave up.
There were 2 big differences this time.
1) I called Polycom sales first and was given the contact info of an
engineer that started out with Spectralink
2) I got the dual battery charging station that allows you to edit the
phone directly with the handset administration tool.
I will keep test driving it to see if if I have any issues, but it
appears to work fine. Parts of the interface are a little quirky
compared to a Soundpoint 450/550/650, but it looks like it will do the
job for a basic phone.
Let me know if anyone is interested in any tips on this phone.
Thanks,
Matthew
On 2/11/2011 4:34 PM, Matthew Kitchin (public/usenet) wrote:
I managed to get the Unidata WPU-7800 working, but it seems like a
piece of junk. It looks like someone wrote the interface in a foreign
language and then used and online translator to get it into English.
Oh well. I'll keep searching.
You would think there would be a decent wifi sip handset out there.
On 2/10/2011 10:05 AM, Matthew Kitchin (public/usenet) wrote:
I did. I ordered one of the Spectralink 8020 handsets. I don't want
to have to buy a Polycom server/wap. I need it to directly user our
Cisco WAP infrastructure. I managed to get the 8020 converted to SIP,
but i did not get too much further. It seemed to be a nightmare (for
me at least) to try and configure from the LCD screen. We could never
get it to stay on on our wifi network for more than about 10 pings.
The WIP 310 was at least simple to configure from the web interface.
I ordered one of these - Unidata WPU-7800. I should have it tomorrow.
The specs look ok, but I'm not overly hopeful. I looked at the specs
for the Polycom 8400. It looks like way overkill. I couldn't find a
price for it, but I imagine it is pretty high.
On 2/10/2011 9:48 AM, Michael Picher wrote:
i assume you've looked at the Polycom / Kirk stuff... they have a
wifi version now.
i did a quick scan of the email thread so i may have missed it.
On Wed, Feb 9, 2011 at 1:00 PM, Tony Graziano
<[email protected] <mailto:[email protected]>>
wrote:
Crappy hardware leaves your experience wanting.
If it matters, android 2.3 and the current shipping version of
honeycomb
have a full sip stack that have direct acces to resources for
apps to
leverage... Stay tuned.
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: [email protected]
<mailto:[email protected]>
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
----- Original Message -----
From: [email protected]
<mailto:[email protected]>
<[email protected]
<mailto:[email protected]>>
To: Discussion list for users of sipXecs software
<[email protected]
<mailto:[email protected]>>
Sent: Wed Feb 09 12:55:32 2011
Subject: Re: [sipx-users] Cisco WIP310 - wifi issues
Hmmm this could be an interesting alternative to droid x with
csipsimple:
http://www.archos.com/products/ta/archos_28it/specs.html?country=us&lang=en
<http://www.archos.com/products/ta/archos_28it/specs.html?country=us&lang=en>
~$99 ea. comes with froyo
I've found that most of these smart phones have crappy wifi antennas
though and roaming sucks!
Kyle
On Wed, Feb 9, 2011 at 10:14 AM, Michael Scheidell
<[email protected]
<mailto:[email protected]>> wrote:
> On 2/9/11 12:11 PM, Matthew Kitchin (public/usenet) wrote:
>
> Sweet. Time to search some more for the perfect wifi phone.
>
>
>
> motorola droid x with sipcimple on it. :-)
>
> supports transfer, bluetooth, etc. only $399 each without a
contract. :-(
>
>
>
> --
> Michael Scheidell, CTO
> o: 561-999-5000
> d: 561-948-2259
> ISN: 1259*1300
>> | SECNAP Network Security Corporation
>
> * Certified SNORT Integrator
> * 2008-9 Hot Company Award Winner, World Executive Alliance
> * Five-Star Partner Program 2009, VARBusiness
> * Best in Email Security,2010: Network Products Guide
> * King of Spam Filters, SC Magazine 2008
>
> ________________________________
>
> This email has been scanned and certified safe by SpammerTrap®.
> For Information please see
http://www.secnap.com/products/spammertrap/
>
> ________________________________
>
>
_______________________________________________
sipx-users mailing list
[email protected]
<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
There are 10 kinds of people in this world, those who understand
binary and those who don't.
[email protected] <mailto:[email protected]>
blog: http://www.sipxecs.info
call: sip:[email protected] <mailto:sip%[email protected]>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive:http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
There are 10 kinds of people in this world, those who understand
binary and those who don't.
[email protected]
blog: http://www.sipxecs.info
call: sip:[email protected]
|
