Fanvil Dual SIP Accounts?
-
I use option 66 in GHCP to setup provision in this Fanvil X5U phone and it works well.
I have added the credentials and ip address to the Line Registration settings page for a second SIP PBX. It won't register. I get a "Failed with 403" error.
The second line register just fine with the info for the first pbx, so I know I am filling in the fields properly.
My questions are:
Is the phone only able to register with the server assigned by DHCP Option 66 when we use option 66?
Am I missing a setting somewhere to turn this on?
Does the second SIP server have to be on another port, ie; 5062?Thanks.
-
@JasGot said in Fanvil Dual SIP Accounts?:
Is the phone only able to register with the server assigned by DHCP Option 66 when we use option 66?
Registration has zero to do with configuration (other than knowing you have the config file correct).
-
@JasGot said in Fanvil Dual SIP Accounts?:
Does the second SIP server have to be on another port, ie; 5062?
No. This is outbound from the phone. Does every website need to be on another port?
-
I have a X4U on my desk. It is configured by DHCP option pointing to my PBX.
The config contains only 1 line and everything works.
I can add a second line in the web GUI and it registers.
-
@JaredBusch Must be an issue at the PBX. I'll look into that next.
-
@JaredBusch Thanks for the screen shot, it made me know I was setup at the phone correctly. It turned out to be some settings at the PBX, then a block in fail2ban, then an issue with the device mapping.
With the help of the PBX support, it is all sorted out now!
-
@JasGot said in Fanvil Dual SIP Accounts?:
@JaredBusch Thanks for the screen shot, it made me know I was setup at the phone correctly. It turned out to be some settings at the PBX, then a block in fail2ban, then an issue with the device mapping.
With the help of the PBX support, it is all sorted out now!
That does not sound likely. If the second PBX was working already, why would there be some setting that needed changed there? The
fail2banblock is understandable if you were failing to log in and caused it to kick in. -
@JaredBusch said in Fanvil Dual SIP Accounts?:
That does not sound likely. If the second PBX was working already, why would there be some setting that needed changed there? The fail2ban block is understandable if you were failing to log in and caused it to kick in.
For reasons I don't exactly recall (something to do with PJSIP a year and a half ago) the ports were set to 5062 and the phone was set to 5060. Also, it turns out there were two places the port needed to be changed from 5062 to 5060 in the PBX, once that was set correct things started to improve.
Not exactly sure why the fail2ban triggered. I know the user id and password were correct when I was setting it up. But I did, while troubleshooting, change the user id and server ip to another identical pbx, perhaps, during this change, I bumped the original server with the wrong user id too many times while making changes.
Then I had to change the port at Skyetel because it too was 5062.
Everything is on port 5060 now and it is singing right along! One phone, two different systems just like your video clip.
