Up to Discussions in OpenSBC

This Question is Answered

2 "helpful" answers available (1 pts)
10 Replies Last post: Oct 16, 2009 11:21 PM by joegen  
Click to view Diego-UY's profile  
Diego-UY
10 posts since
Sep 14, 2009

Oct 2, 2009 3:53 PM

Register URI and incoming calls


Hi all, i have problems with incoming calls and i see that i'm receiving at my softswitch the URI in a different format that we are expecting.

I have configured opensbc as upper-reg

We are receiving from opensbc: URI: <sip:x-reg-id-sip%3AUSERNAME%40xxx.yyy.zzz.163%3A5060@xxx.zzz.yyy.82:5062> where:

USERNME= Sip User
xxx.yyy.zzz.163= IAD IP
xxx.zzz.yyy.82= OpenSBC public address.

The first visible problem is that xxx.zzz.yyy.82 should be the private ip of the opensbc and not the public, how can i change it?

The second problem is: x-reg-id-sip%3AUSERNAME%40xxx.yyy.zzz.163%3A506: how can i modify it to leave only the username?

Click to view Diego-UY's profile  
Diego-UY
10 posts since
Sep 14, 2009
1. Oct 5, 2009 2:21 PM in response to: Diego-UY
Re: Register URI and incoming calls
I found that on the forum http://www.opensourcesip.org:8080/clearspacex/message/9981 i tried to set-up back-door with the correct information but still sending the wrong ip address as contact.


I'm using the version: 1.1.5-108

Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
2. Oct 6, 2009 9:51 PM in response to: Diego-UY
Re: Register URI and incoming calls

Two things. If you are using opensbc in a linux environment, try recompiling it with --enable-gpllibs as argument to configure.

  1. ./configure --enable-gpllibs; make clean; make

This would enable IPRoute2 usage in OpenSBC which helps it determine the correct interface using kernel level system calls. Your other option is to manually help opensbc determine to correct interface. See SIP-Transports/Interface-Route-List in the config pages.

Click to view mpicher's profile  
mpicher
40 posts since
Dec 28, 2008
3. Oct 8, 2009 4:56 AM in response to: joegen
Re: Register URI and incoming calls
Where would this fit into this procedure for compiling on Linux?

1. su
2. cd /usr/src/opensipstack
3. chmod +x ./configure
4. ./configure
5. make bothnoshared
6. cd ../opensbc
7. chmod +x ./configure
8. ./configure
9. make bothnoshared
10. make distrib

This is from my instructions for OpenSBC on Vyatta and I believe the same thing is happening on the systems I built. I assume this goes on line 9 somehow?

Thanks,

Mike

Click to view mpicher's profile  
mpicher
40 posts since
Dec 28, 2008
4. Oct 8, 2009 4:50 AM in response to: mpicher
Re: Register URI and incoming calls
Joegen,

I did what you suggested because I was seeing similar issues on the OpenSBC / Vyatta boxes I built, however, what I'm seeing on a sipXecs Registrations page looks like:


We are receiving from opensbc: URI: <sip:x-reg-id-sip%3AUSERNAME%40xxx.yyy.zzz.163%3A5060@xxx.zzz.yyy.82:5062> where:

USERNME= Sip User
xxx.yyy.zzz.163= IAD IP
xxx.zzz.yyy.82= OpenSBC public address.

xxx.zzz.yyy.82 should be the private
ip of the opensbc / vyatta firewall....

xxx.zzz.yyy.82:5062 is showing as 127.0.0.1:5062 on the sipXecs registration page.

Thanks for your help as always!


Mike

Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
5. Oct 9, 2009 8:31 AM in response to: mpicher
Re: Register URI and incoming calls

Hi Mike,

Made a couple of patches in CVS to correct this situation using SIP-Transport/Interface-Route-List if IP-Route2 is still not solving the issue. Just add something like [sip:ip_of_sipx] sip:private_ip_of_vyatta. Just in case you havent fugured out yet, iproute2 support would be enabled during opensipstack compilation using --enable-gpllibs option. Please send me the log offlist (joegen at opensisptack dot org) together with the real IP info if you think the patch didnt solve it. Thanks.

Joegen

Click to view mpicher's profile  
mpicher
40 posts since
Dec 28, 2008
6. Oct 12, 2009 7:20 AM in response to: joegen
Re: Register URI and incoming calls

Hi Joegen,

The registration still looks wrong. I'll forward the log and the ini file.

I've also tryed the SIP-Transport/Interface-Route-List setting and the registrations are still showing in sipXecs registration page with the 127.0.0.1 address.

Does the '--enable-gpllibs' need to be on
the OpenSBC and OpenSipStack ./configure or just the OpenSBC
./configure (i did the latter).

Thanks,

Mike

Click to view Diego-UY's profile  
Diego-UY
10 posts since
Sep 14, 2009
7. Oct 15, 2009 7:18 AM in response to: mpicher
Re: Register URI and incoming calls

Joegen,

I tried with the new version and i'm still getting the same problem. I have configured the route-list as i sent in a separate email.

Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
8. Oct 15, 2009 10:07 PM in response to: Diego-UY
Re: Register URI and incoming calls
Mike Pitcher reported the same problem to me off-list. The work-around was to bind the back-door listener in sip transports to a static ip instead of *:5062. Try that and get back to me if you still ahve a problem.
Click to view Diego-UY's profile  
Diego-UY
10 posts since
Sep 14, 2009
9. Oct 16, 2009 8:30 AM in response to: joegen
Re: Register URI and incoming calls

Joegen it also solve my problem! now i have other issue with the media but it's a different problem.


Thanks!

Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
10. Oct 16, 2009 11:21 PM in response to: Diego-UY
Re: Register URI and incoming calls
Good to hear you got it working.

Actions

More Like This