[OpenSIPStack] OpenSBC SIP Trunking - Null Session in CallSessionManager.cxx

[Gaurav K. <gkh...@is...>]

Hello Joegen,

 

I grabbed the latest source code from CVS and configured OpenSBC for SIP
trunking. While it may not be prime time, it works quiet well except for a
couple of issues:-

 

1) Upon initialization, OpenSBC is able to register successfully with
various service providers. I configured a couple of Xlite softphones to
register with OpenSBC and used them for testing inbound/ outbound calls with
various service providers.

 

*	Placing an outbound call from one of the Xlite softphones to an
external service provider (Gafachi) works fine (attached log - outgoing.log)
*	Placing an inbound call from an external service provider to opensbc
results in the following error in the log (attached log - incoming.log)

 

4:43:39.304   DTL: [CID=0x0af8] Event: ---> Inbound - INVITE
sip:16462781042@192.168.96.115:5066;transport=udp SIP/2.0

4:43:39.306   DBG: [CID=0x0af8] Session CREATED

4:43:39.306   INF: [CID=0x0af8] *** CREATED (UAS) CALL ***
d82a729522b3f145f0798b363d25b6a1@64.192.112.13

4:43:39.306   INF: [CID=0x0af8] *** DESTROYED CALL ***
d82a729522b3f145f0798b363d25b6a1@64.192.112.13

4:43:39.307   DBG: [CID=0x0af8] CALL: (inbound) : Session DESTROYED

4:43:39.308   ERR: [CID=0x0000] GC: .\src\CallSessionManager.cxx:528
CallSessionManager::OnCreateServerSession::CallSession Attempt to
CreateReference() a NULL Pointer or none descendant of PObject!!!

4:43:39.308   DBG: [CID=0x06cb] *** MESSAGE ARRIVAL *** No Session available
to handle INVITE sip:16462781042@192.168.96.115:5066;transport=udp SIP/2.0

4:43:39.312   PWL: [CID=0x0000] Using Iface: 192.168.96.115 to send to Dest:
64.192.112.13

 

Can you confirm if it's a bug/ configuration issue? The log file is attached
for reference

 

2) While exploring various service providers, I found an issue with
authentication in SIP trunking mode. While placing an outbound call to an
external service provider from one of the UAs registered to SBC, if the
external service provider requests authentication and returns a 407, the 407
is relayed back by OpenSBC to the UA. This should not happen as all the
credentials for service provider (trunk-account information) is present with
the SBC itself. Any comments?

 

I look forward to hearing from you regarding these issues. Please let me
know if you need any other information regarding the same.

 

Regards,

Gaurav