(PASSTHROUGH): Can't send RTP stream to 127.0.0.1:14064 dest

[capt]

Hi guys;

So, we've been working on evaluating the 3cx free version for our business and while most everything went smooth we've come to a point where we definitely need some outside support.

To give a quick overview of the system:

Windows 7 Professional 64 Bit
Sangoma A200 Card with Echo Cancellation and 4x FXO Ports
Latest Build of 3CX Free Version Installed
At the moment, hooked up to 2x Yealink T28's

Configuration of the T28's is as follows:

1x Digital Receptionist at Extension 800
2x Employee Extensions (100 and 101)
3x Department Extensions (200, 201 and 202)

Each of the Yealink Phones is configured with 2x 100 and 101 extensions as well as all three department extensions.

Error description:

When we first restart the server it will take forever for the phones and extensions to register (up to 20 minutes). During this time extension routing will be extremely flaky - Around 50% of the times the system will connect properly to the extensions, whereas the other 50% of the time we get a voice prompt telling us that the destination is unreachable, no routing available, extension isn't registered, etc....

After around 20 minutes the voice prompt will fail, giving us the RTP error. Once this occurs extension and call routing will work 100% of the time.

The log from 3CX shows the following: 00:28:43.954 [MS004000] C:34.1: (PASSTHROUGH): Can't send RTP stream to 127.0.0.1:14064 destination unreachable (10049)

Any and all help in solving this issue would be greatly appreciated as we are already way behind schedule on our phone system rollout!!

 

[capt]

Re: (PASSTHROUGH): Can't send RTP stream to 127.0.0.1:14064

Anyone? :O

 

[capt]

Re: (PASSTHROUGH): Can't send RTP stream to 127.0.0.1:14064

Since its really REALLY difficult to use the PBX with the current problem - Some sort of input would be dearly appreciated. Thank you!

 

[leejor]

Re: (PASSTHROUGH): Can't send RTP stream to 127.0.0.1:14064

When you first start/re-start the server, it can take up to 290 minutes for devices to register. that is because the re-registration time is 30 minutes. So if a set registered 10 minutes ago and you shut down 3CX, the set will not know to register for another 20.

In the meantime, the set will probably be able to place calls, but not receive them.

If you re-start 3CX, reboot (power down/power up) the sets as soon as the server is back up.

Restarting the server is not something that should normally be happening on a daily basis during business hours.