Open Source Sip: B2B UpperReg Problem ...

7 Replies Last post: May 7, 2008 9:20 AM by dcardosoa

dcardosoa

28 posts since
Feb 12, 2008

May 5, 2008 5:05 PM

B2B UpperReg Problem

Hi...

I was using OSBC-1.1.5-3 an the B2BUpper Reg mode worked very well, but I updated to last version (1.1.5-4) and B2BUpper Reg mode doesn't work...

Is there any problem with this mode?

Is there any change on use of B2BUpper Reg mode?

Thanks in advance...

Opensbc.ini:

Upper-Registration
Rewrite-TO-Domain=True
Rewrite-FROM-Domain=True
Route-List Array Size=1
Route-List 1=sip:* sip:192.168.0.25:8060

My LOG:

336117:07:36.046 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:07:36.048 INF: CID=0x0a7d *** CREATED *** PROXY Session D1B9-11D3-4668481716FDEBA7AAD0-001@SipHost
336117:07:36.050 INF: CID=0x0a7d Routing REGISTER for URI sip:555@189.XXX.XXX.XXX
336117:07:36.050 PWL: CID=0x0000 *** NO STATIC ROUTE DEFINED *** From: sip:555@189.XXX.XXX.XXX Target: sip:555@189.XXX.XXX.XXX
336117:07:36.050 INF: CID=0x0a7d *** UPPER REGISTRATION ENABLE *** for sip:555@189.XXX.XXX.XXX
336117:07:36.053 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:07:36.054 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:07:36.552 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:07:36.606 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:07:36.607 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:07:37.553 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:07:39.553 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:07:40.657 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:07:40.659 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:07:43.552 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:07:44.717 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:07:44.718 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:07:46.052 WRN: CID=0x06cb *** TIMER EXPIRATION *** for SIP Session D1B9-11D3-4668481716FDEBA7AAD0-001@SipHost
336117:07:46.054 INF: CID=0x0a7d >>> SIP/2.0 480 Temporarily not available DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=354
336117:07:47.054 INF: CID=0x0a7d *** DESTROYED *** PROXY Session D1B9-11D3-4668481716FDEBA7AAD0-001@SipHost
336117:07:57.754 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:07:57.756 INF: CID=0x0a7d *** CREATED *** PROXY Session D1B9-11D3-4668481716FDEBA7AAD0-001@SipHost
336117:07:57.758 INF: CID=0x0a7d Routing REGISTER for URI sip:555@189.XXX.XXX.XXX
336117:07:57.758 PWL: CID=0x0000 *** NO STATIC ROUTE DEFINED *** From: sip:555@189.XXX.XXX.XXX Target: sip:555@189.XXX.XXX.XXX
336117:07:57.758 INF: CID=0x0a7d *** UPPER REGISTRATION ENABLE *** for sip:555@189.XXX.XXX.XXX
336117:07:57.760 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:07:57.762 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:07:58.252 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:07:58.282 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:07:58.284 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:07:59.253 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:08:01.252 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:08:02.322 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:08:02.324 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:08:05.252 INF: CID=0x0a7d >>> REGISTER sip:189.XXX.XXX.XXX SIP/2.0 DST: 189.XXX.XXX.XXX:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=568
336117:08:06.352 INF: CID=0x0a7d <<< REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0 SRC: 192.168.0.194:5060:UDP enc=0 bytes=397
336117:08:06.354 INF: CID=0x0a7d >>> SIP/2.0 100 Trying DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=335
336117:08:07.752 WRN: CID=0x06cb *** TIMER EXPIRATION *** for SIP Session D1B9-11D3-4668481716FDEBA7AAD0-001@SipHost
336117:08:07.754 INF: CID=0x0a7d >>> SIP/2.0 480 Temporarily not available DST: 192.168.0.194:5060:UDP SRC: 189.XXX.XXX.XXX:8070 enc=0 bytes=354
336117:08:08.754 INF: CID=0x0a7d *** DESTROYED *** PROXY Session D1B9-11D3-4668481716FDEBA7AAD0-001@SipHost

joegen

125 posts since
Apr 28, 2007

1. May 5, 2008 11:46 PM

in response to: dcardosoa

Re: B2B UpperReg Problem

dcardosoa wrote:
Hi...

I was using OSBC-1.1.5-3 an the B2BUpper Reg mode worked very well, but I updated to last version (1.1.5-4) and B2BUpper Reg mode doesn't work...

Is there any problem with this mode?

Is there any change on use of B2BUpper Reg mode?

