Fastweb credentials & settings

[vizeta62]

Fastweb mi ha fornito le credenziali per il suo servizio VOIP, tuttavia il suo registrar (voip.fastwebnet.it:5060) pare non rispondere neppure alla richiesta di registrazione del TRUNK:

11/27/2020 12:53:14 PM - [CM504005]: Registration failed for: Lc:10002(@Fastweb[<sip:[email protected]:5060/UDP>]); Cause: Cause: 408 Request Timeout/REGISTER from local

Ho già cercato questo forum con la KW "FastWeb" ma il post più recente è di 10 anni fa; e comunque non trovo nulla di pertinente.
Qualcuno sa se sia effettivamente possibile utilizzare un TRUNK Fastweb, oppure se vi sono delle "barriere tecnico-commerciali nascoste" ?

 

[NickD_3CX]

Hi there,

I hope you don't mind me replying in English. There are not technical barriers using any provider, so I hope you see now one of the benefits of using a 3CX Supported Provider.

Anyhow, even though the message says "from local", there is a good chance that your provider is not responding to your REGISTER request.

My advice would be, start capturing with Wireshark, then restart the 3CX SIP Server and wait until it has restart. Stop the capture and check for REGISTER messages to the IP of the Provider (you can use Wireshark filter: sip.CSeq.method==REGISTER ).

If the PBX is sending the REGISTER and you are not getting any responses, then you would need to contact the provider.

 

[vizeta62]

English is fine. Thank you for your answer. I have already used Wireshark and I can confirm the registrar sends non answer whatsoever. So I'm sure too it's a provider issue. FastWeb is quite stingy with information....just to say so..... My question was in italian because mabe only an italian user (or Fastweb User) may have an answer.

 

[vizeta62]

("just to say so" == "so to speak") my English is not so good......

 

[vizeta62]

Hi to all !!!
I am very happy to say that I found a workaround to this issue. I am quite sure it depends on Fastweb and NOT on 3CX.
But anyhow, I wish to convert this little & specific, use case into a more general and clear knowledge for all to whom it may turn out to be useful in some way, including myself, first of all

I succeded in REGISTERING to the Fastweb SIP service from an old SIP phone (Thomson ST2030) with no effort whatsoever.

So it seems clear that the Fastweb Registrar is able to tell (distinguish, I mean) a VOIP extension registerig to a PBX, from a PBX trying to set up a trunk. (Let my remind the reader that the Fastweb Registrar will give NO response at all to my 3CX trying to register.)

Having this said, I admit I used to believe that, for what concerns the registration phase only, the SIP interface between extension and PBX il the same as the one between PBX and Registrar; as far as I know, in both cases we have a SIP UA that is interfacing with another SIP UA. But maybe this in NOT the case !

Put it in other words: should I expect a standard-compliant SIP registrar to let both an extension and a PBX register as well? Or mabe should the registering part specify different options in each case? Should I rather assume that Fastweb REGISTRAR is using some SIP or nerworking trick to selectively ban my PBX?

Please, if anybody has a good knowledge about SIP, may she/he explain where I am wrong or right in my hypotesys, and what is happening actually to my case?

Thanks a lot !!!

 

[NickD_3CX]

Technically speaking a phone and a PBX, when registering, do exactly the same thing.
But the fact that you have found a device that registers can help you.
If you can, make a capture of the phone that registers successfully and find the REGISTER message in Wireshark.

Then, you could try and reverse engineer it to make 3CX send the same information.

 

[vizeta62]

Ok! Thank you very much! ....at least I was not so wrong from a theoretical standpoint.....