[Nov 21 20:09:01] NOTICE[9069][C-0001689e]: chan_sip.c:29713 sip_request_call: Conflicting extension values given. Using ‘823************’ and not ‘01342244560’
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
– Called SIP/823*********:5************@78.11.22.33/01342244560
[Nov 21 20:09:01] NOTICE[12287][C-0001689e]: chan_sip.c:22914 handle_response_invite: Failed to authenticate on INVITE to ‘“Leandro Dardini” sip:100@91.11.22.33;tag=as1c0d8470’
– SIP/78.11.22.33-000144c3 is circuit-busy
== Everyone is busy/congested at this time (1:0/1/0)
Which is the correct syntax to use to dial directly with username and password?
I stand corrected. However, user@domain and domain/user are two alternative ways of specifying the same thing. Both set the user field in the request URI. That’s why it is complaining.
Most system authenticate on the From header user.
Before you can go any further, you need to tell us exactly what fields in the SIP request you want to be set to which value.
You may have to push set(CALLERID(…) to the limit.
Your provider doesn’t seem to need a user for INVITE, as defaultuser is for incoming registrations. They may require that you register before you send INVITE, in which case you will have to use sip.conf for the registration.
If defaultuser should have been fromuser, you will need to set CALLERID(num) to the user value.
it works for me as well as long as host=ip of the carrier.
The carrier expects Authentication and number@domain in the to: field.
The Domain unfortunately doesn’t resolve so I added it to /etc/hosts
Adding the domain to the host= sends the correct domain, but ignores the port.
The Solution:
set host=ip
use ! after the dial to send a different to:
Dial(${TESTTRUNK}/${EXTEN}!${EXTEN}@domain,To)