SIP Trunk setup sends wrong username/password

[disconv]

Hello,

I am trying to connect to my Weepee account but weepee always receives the wrong username password.

In dashboard I can see this the image attached.
But 10001 is not the username I am putting in config.
Should this be the username


"Call or Registration to Weepee has failed. sip:[email protected]:5060 replied: 403 Forbidden".

But nowhere did I put in 10001 as username :s

 

[eddv123]

10001 is the "back-ground" trunk ID, designed so that if you set up multiple trunks 3CX knows who is who (like extension numbers sort of).

If this is a registration based trunk (you register with a username and password) then generally it should be:

Type of Authentication - Register/Account based.
Authentication ID - Username
Authentication Password - password.

The Authentication ID and password will be what the provider have given you. Your issue may not even be related to these credentials and could be something else.

Can you first confirm the trunk type, and if Register based the trunk registers green in the trunks list (FYI if IP authenticated it will show green regardless).

 

[StefanW]

Adding this into the mix: https://www.3cx.com/docs/weepee-belgian-sip-trunk/

 

[FS_Mathieu]

Hello @disconv

I don't know much about Weepee but take care that the trunk isn't pointing an unique public IP.

 

[disconv]

Hello,

when looking at pcap, we noticed username is correct; But appearently there is no IP given to Weepee. They say it could be a NAT issue. Nu maybe it's in Google Cloud then. Although the setup was done with PBX express and IP address in Google Cloud is fixed. This is also given in 3CX as fixed.

 

[disconv]

The Request gets to Weepee, because they always block the 3CX (google) external IP with message "wrong username / password" but it could be something else and their message might not be correct. I am sure the username and password are correct because I can connect from a normal softphone app. So either it's 3cx, or Google Cloud.

 

[eddv123]

As per the guide posted "At this point if you refresh the page you should see your Weepee Trunk appear as Registered. "

So this is a registration based trunk. Although rare in my experience some providers do require a username and password and your public IP configured on the platform for security.

I can connect from a normal softphone app

The app can connect to what ? 3CX or to make external calls ?

 

[disconv]

As per the guide posted "At this point if you refresh the page you should see your Weepee Trunk appear as Registered. "

So this is a registration based trunk. Although rare in my experience some providers do require a username and password and your public IP configured on the platform for security.



The app can connect to what ? 3CX or to make external calls ?

It can connect to Weepee, so the weepee Sip Trunk is working and username and password are correct.

I checked with them and IP address is not needed. Only username and password.

 

[eddv123]

So in answer to my question - is the issue in regards to outbound/external calls ?

 

[disconv]

So in answer to my question - is the issue in regards to outbound/external calls ?

Yes, it's the only SIP Trunk I'm trying to set up and it's this one that is not registering.
Everything else seems to be working fine (internal calls etc). It's just the SIP Trunk connection to WEEPEE that is not working.

 

[eddv123]

Thanks for confirming.

Internal calls will work without a SIP trunk so ignore that part. If it were me I would run a PCAP from 3CX https://www.3cx.com/docs/capture-network-traffic/ and confirm for sure why the provider is rejecting the Registrations.

I checked with them and IP address is not needed. Only username and password.

When speaking to them did they confirm for definite that the username and password were definitely the issue here as there are other elements that could cause your error.

The most common reasons for this error:

- The username and / or password are wrong;

- The server is requiring an authentication username and password and none have been provided;

- The user is not allowed to call the destination (or is using the wrong international dialing prefix), or there is insufficient account balance;

- The phone is trying to register too fast and the server has blocked the phone for that reason;

- You are trying to register multiple devices at once and the server is blocking the phone for that reason;

Feel free to PM me the PCAP if you want me to take a look over.

 

[FS_Mathieu]

Something makes me doubtfully :

Our trunk is answering with the public IP of trunk server, not with a fullname + port 5060..

 

[disconv]

Something makes me doubtfully : View attachment 14229

Our trunk is answering with the public IP of trunk server, not with a fullname + port 5060..

this is the server i need to connect to according to Weepee. I did send them a pcap already and from this they said that they do not see any IP address beeing sent and it might be a NAT issue.

 

[eddv123]

And have you checked the PCAP yourself to see what (if anything is being sent). If it is a NAT issue have you checked the firewall infront of 3CX and what is the brand.

There are settings on the trunk that may help, for example "Put Public IP in SIP VIA Header" https://www.3cx.com/docs/sip-trunk-options/ however if you have a NAT issue your firewall should be addressed https://www.3cx.com/blog/voip-howto/firewall-nat-pat-stun/

Does your 3CX firewall checker pass ?

 

[disconv]

Yes the firewall checker passed.

I could see it beeing sent in PCAP, however I don't have enough knowledge to be sure. I could see in PCAP that the username was sent correct however, so that's not the issue.

I tried with the Put Public IP in SIP VIA Header option but isn't working either. I will however take a new PCAP and send it to them again now to see if they see the IP. If not, it might be a NAT issue. Hosting is done on Google Cloud and was installed through PBX Express. Am I wrong to suppose that installation should be correct then?