There is a new flag in General Parameters called `Enable Backdoor Port`. Make sure that is checked when running in B2BUpperReg mode.

Joegen

dcardosoa

28 posts since
Feb 12, 2008

2. May 6, 2008 8:12 AM

in response to: joegen

Re: B2B UpperReg Problem

Thanks
Joegen,

But it is checked and OSBC is not working...

OpenSBC-General-Parameters

....

SBC-Application-Mode=B2BUpperReg Mode
Interface-Address Array Size=1
Interface-Address 1=sip:189.XXX.XXXX.XXX:8070
Enable-Backdoor-Port=True
Enable-Trunk-Port=True
Enable-Calea-Port=True
...

...

The sinaling is sending to port 5060 and I dont know why this happening:

NGREP:

U 192.168.0.194:5060 -> 189.XXX.XXX.XXX:8070
REGISTER sip:189.XXX.XXX.XXX:8070 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.194:5060;rport;branch=z9hG4bK1c6cfefbb768d950..From: "555" <sip:555@18
9.21.62.27>;tag=396e4eb8-684817..To: "555" <sip:555@189.XXX.XXX.XXX>..Call-ID: D1B9-11D3-466848172A2D163AA9F3-001@SipHost..CSeq: 1 REGISTER.
.Contact: <sip:555@192.168.0.194:5060>..Expires: 600..Max-Forwards: 70..User-Agent: 040 12-34-361787..Content-Length: 0....

U 189.XXX.XXX.XXX:8070 -> 192.168.0.194:5060
SIP/2.0 100 Trying..From: "555" <sip:555@189.XXX.XXX.XXX>;tag=396e4eb8-684817..To: "555" <sip:555@189.XXX.XXX.XXX>..Via: SIP/2.0/UDP 192.168.0.
194:5060;iid=30536;branch=z9hG4bK1c6cfefbb768d950;rport=5060;received=192.168.0.194..CSeq: 1 REGISTER..Call-ID: D1B9-11D3-466848172A2D163
AA9F3-001@SipHost..Server: OSBC-1.1.5..Content-Length: 0....

U 189.XXX.XXX.XXX:8070 -> 189.XXX.XXX.XXX:5060
REGISTER sip:189.XXX.XXX.XXX SIP/2.0..From: "555" <sip:555@189.XXX.XXX.XXX>;tag=396e4eb8-684817..To: "555" <sip:555@189.XXX.XXX.XXX>..Via: SIP/2.0
/UDP 189.XXX.XXX.XXX:8070;iid=30536;branch=z9hG4bK1add8ad9d319dd1197c4c457a5a02228-f72bb174ba94adca3cb84e1f4e6a27f0;uas-addr=189.XXX.XXX.XXX;rp
ort..Via: SIP/2.0/UDP 192.168.0.194:5060;branch=z9hG4bK1c6cfefbb768d950;rport=5060;received=192.168.0.194..CSeq: 1 REGISTER..Call-ID: D1B
9-11D3-466848172A2D163AA9F3-001@SipHost..Contact: <sip:555@189.XXX.XXX.XXX:8072>..User-Agent: OSBC-1.1.5..Expires: 600..Max-Forwards: 69..C
ontent-Length: 0....

I 189.XXX.XXX.XXX -> 189.XXX.XXX.XXX 3:3
....E..T..@.@.B8..>...>......@..REGISTER sip:189.XXX.XXX.XXX SIP/2.0..From: "555" <sip:555@189.XXX.XXX.XXX>;tag=396e4eb8-684817..To: "555" <sip
:555@189.XXX.XXX.XXX>..Via: SIP/2.0/UDP 189.XXX.XXX.XXX:8070;iid=30536;branch=z9hG4bK1add8ad9d319dd1197c4c457a5a02228-f72bb174ba94adca3cb84e1f4
e6a27f0;uas-addr=189.XXX.XXX.XXX;rport..Via: SIP/2.0/UDP 192.168.0.194:5060;branch=z9hG4bK1c6cfefbb768d950;rport=5060;received=192.168.0.194
..CSeq: 1 REGISTER..Call-ID: D1B9-11D3-466848172A2D163AA9F3-001@SipHost..Contact: <sip:555@189.XXX.XXX.XXX:8072>..User-Agent: OSBC-1.1.5..E
xpir

I think, that line in bold, must be 189.XXX.XXX.XXX:8070 -> 192.168.0.25:8060

Because I have a route in my UpperReg route...

Thanks...

dcardosoa

28 posts since
Feb 12, 2008

