Can anyone spot anything wrong with the following BUSY response...
INVITE sip:18442332444@209.141.46.21:5080 SIP/2.0Via: SIP/2.0/UDP 109.141.46.21:5873;branch=z9hG4bK-d8754z-97061e52b6148122-1---d8754z-;rportMax-Forwards: 70Contact: <sip:10001@109.141.46.21:5873>To: <sip:18442332444@109.141.46.21:5080>From: "4074664483"<sip:10001@109.141.46.21:5873>;tag=56290568Call-ID: MTVlN2Q0NDRiMTIzZmEwN2QyZTVhZWFjOTE2ZDFmYTM.CSeq: 1 INVITEAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGEContent-Type: application/sdpSupported: replacesContent-Length: 359
SIP/2.0 486 Busy hereVia: SIP/2.0/UDP 109.141.46.21:5873;branch=z9hG4bK-d8754z-97061e52b6148122-1---d8754z-;rportFrom: "4074664483"<sip:10001@109.141.46.21:5873>;tag=56290568To: <sip:18442332444@109.141.46.21:5080>;tag=771072-7710Call-ID: MTVlN2Q0NDRiMTIzZmEwN2QyZTVhZWFjOTE2ZDFmYTM.CSeq: 1 INVITEContent-Length: 0
↧