moh10ly Posted January 30, 2013 Report Posted January 30, 2013 We have managed to get SnomOne integrated with our on-premise Lync and the user which is assigned to SNOM ONE PBx is currently able to make calls but sometimes the presence doesn't change to In a Call. it works for 15 mins then it doesn't work. Any one had similar issue ? Thanks Quote
Vodia PBX Posted January 30, 2013 Report Posted January 30, 2013 The PBX registers with Lync. Is that registration still alive? You should be able to see that on the Lync side. Maybe there is a problem with the keep-alive of the connection. Quote
moh10ly Posted February 1, 2013 Author Report Posted February 1, 2013 The PBX registers with Lync. Is that registration still alive? You should be able to see that on the Lync side. Maybe there is a problem with the keep-alive of the connection. Hi there, there's no indication that registartion still alive however, when you make calls it works normally. How/Where do I check what's the current white space keep alive time ? I couldn't find any command or any option for that Do you mean performance in this snapshot? http://wiki.snomone.com/images/5/53/Systempreformance.jpg thanks Quote
Vodia PBX Posted February 1, 2013 Report Posted February 1, 2013 No the performance is not the point. This looks like a keep-alive problem. Can you put the IP address of the Lync server into the SIP logging field, so that you can see all traffic between the PBX and Lync? Quote
moh10ly Posted February 1, 2013 Author Report Posted February 1, 2013 No the performance is not the point. This looks like a keep-alive problem. Can you put the IP address of the Lync server into the SIP logging field, so that you can see all traffic between the PBX and Lync? I thought so, but do you mean in the sip address where it says sip:domain.com ? or where you enter the sip user address? Thanks Quote
Vodia PBX Posted February 1, 2013 Report Posted February 1, 2013 If you put just the IP address there, then the SIP packet will be sent on UDP transport layer (wasn't our idea, check the RFC). However Lync does not support UDP. Try something like sip:192.168.1.2:5060;transport=tcp. But you might have to use DNS, if the Lync server does not accept the IP address as the destination address. Quote
moh10ly Posted February 4, 2013 Author Report Posted February 4, 2013 If you put just the IP address there, then the SIP packet will be sent on UDP transport layer (wasn't our idea, check the RFC). However Lync does not support UDP. Try something like sip:192.168.1.2:5060;transport=tcp. But you might have to use DNS, if the Lync server does not accept the IP address as the destination address. Tried that but Lync presence doesn't work at all in this case. I will test with Lync 2010 and let you know. I get the following on Log on Snom One PBX [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 80 for HTTP/HTTPS [0] 2013/02/04 13:58:55: TCP(IPv4):Could not bind socket to port 443 on IP 0.0.0.0 [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 443 for HTTP/HTTPS [0] 2013/02/04 13:58:55: (IPv6)Could not bind socket to port 443 on IP [::] [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 443 for HTTP/HTTPS thanks Quote
Vodia PBX Posted February 4, 2013 Report Posted February 4, 2013 I get the following on Log on Snom One PBX [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 80 for HTTP/HTTPS [0] 2013/02/04 13:58:55: TCP(IPv4):Could not bind socket to port 443 on IP 0.0.0.0 [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 443 for HTTP/HTTPS [0] 2013/02/04 13:58:55: (IPv6)Could not bind socket to port 443 on IP [::] [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 443 for HTTP/HTTPS thanks That's happening when you restart the service in Linux (not related top Lync). The sockets are not available immediate, but after one minute or so the PBX is able to get the ports. Quote
moh10ly Posted February 4, 2013 Author Report Posted February 4, 2013 Tried that but Lync presence doesn't work at all in this case. I will test with Lync 2010 and let you know. I get the following on Log on Snom One PBX [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 80 for HTTP/HTTPS [0] 2013/02/04 13:58:55: TCP(IPv4):Could not bind socket to port 443 on IP 0.0.0.0 [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 443 for HTTP/HTTPS [0] 2013/02/04 13:58:55: (IPv6)Could not bind socket to port 443 on IP [::] [0] 2013/02/04 13:58:55: FATAL: Could not open TCP port 443 for HTTP/HTTPS thanks OK, Here's an update. I have tried with Lync 2010 and the result was positive. the presence works and stable. I think the issue is probably related to Lync 2013. Is there any news about a fix or an update to fix this issue soon? this is kind of urgent project. Thanks Quote
Recommended Posts
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.