This Question is Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
18 Replies Last post: Nov 25, 2008 11:21 AM by Guest   1 2 Previous Next
Click to view Vitaly's profile   10 posts since
Nov 12, 2008

Nov 12, 2008 9:06 AM

SipX<=>OpenSBC: inbound route doesn't work


I've configured SIP Trunk on OpenSBC. Calls from sipX to PSTN over sip provider are working well. But when I try to call to my external PSTN number (must be routed to sipX number) I got an Internal error after vey long timeout.

Seems OpenSBC doesn't route calls to sipX.


Help me pls!


My configs:


SBC Mode: B2BOnlyMode


Interface: sip:*:9000


B2BUA Route: sip:44* sip:provider.org;sip-trunk=true


<xml>
<siptrunk trunk-name="provider.org" route-set="provider.org" sip-domain="provider.org" expires="20">
<trunk-accounts>
<account user-name="44444444444" auth-user-name="44444444444" auth-password="mypass" inboundroute="sip:100@sipx.mydomain" expires="3600" />
</trunk-accounts>
<transient-accounts>
<account user-name="44444444444" auth-user-name="44444444444" auth-password="mypass" inboundroute="sip:100@sipx.ebc.mydomain" />
</transient-accounts>
</siptrunk>
</xml>

Click to view joegen's profile   136 posts since
Apr 28, 2007
1. Nov 12, 2008 9:21 AM in response to: Vitaly
Re: SipX<=>OpenSBC: inbound route doesn't work
You might need to put a b2bua route for sip:100@sipx.mydomain. If that does not work, send a level 5 log.

Vitaly wrote:

I've configured SIP Trunk on OpenSBC. Calls from sipX to PSTN over sip provider are working well. But when I try to call to my external PSTN number (must be routed to sipX number) I got an Internal error after vey long timeout.

Seems OpenSBC doesn't route calls to sipX.

Help me pls!

My configs:

SBC Mode: B2BOnlyMode

Interface: sip:*:9000

B2BUA Route: sip:44* sip:provider.org;sip-trunk=true

<xml>
<siptrunk trunk-name="provider.org" route-set="provider.org" sip-domain="provider.org" expires="20">
<trunk-accounts>
<account user-name="44444444444" auth-user-name="44444444444" auth-password="mypass" inboundroute="sip:100@sipx.mydomain" expires="3600" />
</trunk-accounts>
<transient-accounts>
<account user-name="44444444444" auth-user-name="44444444444" auth-password="mypass" inboundroute="sip:100@sipx.ebc.mydomain" />
</transient-accounts>
</siptrunk>
</xml>

Guest
3. Nov 13, 2008 10:52 PM in response to: Vitaly
Re: [OpenSBC] SipX<=>OpenSBC: inbound route doesn't work
Hi,

I have seen the log. Form what I could tell, you are trying to place an
inbound call to a sip-trunk via the main trunk sip listener. That will
not be processed as an inbound trunk call. Instead it will be processed
as outbound. So there is a screw up somewhere. Make sure to send
inbound calls to a siptrunk via the sip-trunk listener.

I am also not 100% clear what your setup is. If you could send a
detailed call diagram of what you want to achieve, so much the better.

Joegen

OpenSBC Forum wrote:

I added B2BUA route sip:100 sip:sipx.ebc.fleurop

Unfortunately it didn't help. I will send the logby mail.

Thanks for reply.


Guest
7. Nov 18, 2008 5:01 AM in response to: Vitaly
Re: [OpenSBC] SipX<=>OpenSBC: inbound route doesn't work
I would start by looking at the log of which UA sent the error. I am
going to assume that your call flow is

UA1 -> SIP-Trunk -> Main Trunk -> SIPX

Upon reaching SIPX what happens to the INVITE? Is it SIPX that's
sending the 500 Internal Server Error?

Joegen

OpenSBC Forum wrote:
Hi Joegen,

Seems I achieved some progress. Inbound calls place to a sip-trunk listener now. But I'm getting Internal Server Errors. Where is my mistake?

340834:04:20.473 INF: CID=0x07a9 &gt;&gt;&gt; SIP/2.0 500 Internal Server Error DST: 10.100.1.37:9000:UDP SRC: 10.100.1.37:9006 enc=0 bytes=443
340834:04:20.473 DBG: CID=0x07a9
340834:04:20.473 DBG: CID=0x07a9 SIP/2.0 500 Internal Server Error
340834:04:20.473 DBG: CID=0x07a9 From: &lt;sip:41325128999@voipgateway.org&gt;;tag=quz8d19vg2
340834:04:20.473 DBG: CID=0x07a9 To: &lt;sip:445551800@voipgateway.org;sip-trunk=true&gt;;tag=7c0ad6efc5b3dd118a28d5799cb4286a
340834:04:20.473 DBG: CID=0x07a9 Via: SIP/2.0/UDP 10.100.1.37:9000;iid=3987;branch=z9hG4bK04c8c7efc5b3dd118a28d5799cb4286a;uas-addr=10.100.1.37;rport=9000;received=10.100.1.37
340834:04:20.473 DBG: CID=0x07a9 CSeq: 1 INVITE
340834:04:20.473 DBG: CID=0x07a9 Call-ID: 3c3a0337c788-s6smov9nh4bh-0x0015
340834:04:20.473 DBG: CID=0x07a9 Server: OpenSIPStack-1.1.7-22
340834:04:20.473 DBG: CID=0x07a9 Content-Length: 0

Thanks for help.


This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Opensipstack-osbcdevel mailing list
Opensipstack-osbcdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.175 / Virus Database: 270.9.4/1794 - Release Date: 11/17/2008 8:48 AM

