@ sign in Authentication ID

[djtec3]

Hi,
I have a problem to register to my SIP Provider (T-Mobile) via 3CX. The problem concerns register name: [email protected]-mobile.pl.
Register request is incorrect:
<sip:+48number%[email protected]-mobile.pl>
Any suggests?
Kind regards
Robert

 

[leejor]

Please post a shot of your trunk settings page. X out part any private information. Where is vpabx.ims.t-mobile.pl used? You must have put it in somewhere. It would seem that it is being added to the correct URL.

 

[djtec3]

Hi,
I would like to add this SIP Provider credentials are working fine in other vpbxes.
Above my 3X pbx settings:

 

[leejor]

Could it be because you have included a URL in the Authentication ID?

 

[djtec3]

Yes. Register name is an URL format. Provider deliver that format and I can use it in other VPBX.
Register request in that case looks fine.

 

[leejor]

In your initial post, you have shown two examples with a URL...which is correct? The second example would seem to have addition information (two URLs).

 

[djtec3]

This is request output capter from 3CX:
From: <sip:+48number%[email protected]-mobile.pl>
Answer SIP server: Internal error.
I am pretty sure that the problem is incorrect format in FROM header.

 

[djtec3]

Output from my Asterisk:
REGISTER sip:vpabx.ims.t-mobile.pl SIP/2.0
| Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK047fa8a9;rport
| From: <sip:[email protected]-mobile.pl>;tag=as61c47ad3
| To: <sip:[email protected]-mobile.pl>
| Call-ID: 0001c3bf4d45e87a688d16ec7dc30314
| CSeq: 111 REGISTER
| User-Agent: Slican IPM
| Max-Forwards: 70
| Expires: 120
| Contact: <sip:[email protected]>
| Event: registration
| Content-Length: 0

 

[leejor]

In ascii %40 = @
See...
https://www.3cx.com/community/threads/cant-get-correct-registration-string.50828/

 

[djtec3]

3CX support replay:
"The only thing i can recommend is to use a supported provider that will never require a special character in the Auth ID field. " is totally unacceptable.
@ sign can be used in Auth ID from almost 2 years. Many providers acepts registration only with that format Auth id.

 

[leejor]

Many providers acepts registration only with that format Auth id.

Unfortunately it seems, none, that are supported by 3CX.

 

[YiannisH_3CX]

Try to register to the provider using only the number in the auth id section and see if that works. The PBX will append the registrar value to the number creating the URL.
If that fails then replace the registrar value in your trunk settings with "ims.t-mobile.pl"

 

[djtec3]

Hi YiannisH_3CX,
Uunfortunately it doesn't work. Any other workaround at this issue?

 

[JohnS_3CX]

Run a capture after changing it as @YiannisH_3CX said, see whether the PBX sends it like the example in post #8

The %40 should go away in this case

This article explains where the PBX takes each value to build the FROM header
https://www.3cx.com/docs/sip-trunk-registration-authentication/