[OpenSIPS-Users] URGENT! uac_registrant:run_reg_tm_cback: failed to parse Contact body

[Ovidiu Sas]

Looking at your Contact header that you built, it doesn't seem right:
<sip:7777 at 182.xx.xx.xx.xx>transport=UDP;expires=300
You need a ';' after '>'.  It should look like this:
<sip:7777 at 182.xx.xx.xx.xx>;transport=UDP;expires=300

Fix your config and try again.

Regards,
Ovidiu Sas

On Mon, Sep 15, 2014 at 10:02 AM, Satish Patel <satish.txt at gmail.com> wrote:
> Any thought? it works with other SIP clients but not Opensips UAC :(
>
> On Fri, Sep 12, 2014 at 9:16 PM, Satish Patel <satish.txt at gmail.com> wrote:
>>
>> But if i configure same account on my SIP phone it works! why it is
>> misbehaving with Opensips?
>>
>> SIP provide will argue if it works with SIP phone then it should work with
>> all devices.
>>
>> On Fri, Sep 12, 2014 at 6:39 PM, Ovidiu Sas <osas at voipembedded.com> wrote:
>>>
>>> You need to tell your provider to fix this.
>>>
>>> Regards,
>>> Ovidiu Sas
>>>
>>> On Sep 12, 2014 4:49 PM, "Satish Patel" <satish.txt at gmail.com> wrote:
>>>>
>>>> What is the solution? do i need to tell my SIP provide or i should do
>>>> something at Opensips side?
>>>>
>>>> On Fri, Sep 12, 2014 at 4:47 PM, Ovidiu Sas <osas at voipembedded.com>
>>>> wrote:
>>>>>
>>>>> The contact header is malformed:
>>>>> Contact:
>>>>> <<sip:73757799 at 182.xx.xx.xx.xx:5060>transport=UDP>;q=1;expires=98;received="sip:182.xx.xx.xx.xx:5060",
>>>>> <<sip:7777 at 182.xx.xx.xx.xx:5060>transport=UDP>;q=1;expires=300;received="sip:182.xx.xx.xx.xx:5060"
>>>>>
>>>>> See the double '<'.
>>>>>
>>>>> Regards,
>>>>> Ovidiu Sas
>>>>>
>>>>> On Sep 12, 2014 4:37 PM, "Satish Patel" <satish.txt at gmail.com> wrote:
>>>>>>
>>>>>> Here is the trace, so where is the problem?
>>>>>>
>>>>>> #
>>>>>> U 182.xx.xx.xx.xx:5060 -> 216.xx.xx.xx.xx:5060
>>>>>> REGISTER sip:sip.example.com:5060 SIP/2.0.
>>>>>> Via: SIP/2.0/UDP 182.xx.xx.xx.xx:5060;branch=z9hG4bK60e.9f8b83d3.0.
>>>>>> To: sip:73757799 at sip.example.com:5060.
>>>>>> From: <sip:73757799 at sip.example.com:5060>;tag=40aeb.
>>>>>> CSeq: 2 REGISTER.
>>>>>> Call-ID: e6a44cb93fd53890295e3cecfed.
>>>>>> Max-Forwards: 70.
>>>>>> Content-Length: 0.
>>>>>> User-Agent: OpenSIPS (1.12.0dev-notls (x86_64/linux)).
>>>>>> Contact: <sip:7777 at 182.xx.xx.xx.xx>transport=UDP;expires=300.
>>>>>> Authorization: Digest username="73757799", realm="sip.example.com",
>>>>>> nonce="VBNMPFQTSxBkZqUtsDCom023iuZ2evbn", uri="sip:sip.example.com:5060",
>>>>>> qop=auth, nc=00000001, cnonce="220797507",
>>>>>> response="8149149a7b11826e409d2954a35939d1", algorithm=MD5.
>>>>>> .
>>>>>>
>>>>>> #
>>>>>> U 216.xx.xx.xx.xx:5060 -> 182.xx.xx.xx.xx:5060
>>>>>> SIP/2.0 200 OK.
>>>>>> Via: SIP/2.0/UDP 182.xx.xx.xx.xx:5060;branch=z9hG4bK60e.9f8b83d3.0.
>>>>>> To:
>>>>>> sip:73757799 at sip.example.com:5060;tag=28f708707fdbe632f4ca1ebbf5e1be15-5a71.
>>>>>> From: <sip:73757799 at sip.example.com:5060>;tag=40aeb.
>>>>>> CSeq: 2 REGISTER.
>>>>>> Call-ID: e6a44cb93fd53890295e3cecfed.
>>>>>> Contact:
>>>>>> <<sip:73757799 at 182.xx.xx.xx.xx:5060>transport=UDP>;q=1;expires=98;received="sip:182.xx.xx.xx.xx:5060",
>>>>>> <<sip:7777 at 182.xx.xx.xx.xx:5060>transport=UDP>;q=1;expires=300;received="sip:182.xx.xx.xx.xx:5060".
>>>>>> Content-Length: 0.
>>>>>>
>>>>>> #
>>>>>> U 216.xx.xx.xx.xx:5060 -> 182.xx.xx.xx.xx:5060
>>>>>> OPTIONS sip:182.xx.xx.xx.xx:5060 SIP/2.0.
>>>>>> Max-Forwards: 10.
>>>>>> Record-Route: <sip:216.xx.xx.xx.xx;lr>.
>>>>>> Via: SIP/2.0/UDP
>>>>>> 216.xx.xx.xx.xx;branch=z9hG4bK3e46.e72ab63026fa3572f78124328a048c26.0.
>>>>>> Via: SIP/2.0/UDP 70.xxx.xxx.xxx.xxx:5060;branch=0.
>>>>>> Route: <sip:216.xx.xx.xx.xx;lr;received='sip:182.xx.xx.xx.xx:5060'>.
>>>>>> From: sip:ping at invalid;tag=5ba30f69.
>>>>>> To: sip:182.xx.xx.xx.xx:5060.
>>>>>> Call-ID: 0c26e475-b1d63378-dc72c58 at 70.xxx.xxx.xxx.xxx.
>>>>>> CSeq: 1 OPTIONS.
>>>>>> Content-Length: 0.
>>>>>> .
>>>>>>
>>>>>> #
>>>>>> U 182.xx.xx.xx.xx:5060 -> 216.xx.xx.xx.xx:5060
>>>>>> SIP/2.0 484 Address Incomplete.
>>>>>> Via: SIP/2.0/UDP
>>>>>> 216.xx.xx.xx.xx;received=216.xx.xx.xx.xx;rport=5060;branch=z9hG4bK3e46.e72ab63026fa3572f78124328a048c26.0.
>>>>>> Via: SIP/2.0/UDP 70.xxx.xxx.xxx.xxx:5060;branch=0.
>>>>>> From: sip:ping at invalid;tag=5ba30f69.
>>>>>> To:
>>>>>> sip:182.xx.xx.xx.xx:5060;tag=c223d9b6a566b5450d01aad8764c61fe.b26e.
>>>>>> Call-ID: 0c26e475-b1d63378-dc72c58 at 70.xxx.xxx.xxx.xxx.
>>>>>> CSeq: 1 OPTIONS.
>>>>>> Server: OpenSIPS (1.12.0dev-notls (x86_64/linux)).
>>>>>> Content-Length: 0.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Sep 12, 2014 at 3:23 PM, Ovidiu Sas <osas at voipembedded.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> Take a look at RFC3261:
>>>>>>> http://tools.ietf.org/html/rfc3261#section-10.2
>>>>>>>   Contact: REGISTER requests MAY contain a Contact header field with
>>>>>>> zero or more values containing address bindings.
>>>>>>>
>>>>>>> The error that you have is related to the Contact header in the
>>>>>>> reply.
>>>>>>> Check the reply received from the registrar.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Ovidiu Sas
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Sep 12, 2014 at 3:03 PM, Satish Patel <satish.txt at gmail.com>
>>>>>>> wrote:
>>>>>>> > In logs i am getting this error
>>>>>>> >
>>>>>>> > ERROR:uac_registrant:run_reg_tm_cback: failed to parse Contact body
>>>>>>> >
>>>>>>> > AOR:: sip:9999 at sip.example.com:5060 expires=300
>>>>>>> >         state:: INTERNAL_ERROR_STATE
>>>>>>> >         last_register_sent:: Sat Sep 13 00:30:28 2014
>>>>>>> >         registration_t_out:: Sat Sep 13 00:35:28 2014
>>>>>>> >         registrar:: sip:sip.example.com:5060
>>>>>>> >         binding:: sip:9999 at 182.xxx.xxx.xxx:5060
>>>>>>> >         dst_IP:: IPv4 ip=sip.example.com
>>>>>>> >
>>>>>>> >
>>>>>>> > I have one more gateway which is asterisk one working fine, what is
>>>>>>> > the
>>>>>>> > binding_URI?
>>>>>>> >
>>>>>>> >
>>>>>>> > _______________________________________________
>>>>>>> > Users mailing list
>>>>>>> > Users at lists.opensips.org
>>>>>>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> VoIP Embedded, Inc.
>>>>>>> http://www.voipembedded.com
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users at lists.opensips.org
>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at lists.opensips.org
>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com