I received this message on the console after a call had been dropped. I searched on google as well as in this forum and no hits returned for “Got SIP response 400 “Missing, Erroneous or Multiple Contact header field(s)” back from” or “Got SIP response 400 Missing, Erroneous”.
anyone have some thoughts as to what may have been the root cause of this?
— Got SIP response 400 “Missing, Erroneous or Multiple Contact header field(s)” back from
e[Krnvoice1*CLI>
– Got SIP response 400 “Missing, Erroneous or Multiple Contact header field(s)” back from [SIP_INTERNAL_IP]
e[Krnvoice1*CLI>
Scheduling destruction of SIP dialog ‘1395de6e3a7cea734acd14872cf40939@sip.[SIP_PROVIDER].com’ in 32000 ms (Method: INVITE)
set_destination: Parsing sip:IP_ADDRESS_1;lr for address/port to send to
set_destination: set destination to IP_ADDRESS_1], port 5060
Reliably Transmitting (no NAT) to [IP_ADDRESS_1]:5060:
BYE sip:[DIALED_NUMBER]@[IP_ADDRESS_2]:5060;transport=udp SIP/2.0
– Got SIP response 400 “Missing, Erroneous or Multiple Contact header field(s)” back from
Still dropping calls after 15 minutes due to the above error. Does anyone have any insight into the possible issue? I have done some searching, but have not found many hits.
Version Information:
Asterisk 1.6.2.7 built by root @ on a x86_64 running Linux on 2010-05-19 19:16:19 UTC
Your SIP trace starts just AFTER the important bit! You need to show the actual content of the 400 Response and the actual content of what it was objecting to.
Sure there is. Read from the bottom up. I think I figured it out. I was using a dialing pattern that contained a pound sign that would change the outbound caller ID number to a specific number when dialed. I have done some testing and since removing pound from the dialing string the “corrupted headers” do not appear.
Do you have any suggestions on how better to handle the changing of the outbound CID number?
I cannot find the text of the 400 status response that it is referring to. In fact, I cannot find anything sent to or read from [SIP_PHONE_IP]. Incidentally, 400 status indicates a non-specific client error.
okay, sorry about that. I must not have gone back far enough. I am pretty confident that the cause was the pound key as it was translating that into %23 in the “From:” field.
Thanks for all your help Dave. Do you know of any reason not to do what I am attempting to do here? Change the CID number based on having users dial an extra digit in front of the called number?