Re: B2buaHelper bug ? B2BUA lose the "Route" header

104 views
Skip to first unread message

Jean Deruelle

unread,
Apr 8, 2009, 8:20:43 AM4/8/09
to Arthur Chen, mobicents-public
Those questions should be directed to mobicents-public google group that I added in cc (please sign up to be a user) to benefit the whole community
I will create an Issue for your problem

Thanks
Jean

On Wed, Apr 8, 2009 at 12:15 PM, Arthur Chen <arth...@gmail.com> wrote:
Dear Sir

            we use mobicent SIP servlet (my platform is mss-0.8-apache-tomcat-6.0.14-0902061530 ) to create a new B2BUA request when receive an Invite SIP message. As Sip-servlet-1.1 SPEC, Record-Route and Via header fields are not copied from orignal request,  the other headers SHOULD be keep. New B2BUA Invite request remove the Via and Record-Route, however, it also remove the Route header,  which we need this in our project. (see our log)

 
Could you please judge the issue??



Source code:

protected void doInvite(SipServletRequest request) throws ServletException,
            IOException {
        if(logger.isInfoEnabled()) {       
            logger.info("We got INVITE: \n" + request.toString());                           
        }
          String[] forwardingUri=new String[]{"sip:f...@sip-servlets.com", "sip:f...@127.0.0.1:5080"};
            B2buaHelper helper = request.getB2buaHelper();                       
           
            SipFactory sipFactory = (SipFactory) getServletContext().getAttribute( SIP_FACTORY);           
            Map<String, List<String>> headers=new HashMap<String, List<String>>();
            List<String> toHeaderSet = new ArrayList<String>();
            toHeaderSet.add(forwardingUri[0]);
            headers.put("To", toHeaderSet);           
          SipServletRequest forkedRequest = helper.createRequest(request,true,headers);
     
            if(logger.isInfoEnabled()) {
                logger.info("!new forkedRequest = " + forkedRequest);
            }       
            forkedRequest.send();           
    }   


the Log message indicates that  :

1. request SIP message :

INFO pool-1-thread-1 nsn.example.CallForwardingB2BUASipServlet - We got INVITE:
INVITE sip:da...@ims.emome.net SIP/2.0
Via: SIP/2.0/UDP 10.8.192.77:5090;branch=z9hG4bK_IMSCA0500620.000_3754e56e7a28b04606c5e483972fe58101;lskpmc=S26,SIP/2.0/TCP 10.8.192.77:5070;branch=z9hG4bK_IMSCA0500620.000_081144cdeafc8989294b7487b7ed9c14;lskpmc=P05,SIP/2.0/UDP 10.8.192.58:8793;branch=z9hG4bK-d87543-1008973ed97aa522-1--d87543-;rport=8793;received=10.8.192.58
Record-Route: <sip:i...@scscf1.ims.emome.net:5090;routing_id=fa8ae120e555a41896ba02a70a4ca646;lskpmc=S26;lr;interface=bcc;tid=3754e56e7a28b04606c5e483972fe58101>,<sip:pcscf1.ims.emome.net:5070;routing_id=pcscf_a_side;lskpmc=P05;lr>
Max-Forwards: 68
Contact: <sip:pcscf1.ims.emome.net>
To: <sip:da...@ims.emome.net>
From: "Arthur" <sip:art...@ims.emome.net>;tag=9317a250
Call-ID: 5328d1714e78cd7d@YXJ0Y2hlbg..
CSeq: 2 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO
Content-Type: application/sdp
Supported: eventlist
User-Agent: CounterPath eyeBeam release 3013o stamp 23470
P-Asserted-Identity: <sip:art...@ims.emome.net>
P-Charging-Vector: icid-value=1a45a8dd3bfcc4e34878a7401d4e743e
P-com.Siemens.Access-Information: xDSL
P-com.Siemens.MSISDN-ID: 992900011
P-com.Siemens.Corr-ID: 3754e56e7a28b04606c5e483972fe58101,5328d1714e78cd7d@YXJ0Y2hlbg..
Route: <sip:i...@scscf1.ims.emome.net:5090;lr;bcos=O3001001000sjnt~fnpnf~ofuN7Rt5bsuivs;lskpmc=S26>
Content-Length: 332

v=0
o=- 23363577 23363721 IN IP4 10.8.192.58
s=CounterPath eyeBeam
c=IN IP4 10.8.192.58
t=0 0
m=audio 7316 RTP/AVP 100 6 0 8 3 97 5 102 101
a=alt:1 1 : 85DD6366 00000075 10.8.192.58 7316
a=fmtp:101 0-15
a=rtpmap:100 speex/16000
a=rtpmap:97 speex/8000
a=rtpmap:102 l16/16000
a=rtpmap:101 telephone-event/8000
a=sendrecv




========================Route: <sip:isc@scscf1...  miss================

2. response SIP message:

NFO pool-1-thread-1 nsn.example.CallForwardingB2BUASipServlet - !new forkedRequest = INVITE sip:da...@ims.emome.net SIP/2.0
Max-Forwards: 68
From: "Arthur" <sip:art...@ims.emome.net>;tag=12531259_7452a8b5
Call-ID: 5328d1714e78cd7d@YXJ0Y2hlbg..
CSeq: 2 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO
Content-Type: application/sdp
Supported: eventlist
User-Agent: CounterPath eyeBeam release 3013o stamp 23470
P-Asserted-Identity: <sip:art...@ims.emome.net>
P-Charging-Vector: icid-value=1a45a8dd3bfcc4e34878a7401d4e743e
P-com.Siemens.Access-Information: xDSL
P-com.Siemens.MSISDN-ID: 992900011
P-com.Siemens.Corr-ID: 3754e56e7a28b04606c5e483972fe58101,5328d1714e78cd7d@YXJ0Y2hlbg..
To: <sip:f...@sip-servlets.com>
Content-Length: 332

v=0
o=- 23363577 23363721 IN IP4 10.8.192.58
s=CounterPath eyeBeam
c=IN IP4 10.8.192.58
t=0 0
m=audio 7316 RTP/AVP 100 6 0 8 3 97 5 102 101
a=alt:1 1 : 85DD6366 00000075 10.8.192.58 7316
a=fmtp:101 0-15
a=rtpmap:100 speex/16000
a=rtpmap:97 speex/8000
a=rtpmap:102 l16/16000
a=rtpmap:101 telephone-event/8000
a=sendrecv





--
Sincerely,
Arthur  Chen

Jean Deruelle

unread,
Apr 8, 2009, 8:25:05 AM4/8/09
to Arthur Chen, mobicents-public

Jean Deruelle

unread,
Apr 8, 2009, 9:31:34 AM4/8/09
to Arthur Chen, mobicents-public
Fixed in trunk.
Can you try it from the source ? a new binary snapshot for test should be available soon too.
Reply all
Reply to author
Forward
0 new messages