9 Replies Latest reply: Jul 7, 2011 11:58 AM by 725569 RSS

    Application working on WLSS 3.0 is not working on OCCAS 4.0

    547687
      Hi,

      I have an application working perfectly on WLSS 3.0, but now that we decide to work with OCCAS 4.0, the application stop working. For every INVITE that we generate we got an exception. In the begining I thouht that was something related with the P-Asserted-Identity, but I configured it and still receive the exception. Someboy have an idea what is causing the problem?...

      ####<Nov 2, 2009 1:55:18 PM CST> <Error> <ServletContext-/serviceMLN> <ines> <engine1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1257191718972> <BEA-000000> <[WLSS.Engine:330052]Failed to dispatch Sip message to servlet serviceMLN
      java.lang.NullPointerException
      at com.bea.wcp.sip.engine.server.TelURLImpl.getAbsolutePhoneContext(TelURLImpl.java:651)
      at com.bea.wcp.sip.engine.server.TelURLImpl.hashCode(TelURLImpl.java:677)
      at com.bea.wcp.sip.engine.server.AddressImpl.hashCode(AddressImpl.java:751)
      at java.util.HashMap.put(HashMap.java:372)
      at java.util.HashSet.add(HashSet.java:200)
      at com.bea.wcp.sip.security.internal.PAssertedIdentityHelper.collectPAIHeaders(PAssertedIdentityHelper.java:262)
      at com.bea.wcp.sip.security.internal.PAssertedIdentityHelper.filterPAIHeaders(PAssertedIdentityHelper.java:222)
      at com.bea.wcp.sip.engine.server.ClientTransaction.sendRequest(ClientTransaction.java:772)
      at com.bea.wcp.sip.engine.server.ClientTransaction.startTransaction(ClientTransaction.java:276)
      at com.bea.wcp.sip.engine.server.TransactionManager.startTransaction(TransactionManager.java:636)
      at com.bea.wcp.sip.engine.server.TransactionManager.startTransaction(TransactionManager.java:709)
      at com.bea.wcp.sip.engine.server.TransactionManager.sendRequest(TransactionManager.java:688)
      at com.bea.wcp.sip.engine.server.SipSessionImpl.sendRequest(SipSessionImpl.java:1705)
      at com.bea.wcp.sip.engine.server.SipSessionImpl.sendRequest(SipSessionImpl.java:1648)
      at com.bea.wcp.sip.engine.server.SipServletRequestImpl.send(SipServletRequestImpl.java:980)
      at com.bea.wcp.sip.engine.server.SipServletRequestImpl.send(SipServletRequestImpl.java:948)
      at com.bea.wcp.sip.engine.SipServletRequestAdapter.send(SipServletRequestAdapter.java:241)
        • 1. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
          user753546
          Seems to be a bug here. What kind of Tel URI is it? is t global?

          Can you paste the whole sip message and also file a bug with Oracle Support for this supplying your testcase.
          • 2. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
            547687
            Scenario A dial B, using 4 digits dialing.

            WLSS 3.0
            INVITE that arrives to application server

            INVITE sip:1001@myimsdomain.com SIP/2.0
            CSeq: 1 INVITE
            Route: <sip:192.168.xxx.99:5060;lr;original-dialog-id=z9hG4bK207d5fb7509ac5e8026a6cddd3279d7e-INVITE>
            Call-ID: M2MxOWVlY2FjNzg0NTZmNGI3MDlmNGYzYjg3MWQ4NjQ.
            Via: SIP/2.0/udp 192.168.xxx.99:5060;branch=z9hG4bK207d5fb7509ac5e8026a6cddd3279d7e
            Via: SIP/2.0/UDP 192.168.xxx.3:15106;rport=15106;branch=z9hG4bK-d8754z-f81e7c52fd36ae62-1---d8754z-;received_port_ext=5060;received=192.168.xxx.3
            From: 5555555550 <sip:5555555550@myimsdomain.com>;tag=ec38be44
            Content-Type: application/sdp
            Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
            To: 1001 <sip:1001@myimsdomain.com>
            Content-Length: 317
            Contact: sip:5555555550@192.168.xxx.3:15106
            User-Agent: X-Lite release 1103k stamp 53621
            Record-Route: <sip:192.168.xxx.99:5060;from-tag=ec38be44;lr>
            Max-Forwards: 69

            v=0
            o=- 6 2 IN IP4 192.168.xxx.3
            s=CounterPath X-Lite 3.0
            c=IN IP4 192.168.xxx.3
            t=0 0
            m=audio 59182 RTP/AVP 107 0 8 101
            a=alt:1 2 : V8NeH3ke 9b6bIkKQ 192.168.xxx.3 59182
            a=alt:2 1 : tL5skPf5 43JPfFYc 192.168.56.1 59182
            a=fmtp:101 0-15
            a=rtpmap:107 BV32/16000
            a=rtpmap:101 telephone-event/8000
            a=sendrecv

            INVITE that leave the application server

            INVITE sip:55555555551@myimsdomain.com;user=phone SIP/2.0
            Min-SE: 600
            CSeq: 1 INVITE
            Route: <sip:192.168.xxx.99:5060;lr;original-dialog-id=z9hG4bK207d5fb7509ac5e8026a6cddd3279d7e-INVITE>
            Call-ID: wlss2c3d6be32e624bef48c8d32b05e66dc3wl(M2MxOWVlY2FjNzg0NTZmNGI3MDlmNGYzYjg3MWQ4NjQ.%)wl@192.168.xxx.245
            X-Orig: true
            Via: SIP/2.0/UDP 192.168.xxx.99:5060;wlsscid=5fbb8cb142088f50;branch=z9hG4bK8c5e5cd05b7307d22adb3b86fcafbc73
            From: <sip:1000@myimsdomain.com;user=phone>;tag=6feed186
            X-AreaCode: 55
            Content-Type: application/sdp
            Privacy: none
            To: <sip:55555555551@myimsdomain.com;user=phone>
            Contact: <sip:192.168.xxx.99:5060;transport=udp;wlsscid=5fbb8cb142088f50;appsessionid=app-fyfo15rt41es>
            Content-Length: 317
            P-Asserted-Identity: 1000 <sip:1000@myimsdomain.com>
            P-Asserted-Identity: 1000 <tel:1000>
            Max-Forwards: 70

            v=0
            o=- 6 2 IN IP4 192.168.xxx.3
            s=CounterPath X-Lite 3.0
            c=IN IP4 192.168.xxx.3
            t=0 0
            m=audio 59182 RTP/AVP 107 0 8 101
            a=alt:1 2 : V8NeH3ke 9b6bIkKQ 192.168.xxx.3 59182
            a=alt:2 1 : tL5skPf5 43JPfFYc 192.168.56.1 59182
            a=fmtp:101 0-15
            a=rtpmap:107 BV32/16000
            a=rtpmap:101 telephone-event/8000
            a=sendrecv

            ============================================================================================================
            OCCAS 4.0

            This the INVITE that arrives to OCCAS, but there is no INVITE that leave.

            INVITE sip:1001@myimsdomain.com SIP/2.0
            Max-Forwards: 69
            Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO
            CSeq: 1 INVITE
            Content-Length: 314
            Contact: <sip:5555555551@192.168.xxx.3:28146>
            User-Agent: X-Lite release 1103k stamp 53621
            Route: <sip:192.168.xxx.99:5060;lr;original-dialog-id=z9hG4bK5d788dc27b37f686a6bd48ba60dcecde-INVITE>
            To: "1001"<sip:1001@myimsdomain.com>
            From: "5555555551"<sip:5555555551@myimsdomain.com>;tag=8655c909
            Call-ID: YzgyNTgyYWFhNGIyNmJhYmIxMzU2NWE2Y2Q0YzdlYTU.
            Content-Type: application/sdp
            Via: SIP/2.0/udp 192.168.xxx.99:5060;branch=z9hG4bK5d788dc27b37f686a6bd48ba60dcecde
            Via: SIP/2.0/UDP 192.168.xxx.3:28146;rport=28146;branch=z9hG4bK-d8754z-d519440851709a58-1---d8754z-;received_port_ext=5060;received=192.168.xxx.3

            v=0
            o=- 8 2 IN IP4 192.168.xxx.3
            s=CounterPath X-Lite 3.0
            c=IN IP4 192.168.xxx.3
            t=0 0
            m=audio 7010 RTP/AVP 107 0 8 101
            a=alt:1 2 : VCGI+azN e2Vicgnj 192.168.xxx.3 7010
            a=alt:2 1 : 3D30iwYm JfJo1JW0 192.168.56.1 7010
            a=fmtp:101 0-15
            a=rtpmap:107 BV32/16000
            a=rtpmap:101 telephone-event/8000
            a=sendrecv
            • 3. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
              user753546
              File a support case and attach the simple reproducer so that issue can be looked into.
              • 4. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
                547687
                thanks...I already start a case with Oracle My Support...

                Saludos
                • 5. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
                  user12028321
                  I notice you mention P-Asserted. I am having an issue where I send out P-Asserted and it is stripped when it comes into OCCAS. When you say "configured" in the original message, what is meant? I there something I need to configure in OCCAS to not strip this header.

                  thanks,
                  Bill
                  • 6. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
                    869251
                    Hi,

                    Have you figured out a solution to your problem?

                    We are also facing same problem, please suggest how you got around it.

                    Thanks
                    • 7. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
                      725569
                      Hello,

                      Seems the parameter "phone-context" is not set in the message.

                      But in any case a NPE should never happen. So you can open a SR to request a patch making method com.bea.wcp.sip.engine.server.TelURLImpl.getAbsolutePhoneContext(TelURLImpl.java:651) more robust so that it does not throw a NPE any more.

                      Also, if you post question on the support community forum for that product more people involved into OCCAS are reading it:
                      https://communities.oracle.com/portal/server.pt/community/service_delivery_platform

                      Best regards,
                      Kai
                      • 8. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
                        869251
                        Hi,

                        Did you find a solution to your problem?

                        We are also facing the same problem when PAI includes a comma.

                        Thanks
                        Tjs
                        • 9. Re: Application working on WLSS 3.0 is not working on OCCAS 4.0
                          725569
                          Hello,

                          And you installed all recommended patches as described in Knowledge note 1184055.1 - "Recommended Patches to Install On OCCAS 4.0 or Products Depending on OCCAS 4.0"?

                          There had been parsing issues with URIs if they had been too complex and they had been fixed. I don't remember all. So please open a service request if this is not already fixed at the recommended patches. Support will than review and decide whether this is a known issue or not.

                          BR;
                          Kai