Forums Read-only archive

Port Allocation failed 486

10 posts · Brekeke PBX Forum

teo_teo Original post
1. Brekeke Product Name and version:
Brekeke PBX, Version 2.2.6.2 , Pro
2. Java version:
1.6.0_11
3. OS type and the version:
linux 2.6.18-92.el5
4. UA (phone), gateway or other hardware/software involved:
LinkSYS SPA922
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :

6. Your problem:
Today i started receing the following error
Port Allocation failed 486.
As soon i restarted the server it was gone. What exactly this message mean?Will it appear again? As i was maiking a call, the other party when answeared the call, i was getting this error and call ended send by pbx.
hope
where was "Port Allocation failed 486." shown?
on the phone LCD?

Did you set "SIP port" under the ext on the phone?
teo_teo
Port Allocation failed 486 was shown on PBX call logs.
Nothing was shown under the ext on the phone, just call ended.
Harold
Hi
I think you need to expand the range of RTP port in the SIP Server.
Refer the RTP port settings in the SIP Server document.
teo_teo
Thank u for your reply,

The number of RTP port range is already far bigger than number of users. Also after I rebooted linux , i did not experience this again and when it happend, 7 out of 10 calls had this type of Port Allocation failed 486 error. I dont know what to say. I will change it and see if happens again.
Harold
Hi
Are you using RTP-Relay at the SIP Server? Let you set it to "auto".

How many concurrent calls?
Are there any VIDEO calls?
What kind of SIP client are users using?
teo_teo
Thank u for your reply,

RTP-Relay is ON.
How many concurrent calls?
Max 12 calls
Are there any VIDEO calls?
No,
What kind of SIP client are users using
Linksys IP IPHONE spa922,SPA942
Harold
Hi
Which port range are you using for RTP at the SIP Server?
If you disable RTP-Relay, does the issue happen still?
teo_teo
Hi,

Which port range are you using for RTP at the SIP Server?
10000-10999
If you disable RTP-Relay, does the issue happen still?
As i said only one time this problem happened and It would be very
helpful if I knew if it was PBX problem or maybe Linux.
Because server is in production mode when It is possible I will try it.

Thanks
Harold
teo_teo

Do you still experience the same problem?

I don't know the problem is related with PBX or Linux.
But I've never experienced such a problem from my PBX on CentOS.
Which Linux distribution are you using?