Pjsip trunk with @ in username

Hello,
i have start to move my trunks to pjsip.
One of my providers use the symbol @ in the username. So the username is like a email (for example 48845458@myprovider.com)
However as far i have see in my tests in pjsip the @ is not allowed in username.
How i can solve this? It is any way to bypass this?
Thank you

@ in URIs should be encoded as %40. If they actually want @ over the wire, find a provider that implements SIP.

in URI @ is with user name
how do i pass @ with username in PJSIP “ps_registrations”?

i got an error with %40
(WARNING[2908]: res_pjsip_outbound_registration.c:1197 handle_registration_response: Fatal response ‘400’ received from ‘sip:+917314895400%40ims.airtel.in@10.232.145.146:5060’ on registration attempt to ‘sip:192.168.1.247:5060’, stopping outbound registration
)

with @ user name i got an error
( res_pjsip_outbound_registration.c:1636 sip_outbound_registration_regc_alloc: Invalid server URI ‘sip:+917314895400@ims.airtel.in@10.232.145.146:5060’ specified on outbound registration)

here +917314895400@ims.airtel.in is username

Username doesn’t go in the server URI. The server URI is how the server is reached, such as:

sip:10.232.145.146

Which means to contact that IP address. The username usually doesn’t contain @, what that generally means is the domain which would be client_uri for a registration:

sip:+917314895400@ims.airtel.in

i am using PJSIP real time

now i got an error
(res_pjsip_outbound_registration.c:1197 handle_registration_response: Fatal response ‘486’ received from ‘sip:10.232.145.146:5060’ on registration attempt to ‘sip:+917314895400@ims.airtel.in’, stopping outbound registration)

i am using registration string with SIP it’s working on it
registration string is - +917314895400@ims.airtel.in:password:+917314895400@ims.airtel.in@10.232.145.146/+917314895400

You could provide a SIP trace from chan_sip and someone may provide guidance. Your provider is basically reusing cellular IMS infrastructure for SIP, so it’s very much off in an unusual world.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.