markh Posted April 15, 2010 Report Share Posted April 15, 2010 Just curious, does anyone have pbxnsip 4.x running on 2008 without issue? I've run into another issue and I'm starting to wonder if it's just not possible to get this config running. Is anyone running ocs r2 with pbxnsip 4.x on 2003 ok? should i just downgrade 3.x? This time round when I call an external #, if the external user answers the calls after 5 or so seconds, the ocs client doesnt acknowledge the answer and keeps saying 'calling' however the external caller hears silence. If the remote party answers the call within about 5 seconds, everything is ok. inbound calls do not experience this problem. [9] 2010/04/14 18:23:33: Message repetition, packet dropped [7] 2010/04/14 18:23:33: SIP Rx tcp:10.100.100.44:49455: PRACK sip:+9053614585@10.100.100.60:5060;transport=tcp SIP/2.0 FROM: <sip:+internal#;user=phone>;epid=0C4547F37F;tag=f3f0467ad7 TO: <sip:+external#@10.100.100.60;user=phone>;tag=5b7337002b CSEQ: 45 PRACK CALL-ID: 8956ea68-416d-47de-a96a-5173591cd18b MAX-FORWARDS: 70 VIA: SIP/2.0/TCP 10.100.100.44:49455;branch=z9hG4bK4741eef2 CONTENT-LENGTH: 0 USER-AGENT: RTCC/3.5.0.0 MediationServer RAck: 1 44 INVITE [7] 2010/04/14 18:23:33: SIP Tx tcp:10.100.100.44:49455: SIP/2.0 200 Ok Via: SIP/2.0/TCP 10.100.100.44:49455;branch=z9hG4bK4741eef2 From: <sip:+internal#@dc1-mediation;user=phone>;tag=f3f0467ad7;epid=0C4547F37F To: <sip:+external@10.100.100.60;user=phone>;tag=5b7337002b Call-ID: 8956ea68-416d-47de-a96a-5173591cd18b CSeq: 45 PRACK Contact: <sip:+internal#@10.100.100.60:5060;transport=tcp> User-Agent: pbxnsip-PBX/4.0.1.3446 Content-Length: 0 so this happens : [6] 2010/04/14 18:23:36: SIP TCP/TLS timeout on 10.100.100.44:49454, closing connection which then causes this error : [6] 2010/04/14 18:23:49: Response to 10.100.100.44:49455 must be sent over existing connection (10.100.100.44) ; 10.100.100.44 being mediation server. and the call is gone. Quote Link to comment Share on other sites More sharing options...
markh Posted April 15, 2010 Author Report Share Posted April 15, 2010 ok, I've tried the following. tried using the 2007 ocs mediation server. same problem. tried the mediation server on 2003. same problem. tried pbxnsip on 2003. same problem. All signs are pointing to a problem with pbxnsip ... same error in all configs : [6] 2010/04/15 10:44:32: SIP TCP/TLS timeout on 10.100.100.10:4335, closing connection update : just tested with 3.4 & the problem is gone, so as I suspected it is a problem in ver 4 ... however I can't use 3.4 because of the 30 second silence issue with ocs ... happy to test/troubleshoot with anyone to resolve this issue! Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 16, 2010 Report Share Posted April 16, 2010 Is there a route entry for sending messages with the 10.100.100.44 IP address that sends them via the loopback interface? That might cause grief, because OCS might have an issue dealing with sockets bound to the loopback interface. What is the output of "route print"? Quote Link to comment Share on other sites More sharing options...
polycom2080 Posted April 16, 2010 Report Share Posted April 16, 2010 Hi I had the same problem i got it working by changing the trunk setup set Request Timeout: to 10 and it should work fine(i think the sec to the old ver 3. wasn't working 100% and now they fixed it so you need to change the settings ) let me know if it worked for you Quote Link to comment Share on other sites More sharing options...
markh Posted April 16, 2010 Author Report Share Posted April 16, 2010 Hi I had the same problem i got it working by changing the trunk setup set Request Timeout: to 10 and it should work fine(i think the sec to the old ver 3. wasn't working 100% and now they fixed it so you need to change the settings ) let me know if it worked for you thank you for replying. I know it's right in front of me, but I can't find the setting can you (or anyone) tell me where to find this setting? Quote Link to comment Share on other sites More sharing options...
pbx support Posted April 16, 2010 Report Share Posted April 16, 2010 thank you for replying. I know it's right in front of me, but I can't find the setting can you (or anyone) tell me where to find this setting? In order to see the "Request Timeout" field on the trunk, first you need to change the "Failover Behavior" setting on the trunk page. Quote Link to comment Share on other sites More sharing options...
markh Posted April 21, 2010 Author Report Share Posted April 21, 2010 ok I tried this setting, didn't fix the problem. I tried it on both the sip trunk and the ocs trunk. Downgrading back to ver 3 .. any other ideas? Quote Link to comment Share on other sites More sharing options...
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.