We are testing VOIP service.

a provider has set us up with a DID and 3 Call paths for a SIP trunk.

We have configured IT 5.2.13 settings with all relevant information provided by the VOIP provider. Upon saving the config to our MCP based OS7200 (running 4.46d), the SIP Service Available option changes to Yes. at this point we can send and receive calls using the service without any problems.

After a certain amount of time (about 10-15 minutes), we suddenly lose the ability to receive inbound calls. Any inbound call gets an operator message that the call cannot be completed as dialed. Outbound calls can still be placed without issue.

Furthermore, if we enter IT 5.2.13 and Disable the service and then immediately reenable, we once again regain the ability to send and receive, until an additional 10-15 minutes has passed.

Has anyone encountered this before?

Is this a problem with the provider or with our configuration?

I am doing some additional testing to determine if the inability to receive calls only happens if no incoming calls are received or if it just strictly X amount of time from the initial connection.

Any insight would be greatly appreciated.

We have been having major issues with SIP on the 7030 and the 7200S, either dropping calls, service going unavailable, from our experience it depends on the SIP provider. Samsung Tech support has been of very little help. Who is the SIP provider?

The provider is Voxitas.

This problem has been narrowed down to approximately a 5 minute timeout. It only stops accepting inbound calls if an inbound call does not occur within 5 minutes.

Outside of this issue, we have not have problems with dropped calls, call quality, or service becoming unavailable.

Since the problem is no consistent, I feel it needs to be a configuration settings on our side or the side of Voxitas.

I have attempted to adjust all of the "timers" in 5.2.13 to be 250 (I assumed the times were in seconds making 250 be less than 5 minutes), however this has not hel[ped the situation.

I am hoping that touching base with Voxitas on Monday a solution will be reached if no one on this forum can suggest anything to correct the problem.

Might be worth a look with wireshark

Have you done the required port forwards in the router?

Specifically UDP 5060 to the MCP IP address.

Got your private/public settings correct for the MCP and MGI card?

Hi,

The problem was the port forwarding.

The firewall was automatically creating this PAT translation when the phone system initially registered, however, after the 5 minutes had past it would time out. Once a permanent static translation was entered, everything works as expected.

If its timing out after 5 mins, then in theory you could adjust your "trunk register time out" to be less then 5 mins.

But doing the port forward works definately