All pastes #18543 Raw Edit

Anonymous

public text v1 · immutable
#18543 ·published 2005-07-26 19:03 UTC
rendered paste body
Zap phone calling ipDialog SIP phone 121.  Sip phone rings.  Zap phone hangs up,
SIP phone keeps ringing.  Looks like asterisk is consumed with bogus PUBLISH commands.
Similar happens on Polycom and Grandstream.


*CLI> sip debug peer 128
SIP Debugging Enabled for IP: 192.70.160.48:5060
    -- Executing Macro("Zap/1-1", "sip-phone|128") in new stack
    -- Executing Macro("Zap/1-1", "set-call-return|128|inside") in new stack
    -- Executing DBput("Zap/1-1", "CLID/128=120") in new stack
    -- DBput: family=CLID, key=128, value=120
    -- Executing Macro("Zap/1-1", "set-last-number-redial|128|inside") in new stack
    -- Executing GotoIf("Zap/1-1", "1?2:3") in new stack
    -- Goto (macro-set-last-number-redial,s,2)
    -- Executing DBput("Zap/1-1", "LNR/120=128") in new stack
    -- DBput: family=LNR, key=120, value=128
    -- Executing NoOp("Zap/1-1", "macro-sip-phone") in new stack
    -- Executing Dial("Zap/1-1", "SIP/128|") in new stack
We're at 192.70.160.39 port 10380
Answering with preferred capability 0x4 (ulaw)
Answering with non-codec capability 0x1 (telephone-event)
12 headers, 10 lines
Reliably Transmitting (no NAT) to 192.70.160.48:5060:
INVITE sip:128@192.70.160.48 SIP/2.0
Via: SIP/2.0/UDP 192.70.160.39:5060;branch=z9hG4bK3c80c036
From: "Craig Wireless" <sip:120@192.70.160.39>;tag=as5ac7971b
To: <sip:128@192.70.160.48>
Contact: <sip:120@192.70.160.39>
Call-ID: 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Date: Tue, 26 Jul 2005 18:57:47 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY
Content-Type: application/sdp
Content-Length: 216

v=0
o=root 7716 7716 IN IP4 192.70.160.39
s=session
c=IN IP4 192.70.160.39
t=0 0
m=audio 10380 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -

---
    -- Called 128
    -- SIP/128-dbd1 is ringing
Reliably Transmitting (no NAT) to 192.70.160.48:5060:
PUBLISH sip:128@192.70.160.48 SIP/2.0
Via: SIP/2.0/UDP 192.70.160.39:5060;branch=z9hG4bK3c80c036
From: "Craig Wireless" <sip:120@192.70.160.39>;tag=as5ac7971b
To: <sip:128@192.70.160.48>
Contact: <sip:120@192.70.160.39>
Call-ID: 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39
CSeq: 102 PUBLISH
User-Agent: Asterisk PBX
Content-Length: 0


---
Scheduling destruction of call '3e346b001a6685ec1f5ab91c1d692769@192.70.160.39' in 15000 ms
  == Spawn extension (macro-sip-phone, s, 3) exited non-zero on 'Zap/1-1' in macro 'sip-phone'
  == Spawn extension (inside, 128, 1) exited non-zero on 'Zap/1-1'
    -- Got SIP response 400 "Bad Request" back from 192.70.160.48
    -- Hungup 'Zap/1-1'
Retransmitting #1 (no NAT) to 192.70.160.48:5060:
PUBLISH sip:128@192.70.160.48 SIP/2.0
Via: SIP/2.0/UDP 192.70.160.39:5060;branch=z9hG4bK3c80c036
From: "Craig Wireless" <sip:120@192.70.160.39>;tag=as5ac7971b
To: <sip:128@192.70.160.48>
Contact: <sip:120@192.70.160.39>
Call-ID: 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39
CSeq: 102 PUBLISH
User-Agent: Asterisk PBX
Content-Length: 0


---
    -- Got SIP response 400 "Bad Request" back from 192.70.160.48
Retransmitting #2 (no NAT) to 192.70.160.48:5060:
PUBLISH sip:128@192.70.160.48 SIP/2.0
Via: SIP/2.0/UDP 192.70.160.39:5060;branch=z9hG4bK3c80c036
From: "Craig Wireless" <sip:120@192.70.160.39>;tag=as5ac7971b
To: <sip:128@192.70.160.48>
Contact: <sip:120@192.70.160.39>
Call-ID: 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39
CSeq: 102 PUBLISH
User-Agent: Asterisk PBX
Content-Length: 0


---
    -- Got SIP response 400 "Bad Request" back from 192.70.160.48
Retransmitting #3 (no NAT) to 192.70.160.48:5060:
PUBLISH sip:128@192.70.160.48 SIP/2.0
Via: SIP/2.0/UDP 192.70.160.39:5060;branch=z9hG4bK3c80c036
From: "Craig Wireless" <sip:120@192.70.160.39>;tag=as5ac7971b
To: <sip:128@192.70.160.48>
Contact: <sip:120@192.70.160.39>
Call-ID: 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39
CSeq: 102 PUBLISH
User-Agent: Asterisk PBX
Content-Length: 0


---
    -- Got SIP response 400 "Bad Request" back from 192.70.160.48
Retransmitting #4 (no NAT) to 192.70.160.48:5060:
PUBLISH sip:128@192.70.160.48 SIP/2.0
Via: SIP/2.0/UDP 192.70.160.39:5060;branch=z9hG4bK3c80c036
From: "Craig Wireless" <sip:120@192.70.160.39>;tag=as5ac7971b
To: <sip:128@192.70.160.48>
Contact: <sip:120@192.70.160.39>
Call-ID: 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39
CSeq: 102 PUBLISH
User-Agent: Asterisk PBX
Content-Length: 0


---
    -- Got SIP response 400 "Bad Request" back from 192.70.160.48
Retransmitting #5 (no NAT) to 192.70.160.48:5060:
PUBLISH sip:128@192.70.160.48 SIP/2.0
Via: SIP/2.0/UDP 192.70.160.39:5060;branch=z9hG4bK3c80c036
From: "Craig Wireless" <sip:120@192.70.160.39>;tag=as5ac7971b
To: <sip:128@192.70.160.48>
Contact: <sip:120@192.70.160.39>
Call-ID: 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39
CSeq: 102 PUBLISH
User-Agent: Asterisk PBX
Content-Length: 0


---
    -- Got SIP response 400 "Bad Request" back from 192.70.160.48
Jul 26 14:58:02 WARNING[7716]: chan_sip.c:1039 retrans_pkt: Maximum retries exceeded on call 3e346b001a6685ec1f5ab91c1d692769@192.70.160.39 for seqno 102 (Non-critical Request)