Guest
9. Nov 18, 2008 9:34 AM in response to: Vitaly
Re: [OpenSBC] SipX<=>OpenSBC: inbound route doesn't work
Now I am confused.

1. Are ext num1 and ext num2 actual SIP User Agents in the signaling path?
2. There seem to be two sip trunks in your call flow. Are you running
two instances of OpenSBC?
3. OpenSBC does not send a 500 Internal Server Error. I am quite sure
it did not come from OSBC. So please dig deeper into your setup and
find out which UA is causing it. I could probably help in the why as
long as you give give me the exact picture.

Joegen

OpenSBC Forum wrote:
I guess it is a sip-trunk error.

Call scheme

UA1->SIP-Trunk -> ext num1 -> ext num2 -> SIP-Trunk -> Main Trunk -> SIPX -> UA2


Guest
10. Nov 18, 2008 9:44 AM in response to: Guest
Re: [OpenSBC] SipX<=>OpenSBC: inbound route doesn't work
In addition, from the looks at the log you sent me, you seem to be
tromboning/hairpining the call back to OpenSBC. So the call goes out
the SIP Trunk and loop back to the SIP trunk again. This will not
work. OpenSBC will not route this call properly in this context.

Joegen E. Baclor wrote:
Now I am confused.

1. Are ext num1 and ext num2 actual SIP User Agents in the signaling path?
2. There seem to be two sip trunks in your call flow. Are you running
two instances of OpenSBC?
3. OpenSBC does not send a 500 Internal Server Error. I am quite sure
it did not come from OSBC. So please dig deeper into your setup and
find out which UA is causing it. I could probably help in the why as
long as you give give me the exact picture.

Joegen

OpenSBC Forum wrote:

I guess it is a sip-trunk error.

Call scheme

UA1->SIP-Trunk -> ext num1 -> ext num2 -> SIP-Trunk -> Main Trunk -> SIPX -> UA2

Guest
12. Nov 18, 2008 12:00 PM in response to: Vitaly
Re: [OpenSBC] SipX<=>OpenSBC: inbound route doesn't work
Hi

I am using a inGate SBC and i am able to hairpin. I did run into a proble
at first but it turned out to be something else. But along the way i was
able to route inbound to the sipX by changing the port away form 5060, just
pick one like 6070 then set up a rule that looked for and took traffic from
port 6070 and set it Forward back to 5060 out to the SBC => ITSP. The other
and final solution was changing the remote phone from Grandstream to Snom
because Grandstream fails in all phones to manage RE-Invites. Lost two
weeks screwing with the Grandstreams.

AT&T analog phone <==> Sip trunk ITSP <==> ((inGate <==> sipX(
registration ) back out <==> SiP Trunk ITSP)(high speed T1)) <==> and ring a
ip phone connected to an AT&T DSL router in another part of the office.

r


Original Message

From: "OpenSBC Forum"
To:
Sent: Tuesday, November 18, 2008 9:50 AM
Subject: Re: OpenSBC SipX<=>OpenSBC: inbound route doesn't work


I guess I can make two calls over sip-trunk at the same time.

I want to test incoming calls but I can't call from PSTN number. So I'm
trying to call from my internal sipx number over sip-trunk to another number
which must be routed to another internal number.


According to this sip-trunk config I dial 44555555555 from number
sip:100@sipx.mydomain and want to be routed to number sip:200@sipx.mydomain


Is it correct?

&lt;xml&gt;
&lt;siptrunk trunk-name="provider.org" route-set="provider.org"
sip-domain="provider.org" expires="20"&gt;
&lt;trunk-accounts&gt;
&lt;account user-name="44444444444" auth-user-name="44444444444"
auth-password="mypass" inboundroute="sip:100@sipx.mydomain" expires="3600"
/&gt;
&lt;account user-name="44555555555" auth-user-name="44555555555"
auth-password="mypass" inboundroute="sip:200@sipx.mydomain" expires="3600"
/&gt;
&lt;/trunk-accounts&gt;
&lt;transient-accounts&gt;
&lt;account user-name="44444444444" auth-user-name="44444444444"
auth-password="mypass" inboundroute="sip:100@sipx.ebc.mydomain" /&gt;
&lt;account user-name="44555555555" auth-user-name="44555555555"
auth-password="mypass" inboundroute="sip:200@sipx.mydomain" /&gt;
&lt;/transient-accounts&gt;
&lt;/siptrunk&gt;
&lt;/xml&gt;

This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Opensipstack-osbcdevel mailing list
Opensipstack-osbcdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel
Click to view joegen's profile   136 posts since
Apr 28, 2007
14. Nov 19, 2008 12:09 AM in response to: Guest
Re: [OpenSBC] SipX<=>OpenSBC: inbound route doesn't work
Threading was screwed up in the OSS Forum so I am reposting this:

Hi Robert,

OpenSBC can do hairpin if you do it correctly. The outbound call should
be sent through the main trunk

UA1 -> OSBC-Main-Trunk -> SIP-Server

When the SIP-Server hairpins/trombones the call back to OpenSBC, it must
either use one of two listeners based on which config applies

    • SIP-Server has static routing policies OR is configured as upper-reg
SIP-Server -> OSBC-BackDoor -> OSBC-Main-Trunk -> UA2

Or

    • SIP-Server configured as a trunk provider
SIP-Server -> OSBC-SIP-Trunk -> OSBC-Main-Trunk -> UA2

In the case of the original poster, he is trying to trombone the call
back to the SIP-Trunk which would cause call-id collisions

Joegen