I have an NEC SV9100 that I have set up totally as VOIP. I have 8 statiions and 8 SIP trunks. I can call out on the SIP trunks no problem. But incoming calls do not ring through unless I first use the system to make an outgoing call. To further explain, when you first arrive in the morning after the system has not been use overnight, callers will hear that "your call did not go through..." If you now make an outgoing call, you can then start receiving incoming calls. After not too long you will once again not be able to receive incoming call. The SIP trunk service is Edge Communications which is the NEC SIP trunk provider. Not sure if there is some kind of "Keep Alive" feature I need to turn on or maybe something else.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NEC SV9100 Incoming calls to SIP Trunks not going through
- Thread starter flashtel
- Start date
Sounds like you are missing port forwarding settings on the router. When you make an outbound call, the router leaves the ports open for a period of time waiting for a reply. This is the time period your inbound calls work. After the timeout the ports close and the router starts ignoring the inbound packets so your inbound calls stop working. Call forward 5060 UDP (or whatever SIP port your carrier is using) to the IP address in 10-12-09 and port forward 10020-10083 to the IP address in 84-26.
(The base port in 84-26 is 10020 and you need two ports per call. So the first call uses 10020-10021, the second call uses 10022-10023, etc. 10020-10083 gives you up to 32 calls. If you have more than 32 trunks you'd need to make that range bigger)
(The base port in 84-26 is 10020 and you need two ports per call. So the first call uses 10020-10021, the second call uses 10022-10023, etc. 10020-10083 gives you up to 32 calls. If you have more than 32 trunks you'd need to make that range bigger)
- Thread starter
- #4
- Thread starter
- #5
Hmm... It "works" after you make an outbound call. This says that you're programming is basically correct. It can't be that you forgot the inbound DID entry.
What you are experiencing still points toward the router. There isn't anything changing on the SV9100. If it gets the packets inbound works, if it doesn't get the packets that intercept message is the normal response without a failover destination set by the SIP carrier.
Either your registration with Edge is expiring and Edge no longer knows where to send the inbound calls, or the router isn't passing the traffic to the SV9100. 10-29-15 is the registration expiration timer. You can shorten that to test and see if it makes a difference. (Change it back when you are done unless it fixes the problem in which case you should call Edge. Some carriers don't want excessive registration packets and have longer expiration timers intentionally.) I don't suspect this is your issue.
Since inbound works you basically know that your SV9100 programming is likely correct. Your problem is getting the SIP traffic to the SV9100 which is a networking issue and most likely the router. Unfortunately that seems like it is out of your control. Do they have multiple static IP addresses? Could you try a different router?
What you are experiencing still points toward the router. There isn't anything changing on the SV9100. If it gets the packets inbound works, if it doesn't get the packets that intercept message is the normal response without a failover destination set by the SIP carrier.
Either your registration with Edge is expiring and Edge no longer knows where to send the inbound calls, or the router isn't passing the traffic to the SV9100. 10-29-15 is the registration expiration timer. You can shorten that to test and see if it makes a difference. (Change it back when you are done unless it fixes the problem in which case you should call Edge. Some carriers don't want excessive registration packets and have longer expiration timers intentionally.) I don't suspect this is your issue.
Since inbound works you basically know that your SV9100 programming is likely correct. Your problem is getting the SIP traffic to the SV9100 which is a networking issue and most likely the router. Unfortunately that seems like it is out of your control. Do they have multiple static IP addresses? Could you try a different router?
- Thread starter
- #7
- Status
