reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] Can the repro support PUBLISH ? I send PUBLISH to repro sip sever and receive 405.

repro supports PUBLISH.  Looks like the 405 is coming from a UA using pjsip and not from repro.  Look at the User-Agent header in the 405 response:

User-Agent: PJSUA v2.1-svn/i686-pc-linux-gnu

Scott


On Wed, Sep 11, 2013 at 10:53 PM, 庄达 <zhuangzhida1989@xxxxxxxxx> wrote:
Hello, I compile the reSIProcate and then run the repro, and I can register and invite successfully, but when I try the PUBLISH command , the repro reply me that 405 Method not allowed.
the fllowing is what I receive from repro sip sever:

PUBLISH sip:***@*** SIP/2.0
Via: SIP/2.0/UDP 192.168.1.228:22899;rport;branch=z9hG4bKPjyqvfCCXUJGlhRZpTT1TypXS3Nwr5n.T7
Max-Forwards: 70
From: <sip:***@***>;tag=KALWZIqdTEQQiFn5UEvJmuW7AmCqWx4f
To: <sip:***@***>
Call-ID: X2RqG3XZ-p1.r39nkcGNzu5ryiLskZwp
CSeq: 14843 PUBLISH
Event: presence
User-Agent: PJSUA v2.1-svn Linux-3.2.0.31/i686/glibc-2.15
Proxy-Authorization: Digest username="***", realm="***", nonce="1378953444:e93a0f822ed41f3cc2e152431122cd23", uri="sip:***@***", response="09276885fa75a51a89ab44bfe19fc3c9", algorithm=MD5, cnonce="FJIbPjxrKDEIDdLXnwiIZca4Jzc732Ye", qop=auth, nc=00000001
Content-Type: application/pidf+xml
Content-Length:   292

<?xml version="1.0" encoding="UTF-8"?>
<presence entity="sip:zzd987@xxxxxxxxxxxxxxxxxx" xmlns="urn:ietf:params:xml:ns:pidf">
 <tuple id="pjuZ.baHhWywA9PRvUW7lhJtRgUZQCry-4">
  <status>
   <basic>open</basic>
  </status>
  <timestamp>2013-09-12T10:40:01.343Z</timestamp>
 </tuple>
</presence>

--end msg--

10:40:01.504   pjsua_core.c  .TX 633 bytes Response msg 405/PUBLISH/cseq=14843 (tdta0xb3907978) to UDP 124.232.165.189:5060:
SIP/2.0 405 Method Not Allowed
Via: SIP/2.0/UDP 124.232.165.189:5060;rport=5060;received=124.232.165.189;branch=z9hG4bK-524287-1---5193a567b5b1ca12
Via: SIP/2.0/UDP 183.39.130.109:22899;rport=22899;branch=z9hG4bKPjyqvfCCXUJGlhRZpTT1TypXS3Nwr5n.T7
Call-ID: X2RqG3XZ-p1.r39nkcGNzu5ryiLskZwp
From: <sip:zzd987@xxxxxxxxxxxxxxxxxx>;tag=KALWZIqdTEQQiFn5UEvJmuW7AmCqWx4f
To: <sip:zzd987@xxxxxxxxxxxxxxxxxx>;tag=z9hG4bK-524287-1---5193a567b5b1ca12
CSeq: 14843 PUBLISH
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: PJSUA v2.1-svn/i686-pc-linux-gnu
Content-Length:  0


--end msg--


and the repro message is that:
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | Proxy.cxx:353 | New RequestContext tid=pjyqvfccxujglhrzptt1typxs3nwr5n.t7 : SipReq:  PUBLISH ***@*** tid=PjyqvfCCXUJGlhRZpTT1TypXS3Nwr5n.T7 cseq=14843 PUBLISH / 14843 from(wire)
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | Proxy.cxx:363 | Inserting new RequestContext tid=pjyqvfccxujglhrzptt1typxs3nwr5n.t7 -> numtrans=1 final=0
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | RequestContext.cxx:90 | RequestContext::process(SipMessage) PjyqvfCCXUJGlhRZpTT1TypXS3Nwr5n.T7
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | AclStore.cxx:532 | AclStore - source address NOT trusted: 183.39.130.109:22899 UDP
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | monkeys/DigestAuthenticator.cxx:369 | Request user auth info for *** at realm ***
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | RequestContext.cxx:635 | RequestContext::process(ApplicationMessage) UserInfoMessage(tid=PjyqvfCCXUJGlhRZpTT1TypXS3Nwr5n.T7)
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | monkeys/DigestAuthenticator.cxx:114 | Received user auth info for *** at realm imaginp2p.3322.org a1 is b80c615835c4110b5b530bf529e01eaf
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | monkeys/DigestAuthenticator.cxx:133 | Authentication ok for ***
INFO | 20130912-103724.485 | lt-repro | REPRO:APP | 140552139831040 | monkeys/LocationServer.cxx:74 | LocationServer adding target <sip:zzd987@183.39.130.109:22899;ob> with tuple [ V4 183.39.130.109:22899 UDP target domain=unspecified mFlowKey=10 ]
INFO | 20130912-103724.486 | lt-repro | REPRO:APP | 140552139831040 | RequestContext.cxx:701 | numtrans=1 final=0 identity=*** req=SipReq:  PUBLISH ***@*** tid=PjyqvfCCXUJGlhRZpTT1TypXS3Nwr5n.T7 cseq=14843 PUBLISH / 14843 from(wire) there are 1 candidates -> continue
INFO | 20130912-103724.486 | lt-repro | REPRO:APP | 140552139831040 | Proxy.cxx:527 | add client transaction tid=5193a567b5b1ca12 0x1f18510
INFO | 20130912-103724.486 | lt-repro | REPRO:APP | 140552139831040 | ResponseContext.cxx:233 | Creating new client transaction 5193a567b5b1ca12 -> sip:***@183.39.130.109:***;ob
INFO | 20130912-103724.549 | lt-repro | REPRO:APP | 140552139831040 | Proxy.cxx:397 | Looking up RequestContext tid=5193a567b5b1ca12
INFO | 20130912-103724.549 | lt-repro | REPRO:APP | 140552139831040 | RequestContext.cxx:90 | RequestContext::process(SipMessage) 5193a567b5b1ca12
INFO | 20130912-103724.549 | lt-repro | REPRO:APP | 140552139831040 | ResponseContext.cxx:927 | processResponse: 
SIP/2.0 405 Method Not Allowed
Via: SIP/2.0/UDP *.*.*.*:5060;rport=5060;received=*.*.*.*;branch=z9hG4bK-524287-1---5193a567b5b1ca12
Via: SIP/2.0/UDP 183.39.130.109:22899;rport=22899;branch=z9hG4bKPjyqvfCCXUJGlhRZpTT1TypXS3Nwr5n.T7
To: <sip:***@***>;tag=z9hG4bK-524287-1---5193a567b5b1ca12
From: <sip:***@***>;tag=KALWZIqdTEQQiFn5UEvJmuW7AmCqWx4f
Call-ID: X2RqG3XZ-p1.r39nkcGNzu5ryiLskZwp
CSeq: 14843 PUBLISH
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: PJSUA v2.1-svn/i686-pc-linux-gnu
Content-Length: 0


What's the matter? How can I make the repro support PUBLISH?

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/