[OpenSIPS-Users] Preload Route denied for SIP REGISTER. Why should I use an alias? What is the fundamentals behind it?

Rodrigo Pimenta Carvalho pimenta at inatel.br
Mon Dec 7 20:26:02 CET 2015

Dear OpenSIPS-users.

I'm working with OpenSIPS and softphones successfully, since some months ago. All my softphones can register on OpenSIPS very well.

All was ok while this SIP proxy and the softphones was all running in the same local network.

Today, I have just created  a new isolated network and I put my OpenSIPS there. That is, now my OpenSIPS is behind a NAT from the point of view of all softphones. In this case, when a softphone tries to register on OpenSIPS, it get the answer: "Status: 403 Preload Route denied".

I have studied about this issue today (RR Module) including the answer found here: http://comments.gmane.org/gmane.comp.voip.opensips.user/24120 .

According to that answer I could comment, in opensips.cfg file,  the part that uses the function loose_route(). However it caused the "too many hops" problem.

Then, after reading more discussions, I have put an alias in my OpenSIPS.cfg script. It solved the issue, but I'm not sure if it is a good solution.

Could someone explain a bit about the issue I'm dealing with, please? I'm missing some fundamentals here, for sure. What could be an alternative solution?

Is there some way of "fixing" some header in the SIP REGISTER request, by means of OpenSIPS, so that it could accept the SIP REGISTER without issues?

Any hint will be very helpful!!

Thanks alot!

Inatel Competence Center
Ph: +55 35 3471 9200 RAMAL 979
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20151207/810af67f/attachment.htm>

More information about the Users mailing list