Just for laughs, I put this into MicroSIP:
and was astonished to find that it sent:
REGISTER sip:10.232.142.146 SIP/2.0
Via: SIP/2.0/UDP 192.168.4.78:55015;rport;branch=z9hG4bKPjbd6a7ff3acb84400856c2256d176d373
Max-Forwards: 70
From: <sip:+9122233344444@ims.airtel.in>;tag=83fc8ae46ad44e708636d11e79289a9d
To: <sip:+9122233344444@ims.airtel.in>
Call-ID: 78551949de1f4ef4bdd1ef38a60dd8e8
CSeq: 29994 REGISTER
User-Agent: MicroSIP/3.20.0
Contact: <sip:+9122233344444@192.168.4.78:55015;ob>
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0
I have no idea why it would do this!
If your MicroSIP does the same thing (and it works), your corresponding register string would be:
+915324000xx@ims.airtel.in:Huawei@1:+915324000xx@ims.airtel.in@10.232.142.146/+91532400xx
If this still fails to register, please post SIP trace of successful registration from MicroSIP log, as well as SIP trace from Asterisk for the failed registration. At the Asterisk command prompt, type
sip set debug on
and the SIP trace will be included in the regular Asterisk log.