3. May 6, 2008 9:50 AM

in response to: dcardosoa

Re: B2B UpperReg Problem

I think that there is a BUG in OpenSBC 1.1.5-4.

I try use the B2B UpperReg mode on port 8070 and the UPPER REGISTER does not work, other functions are ok...

but when I use B2B UpperReg mode on port 5060, it work ALL perfect, include the UPPER REGISTER...

Pls let me know if I correct or wrong...

Thanks...

Guest

4. May 7, 2008 1:34 AM

in response to: dcardosoa

RE: [OpenSBC] B2B UpperReg Problem

Hi,

The bug is in SBCConfigParams.h.

Change:

static const char configKeyUpperRegistrarSection[] = "Upper-Registrations";

to

static const char configKeyUpperRegistrarSection[] = "Upper-Registration";

I hope this help

Date: Tue, 6 May 2008 09:50:38 -0400> From: opensipstack-osbcdevel@opensourcesip.org> To: opensipstack-osbcdevel@lists.sourceforge.net> Subject: Re: OpenSBC B2B UpperReg Problem> > > I think that there is a BUG in OpenSBC 1.1.5-4. > > > > > > I try use the B2B UpperReg mode on port 8070 and the UPPER REGISTER does not work, other functions are ok...> > > but when I use B2B UpperReg mode on port 5060, it work ALL perfect, include the UPPER REGISTER...> > > > > > Pls let me know if I correct or wrong... > > > > > > Thanks...> > > > -------------------------------------------------------------------------> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone> _______________________________________________> Opensipstack-osbcdevel mailing list> Opensipstack-osbcdevel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel

_________________________________________________________________
Ingresá ya a MSN en Concierto y disfrutá los recitales en vivo de tus artistas favoritos.
http://msninconcert.msn.com/music/archive/es-la/archive.aspx
http://att1.html

Attachments:

att1.html (2.1 K)

Guest

5. May 6, 2008 9:24 PM

in response to: Guest

Re: [OpenSBC] B2B UpperReg Problem

Hi Gustavo,

Thanks for the report. I have submitted the patch in CVS

Joegen

Gustavo Curetti wrote:

Hi,

The bug is in SBCConfigParams.h.

Change:

static const char configKeyUpperRegistrarSection[] =
"Upper-Registrations";

to

static const char configKeyUpperRegistrarSection[] = "Upper-Registration";

I hope this help

Date: Tue, 6 May 2008 09:50:38 -0400
From: opensipstack-osbcdevel@opensourcesip.org
To: opensipstack-osbcdevel@lists.sourceforge.net
Subject: Re: OpenSBC B2B UpperReg Problem

I think that there is a BUG in OpenSBC 1.1.5-4.

I try use the B2B UpperReg mode on port 8070 and the UPPER REGISTER

does not work, other functions are ok...

but when I use B2B UpperReg mode on port 5060, it work ALL perfect,

include the UPPER REGISTER...

Pls let me know if I correct or wrong...

Thanks...

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.

http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Opensipstack-osbcdevel mailing list
Opensipstack-osbcdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel

Ingresá ya a MSN en Concierto y disfrutá los recitales en vivo de tus
artistas favoritos. MSN en Concierto
<http://msninconcert.msn.com/music/archive/es-la/archive.aspx>

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Opensipstack-osbcdevel mailing list
Opensipstack-osbcdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel

Internal Virus Database is out-of-date.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.6/1404 - Release Date: 4/29/2008 6:27 PM

joegen

125 posts since
Apr 28, 2007

6. May 6, 2008 9:30 PM

in response to: dcardosoa

Re: B2B UpperReg Problem

Hi,

Gustavo pointed out a typo in SBCConfigParams.h. See his comments below. Can you check if this is causing upper reg not to work for you?

Joegen

Gustavo Curetti wrote:

I hope this help

dcardosoa wrote:

I think that there is a BUG in OpenSBC 1.1.5-4.

I try use the B2B UpperReg mode on port 8070 and the UPPER REGISTER does not work, other functions are ok...

but when I use B2B UpperReg mode on port 5060, it work ALL perfect, include the UPPER REGISTER...

Pls let me know if I correct or wrong...

Thanks...

dcardosoa

28 posts since
Feb 12, 2008

7. May 8, 2008 3:20 PM

in response to: joegen

Re: B2B UpperReg Problem

Thanks
Gustavo and
Joegen...

I changed the code and now it works perfect...

thanks...

Go to original post

May 5, 2008 5:05 PM

B2B UpperReg Problem

Actions

More Like This