Hello,
I try to make the PushSDK to work.
I've installed Tomcat version 6.0, deployed a sample application from PushSDK: push.war and made the following changes in the 46xxsettings.txt file:
SET TPSLIST 192.168.2.65 - address of my Tomcat server
SET PUSHPORT 80
SET PUSHCAP 222
Than I reboot my Avaya 9630 IP phone (firmware release 3.02) and try to send TOPLINE PUSH ...
I have this issue as well, dont think its a bug, it must be the set up as other users have it working. Perhaps a firewall issue? If anyone figures it out, i'd also be interested. I posted about this before, even had a sniffer on, but no success.
I got the report from wireshark as below:
No. Time Source Destination Protocol Info
31 13.173559 192.168.100.105 192.168.100.222 TCP [TCP segment of a reassembled PDU]
Frame 31 (245 bytes on wire, 245 bytes captured)
Ethernet II, Src: 00:1b:4f:14:fc:84 (00:1b:4f:14:fc:84), Dst: Usi_15:89:a1 (00:16:41:15:89:a1)
Internet Protocol, Src: 192.168.100.105 (192.168.100.105), Dst: 192....
jakiehu jakiehu is offline Member replied 3 months ago
I got the report from wireshark as below:
No. Time Source Destination Protocol Info
31 13.173559 192.168.100.105 192.168.100.222 TCP [TCP segment of a reassembled PDU]
Frame 31 (245 bytes on wire, 245 bytes captured)
Ethernet II, Src: 00:1b:4f:14:fc:84 (00:1b:4f:14:fc:84), Dst: Usi_15:89:a1 (00:16:41:15:89:a1)
Internet Protocol, Src: 192.168.100.105 (192.168.100.105), Dst: 192....
Quote:
Originally Posted by smitty50
Try SET TPSLIST 192.168.2.65:8080 That fixed my issue...
BIG thanks, adding the port 8080 solved my issue. Didn't see this in any documentation.
Smitty, were you able to get this to work also? The Audio Push Recieve to the phone works ok, but getting to record from the phone isn't. A file is created, but the message never gets sent to the phone to tell it to record. heres a bit of the pushlog. ???
<Push alert="1" type="audio" mode="normal" >
<go href="http://10.190.8.74:8080/AvayaPushSDK/servlet /Startpush" method="post">
...
I got the report from wireshark as below: No. Time Source Destination Protocol Info 31 13.173559 192.168.100.105 192.168.100.222 TCP [TCP segment of a reassembled PDU] Frame 31 (245 bytes on wire, 245 bytes captured) Ethernet II, Src: 00:1b:4f:14:fc:84 (00:1b:4f:14:fc:84), Dst: Usi_15:89:a1 (00:16:41:15:89:a1) Internet Protocol, Src: 192.168.100.105 (192.168.100.105), Dst: 192.168.100.222 (192.168.100.222) Transmission Control Protocol, Src...
I got the report from wireshark as below: No. Time Source Destination Protocol Info 31 13.173559 192.168.100.105 192.168.100.222 TCP [TCP segment of a reassembled PDU] Frame 31 (245 bytes on wire, 245 bytes captured) Ethernet II, Src: 00:1b:4f:14:fc:84 (00:1b:4f:14:fc:84), Dst: Usi_15:89:a1 (00:16:41:15:89:a1) Internet Protocol, Src: 192.168.100.105 (192.168.100.105), Dst: 192.168.100.222 (192.168.100.222) Transmission Control Protocol, Src...
Quote: Originally Posted by smitty50 Try SET TPSLIST 192.168.2.65:8080 That fixed my issue... i have a problem with display push. I can send topline or subscribe push without any problem, but display push always show 205 not in push state. what can i check?
Hello, I try to make the PushSDK to work. I've installed Tomcat version 6.0, deployed a sample application from PushSDK: push.war and made the following changes in the 46xxsettings.txt file: SET TPSLIST 192.168.2.65 - address of my Tomcat server SET PUSHPORT 80 SET PUSHCAP 222 Than I reboot my Avaya 9630 IP phone (firmware release 3.02) and try to send TOPLINE PUSH by passing text message. I receive the following error message: Could not...
Thread profile page for "PushSDK Tomcat Avaya 9630 not working" on http://avayausers.com.
This report page is a snippet summary view from a single thread "PushSDK Tomcat Avaya 9630 not working", located on the Message Board at http://avayausers.com.
This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity