VoIP/DID Inbound Problem.

Status
Not open for further replies.

wzaatar

Joined
Aug 1, 2007
Messages
90
Reaction score
1
Hello everyone,

I tried searching this issue in the forums, but didn't get any results. If it's redundant, I apologize and ask you to redirect me to the proper thread.

I have an "interesting" problem with a DID provider:

I have registered an account with a DID (DDI2.net), configured it on 3CX, works great outbound. On inbound, however it works for the first couple minutes and then if I dial my DID number again, it doesn't connect... However, if I dial out another number, then redial the DID back again.. It works for a couple more minutes but then dies back again.

Looks like the DID server needs some 'keepalive' mechanism?!?!

I'd appreciate if anyone can help with this issue.

Thanks,

Wadih
 
Are you using the latest build 3752?

Can you post server status log?

Also are you using a fixed IP? if the IP changes during the time of registration this will not work....
 
Hi,

Thanks for the prompt reply. Here goes the status log:

10:44:19.121 FaxCfg::updateContact :[CM504008]: Fax Service: registered as sip:888@3CXPhoneSystem with contact sip:[email protected]:5100;user=phone
10:44:18.810 StunClient::onInitTests :[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.23:3478 over Transport 172.16.1.2:5060
10:44:16.227 FaxCfg::updateContact :[CM504010]: Fax Service: unregistered contact sip:888:5100;user=phone
10:37:00.340 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:1000 forwards to DN:100
10:37:00.320 Call::Terminate :[CM503008]: Call(13): Call is terminated
10:37:00.300 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:1000 forwards to DN:100
10:36:18.560 CallCtrl::onLegConnected :[CM503007]: Call(13): Device joined: sip:[email protected]:8149
10:36:18.560 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:1000 forwards to DN:100
10:36:18.540 CallCtrl::onLegConnected :[CM503007]: Call(13): Device joined: sip:[email protected]
10:36:10.899 CallCtrl::onSelectRouteReq :[CM503004]: Call(13): Calling: Ext:100@[Dev:sip:[email protected]:8149]
10:36:10.899 Line::printEndpointInfo :[CM505003]: Provider:[DDI2] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Vox Callcontrol] Transport: [sip:172.16.1.2:5060]
10:36:10.899 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:1000 forwards to DN:100
10:36:10.869 CallCtrl::onIncomingCall :[CM503001]: Call(13): Incoming call from 0@(Ln.1000@DDI2) to [sip:100@xxxxxxxxxxxx:5060]
10:36:10.298 LineCfg::getInboundTarget :[CM503011]: Inbound office hours' rule for LN:1000 forwards to DN:100

I have just removed the real sip IP for my machine.
From the above, you can see that I'm running a server on a 172.16.1.0/24 subnet, server is .2 and client is .110 (Server is not fixed IP, but it has a static lease).

Also, I've just downloaded and installed the latest build. Still the same issue.

Thanks again!

Cheers,

W.
 
Hi again,

I found the problem. The VoIP provider needs a very short re-registration period to work. I adjusted it to 60 seconds and now it's working perfectly.

I would like to add it to the list of supported providers, if it's ok with you.

Cheers,

Wadih
 
Status
Not open for further replies.

Forum statistics

Threads
111,900
Messages
589,629
Members
164,765
Latest member
domi