I’m very new to asterisk and freepbx and I was able to create a working voip, however I do have some issues with some devices.
I am trying to create a local VOIP network.
I’m getting this error “Endpoint ‘anonymous’ (:5060) has no configured AORs” and I found out that the client VOIP device is trying to REGISTER with SIP URL that contains prefix “+63”.
There’s no way to edit or remove the + sign on the SIP account settings on the client device, so only way is to do it within asterisk or freepbx.
I tried creating extensions with “+63” prefix but it won’t let me add the + sign at the beginning.
Is it possible to allow SIP connections with + on the username or SIP URL? How can this be done?
Thanks in advanced.
I’ve never heard of that. Do you not have the ability to configure the device (for example you don’t know the admin password), or is the prefix somehow hard coded in the firmware? Device make/model? How many of these do you have?
If you really are stuck with this situation, you should be able to configure them as trunks, rather than extensions. If they just need to make and receive calls, this is pretty easy. If you need other extension capability (voicemail, forwarding, etc.), you may be able to use a custom extension and a trunk.
Alternatively, you could set up these devices as extensions in Asterisk using custom config files, rather than using the FreePBX GUI.
Yet another option may be to use a small amount of custom dialplan to rewrite the source and destination numbers, depending on the details of what the devices allow.
I have more than 40 units of ONUs (HG6245D) where the prefix is hardcoded in firmware, it only allows me to change the sip server/port and the sip number and password. I also have few ZTE F670L and they are working fine since it does not add +63 prefix when doing registration with SIP.
Thanks for suggesting about trunks, i’ll try that method.
Hello @Stewart1 ,
I’m not successful in using them as Trunk.
The only way I can have the endpoints registered is by manually editing the conf file and add individual extension with the “+63” added in the username, but those modifications will be wiped out if I made changes on the freepbx GUI.
Here is the registration I get:
<--- Received SIP request (452 bytes) from UDP:172.16.30.151:5060 --->
REGISTER sip:10.0.31.254 SIP/2.0
From: "+63900003"<sip:[email protected]>;tag=afd265c0-971e10ac-13c4-6a6f2-5dc11640-6a6f2
To: "+63900003"<sip:[email protected]>
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 172.16.30.151:5060;branch=z9hG4bK-6a6f2-19fc231b-77445fc9;rport
Contact: <sip:[email protected]:5060>
<--- Transmitting SIP response (585 bytes) to UDP:172.16.30.151:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.16.30.151:5060;rport=5060;received=172.16.30.151;branch=z9hG4bK-6a851-1a017eb5-5bad87fd
From: "+63900003" <sip:[email protected]>;tag=afd26cc0-971e10ac-13c4-6a851-68b9aec4-6a851
To: "+63900003" <sip:[email protected]>;tag=z9hG4bK-6a851-1a017eb5-5bad87fd
CSeq: 5 REGISTER
WWW-Authenticate: Digest realm="asterisk",nonce="1691905203/b82e7ff367c40e86f349f9455eb47ad0",opaque="350365177e60d84b",algorithm=MD5,qop="auth"
Can you help me if there is a workaround in creating extensions that accepts “+63” prefix for the username?
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.