2 Replies Latest reply on Jul 2, 2010 10:28 PM by user753546

    SIP registrar example is not accessible


      I have created a sipserverdomain using Configuration Wizard on OCCAS 4.0 and I have deployed a Registar example there (on the AdminServer). Starting Weblogic is ok and I can see, that the SIP server is started as well:

      <17.06.2010 18:29:11 EEST> <Notice> <Server> <BEA-002613> <Channel "sip" is now listening on for protocols sip.>
      <17.06.2010 18:29:11 EEST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on for protocols iiop, t3, ldap, snmp, http.>
      <17.06.2010 18:29:11 EEST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "ngin_4" running in Development Mode>
      <17.06.2010 18:29:11 EEST> <Notice> <WLSS.Transport> <BEA-330687> <Thread "SIP Message processor (Transport UDP)" is listening on port 5060>

      Also, from the console, I see that my application is deployed:
      SIP Server -> SIP Applications -> AdminServer     AdminServer_/registrar

      However, I cannot access this application anyhow, even if I use the example

      sipp -sf register.xml localhost:5060 -m 1

      This results in:

      sipp: The following events occured:
      2010-06-17     18:23:36:121     1276788216.121569: Aborting call on unexpected message for Call-Id '1-7684@fe80::9d53:c546:c1da:6215%19': while expecting '200' (index 1), received 'REGISTER sip:service@[::1]:5060 SIP/2.0
      Via: SIP/2.0/UDP [fe80::9d53:c546:c1da:6215%19]:5060;branch=z9hG4bK-7684-1-0
      From: sipp <sip:sipp@[fe80::9d53:c546:c1da:6215%19]:5060>;tag=1
      To: sut <sip:service@[::1]:5060>
      Call-ID: 1-7684@fe80::9d53:c546:c1da:6215%19
      CSeq: 1 REGISTER
      Contact: sip:joe_home@[fe80::9d53:c546:c1da:6215%19]:5060
      Contact: sip:joe_cell@[fe80::9d53:c546:c1da:6215%19]:5060
      Contact: sip:joe_work@[fe80::9d53:c546:c1da:6215%19]:5060;expires=22
      Expires: 41
      Max-Forwards: 70
      Subject: Performance Test
      Content-Length: 0

      What is wrong? Is it some configuration which is missing? How do I access my sip servlet using SIP?

      Btw, I've noticed that there is a message "DataTier Resource is not configured" when I click Sip Server -> Configuration -> Data Tier. Can it be the case? How can I solve it?

        • 1. Re: SIP registrar example is not accessible

          May it be that SIPP send the message to itself?

          Please enable SIP message debug on the SIP server side via the SIP extension of the WLS Admin Console. You will than see in the AdminServer.log how the message flow goes and what messages is sent from and to which IP+port and whether TCP or UDP is used.

          Best regards,
          • 2. Re: SIP registrar example is not accessible
            Kai has suggested correct way to further troubleshoot it.

            You may also specify specific listen address for your sipserver in config.xml or through console rather than specifying no value which defaults to any IP.

            Also in sipp you can use -i option to specify source ip and ip option to specify port for for sip request sent to server .By default port used is sipp is 5060