We're running into an issue with phone calls between sipX and Avaya terminate after 30 minutes. My colleague has observed that the Avaya will refresh the session according to its "Preferred Minimum Session Refresh Interval." Avaya sends an Invite packet to sipX using TCP/5060 (packet 50 below). sipX responds with a Trying 100 packet on UDP 5060 (packet 52). Avaya doesn't support SIP over UDP. The call terminates because the SIP conversation doesn't take place properly.
Here's a sanitized packet capture: "50","124.018306","Our_Avaya","Our_sipX","SIP/SDP","Request: INVITE sip:u...@some_workstation:61154;x-sipX-nonat, with session description" "51","124.018532","Our_sipX","Our_Avaya","TCP","sip > 11369 [ACK] Seq=1 Ack=1264 Win=364 Len=0 TSV=3724996432 TSER=52502151" "52","124.019525","Our_sipX","Our_Avaya","SIP","Status: 100 Trying" "53","124.019806","Our_Avaya","Our_sipX","ICMP","Destination unreachable (Port unreachable)" "54","124.131581","Our_sipX","Our_Avaya","SIP/SDP","Status: 200 OK, with session description" "55","124.131991","Our_Avaya","Our_sipX","ICMP","Destination unreachable (Port unreachable)" Is it possible to work around this now? If not, can this be a feature request? -- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman "The system's broke, Hank. The election baby has peed in the bath water. You got to throw 'em both out." --Dale Gribble "Those who vote decide nothing. Those who count the votes decide everything.” --Joseph Stalin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
