Application working on WLSS 3.0 is not working on OCCAS 4.0

Question

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)

Answer 1

Scenario A dial B, using 4 digits dialing.
WLSS 3.0
INVITE that arrives to application server
INVITE sip:[email protected] 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:[email protected]>;tag=ec38be44
Content-Type: application/sdp
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
To: 1001 <sip:[email protected]>
Content-Length: 317
Contact: sip:[email protected]: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:[email protected];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.%)[email protected]
X-Orig: true
Via: SIP/2.0/UDP 192.168.xxx.99:5060;wlsscid=5fbb8cb142088f50;branch=z9hG4bK8c5e5cd05b7307d22adb3b86fcafbc73
From: <sip:[email protected];user=phone>;tag=6feed186
X-AreaCode: 55
Content-Type: application/sdp
Privacy: none
To: <sip:[email protected];user=phone>
Contact: <sip:192.168.xxx.99:5060;transport=udp;wlsscid=5fbb8cb142088f50;appsessionid=app-fyfo15rt41es>
Content-Length: 317
P-Asserted-Identity: 1000 <sip:[email protected]>
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:[email protected] 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:[email protected]: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:[email protected]>
From: "5555555551"<sip:[email protected]>;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