Open Source Sip: Inbound calls not routed properly ...

Up to Discussions in OpenSBC

This Question is Answered

1 "correct" answer available (5 pts)

28 Replies Last post: Dec 1, 2009 5:44 AM by mpicher 1 2 Previous Next

cbntech

18 posts since
Aug 13, 2009

Sep 12, 2009 2:44 PM

Inbound calls not routed properly

Hi All !

First things first, I would like to express my admiration for all the work that has been put into that product! Did setup the server in a few hours ( used the tutorial written by Michael W. Picher) . Can make calls out whithout problems, using PBX in A Flash as upper registrar and gateway. To receive calls is another story... At first, calls would come in, phone would ring, but conversation length would be only a few seconds. Now phones does not ring at all.

Looking at the logs, can see is sent to port 5061 ..... why ? I dunno

Can you please tell me what I did wrong ? Here is my configuration file:

OpenSBC internal interface= 192.168.20.20

OpenSBC external interface= 123.456.96.31

PBX in a Flash (Registrar) = 192.168.20.7

Phone = 123.456.96.35

++++++++++++++++++++++++++++++++++++++++Opensbc.ini++++++++++++++++++++++++++++++++++++++++

[OpenSBC-General-Parameters]
SIP-Log-Level=4
PTRACE-Log-Level=5
Log-File-Prefix=b2bua
SBC-Application-Mode=B2BUpperReg Mode
Enable-Trunk-Port=True
Enable-Calea-Port=True
RTP-Min-Port=10000
RTP-Max-Port=20000
NAT-Keep-Alive-Interval=15
Send-OPTIONS-NAT-Keep-Alive=False
Send-Responses-Using-New-Socket=False
Enable-Local-Refer=True
Disable-Refer-Optimization=False
Max-Forwards=70
Encryption-Mode=XOR
Encryption-Key=GS
Alerting-Timeout=30000
Seize-Timeout=60000
SIP-Timer-B=Default
SIP-Timer-H=Default
Session-Keep-Alive=1800
Session-Max-Life-Span=10800
Max-Concurrent-Session=100
Max-Call-Rate-Per-Second=10
Interface-Address 1=sip:192.168.20.20:9000

[Upper-Registration]
All-Reg-As-Upper-Reg=True
Enable-Stateful-Reg=False
Rewrite-TO-Domain=True
Rewrite-FROM-Domain=True
Route-List Array Size=1
Route-List 1=[sip:*@123.456.96.31] sip:192.168.20.7:5060

[SIP-Transports]
Main-Interface-Address Array Size=2
Main-Interface-Address 1=sip:192.168.20.20:5060
Backdoor-Interface-Address=sip:192.168.20.20:5061
Trunk-Interface-Address=sip:192.168.20.20:5064
Media-Server-Interface-Address=sip:192.168.20.20:5066
CALEA-Interface-Address=sip:*:5068
Auxiliary-Interface-Address=sip:*:5070
Interface-Route-List Array Size=0
Main-Interface-Address 2=sip:123.456.96.31:5060

[B2BUA-Routes]
Route-List Array Size=1
Route-List 1=[sip:*@123.456.96.31] sip:192.168.20.7
Insert-Route-Header=True
Rewrite-TO-URI=True
Prepend-ISUP-OLI=False
Route-By-Request-URI=True
Route-By-To-URI=False
Drop-Routes-On-Ping-Timeout=False
Use-External-XML=False
External-XML-File=b2bua-route.xml

[Local-Domain-Accounts]
Accept-All-Registration=True
Account-List Array Size=0

[Trusted-Domains]
Accept-All-Calls=True
Trusted-Domain-List Array Size=0

[RTP-Proxy]
Proxy-On-Private-Contact=True
Proxy-On-via-received-vs-signaling-address=True
Proxy-On-Private-Via=True
Proxy-On-Different-RPORT=True
Proxy-All-Media=True

[Internal-DNS-Mapping]
Internal-DNS-Map Array Size=0

[OpenSBC HTTP Admin]
HTTP User=maint
HTTP Password=Ssowwy+sINl0X4fPcMzMKA==
SMTP Return Address=noreply@localhost
SMTP User=maint
SMTP Password=Ssowwy+sINmPOuS/UPvCEQ==
SMTP Server=localhost

[Media-Server]
Enable-Media-Server=False
Media-Server-Number=5000
Codec-List Array Size=0
No-RTP-Proxy-On-All-Transfers=False
Enable-Announcement-Service=False
4xx-Error-Map=prompts/basic/cant_complete.wav
5xx-Error-Map=prompts/basic/cant_complete.wav
6xx-Error-Map=prompts/basic/cant_complete.wav
Announcement-Error-Map Array Size=0

=========================================Call Log ==================================================================

[CID=0xe76b8933] OPTIONS sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] From: "Unknown" <sip:Unknown@192.168.20.7>;tag=as030ff2af
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] To: <sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061>
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Via: SIP/2.0/UDP 192.168.20.7:5060;branch=z9hG4bK1b2a01aa;rport=5060;received=192.168.20.7
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] CSeq: 102 OPTIONS
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Call-ID: 035e3cd04b6ba725432c202049589b1d@192.168.20.7
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Contact: <sip:Unknown@192.168.20.7>
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Date: Sat, 12 Sep 2009 16:28:36 GMT
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] User-Agent: Asterisk PBX
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Max-Forwards: 70
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Supported: replaces
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933] Content-Length: 0
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933]
2009/09/12 16:28:36.373 DBG: [CID=0xe76b8933]
2009/09/12 16:28:36.374 DTL: [CID=0xe76b8933] NIST(685357562) *** CREATED *** - NIST|035e3cd04b6ba725432c202049589b1d@192.168.20.7|z9hG4bK1b2a01aa|OPTIONS
2009/09/12 16:28:36.374 DTL: [CID=0xe76b8933] NIST(685357562) Event(SIPMessage) - OPTIONS sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0
2009/09/12 16:28:36.374 DBG: [CID=0xe76b8933] TRANSACTION: (NIST) OPTIONS sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0 State: 0
2009/09/12 16:28:36.375 DTL: [CID=0xe76b8933] NIST(685357562) StateIdle->StateTrying
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7]
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] Found NIST|035e3cd04b6ba725432c202049589b1d@192.168.20.7|z9hG4bK1b2a01aa|OPTIONS for SIP/2.0 200 OK
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] From: "Unknown" <sip:Unknown@192.168.20.7>;tag=as030ff2af
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] To: <sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061>
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] Via: SIP/2.0/UDP 192.168.20.7:5060;branch=z9hG4bK1b2a01aa;rport=5060;received=192.168.20.7
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] CSeq: 102 OPTIONS
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] Call-ID: 035e3cd04b6ba725432c202049589b1d@192.168.20.7
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] Server: OpenSBC v1.1.6-0
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS, PRACK
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7] Content-Length: 0
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7]
2009/09/12 16:28:36.375 DTL: [CID=0x4e67c6a7]
2009/09/12 16:28:36.376 DTL: [CID=0xe76b8933] NIST(685357562) Event(SIPMessage) - SIP/2.0 200 OK
2009/09/12 16:28:36.376 DBG: [CID=0xe76b8933] TRANSACTION: (NIST) SIP/2.0 200 OK State: 1
2009/09/12 16:28:36.376 DTL: [CID=0xe76b8933] NIST(685357562)HandleStateTrying->StateCompleted
2009/09/12 16:28:36.378 INF: [CID=0xe76b8933] >>> SIP/2.0 200 OK Method(OPTIONS) DST: 192.168.20.7:5060:UDP SRC: 192.168.20.20:5060 enc=0 bytes=428
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933]
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] SIP/2.0 200 OK
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] From: "Unknown" <sip:Unknown@192.168.20.7>;tag=as030ff2af
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] To: <sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061>
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] Via: SIP/2.0/UDP 192.168.20.7:5060;branch=z9hG4bK1b2a01aa;rport=5060;received=192.168.20.7
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] CSeq: 102 OPTIONS
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] Call-ID: 035e3cd04b6ba725432c202049589b1d@192.168.20.7
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] Server: OpenSBC v1.1.6-0
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS, PRACK
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933] Content-Length: 0
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933]
2009/09/12 16:28:36.378 DBG: [CID=0xe76b8933]
2009/09/12 16:28:36.378 PWL: [CID=0x00000000] Using Iface: 192.168.20.20 to send to Dest: 192.168.20.7
2009/09/12 16:28:42.036 INF: [CID=0xbd53c8ca] <<< INVITE sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0 Method(INVITE) SRC: 192.168.20.7:5060:UDP enc=0 bytes=XXX
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca]
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] INVITE sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] From: "250XXX6723" <sip:250XXX6723@192.168.20.7>;tag=as79db459b
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] To: <sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061>
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Via: SIP/2.0/UDP 192.168.20.7:5060;branch=z9hG4bK1b081d6e;rport=5060;received=192.168.20.7
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] CSeq: 102 INVITE
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Call-ID: 3f3542e54837e78975f7442676c71688@192.168.20.7
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Contact: <sip:250XXX6723@192.168.20.7>
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Date: Sat, 12 Sep 2009 16:28:42 GMT
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] User-Agent: Asterisk PBX
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Max-Forwards: 70
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Supported: replaces
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Content-Type: application/sdp
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] Content-Length: 262
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca]
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] v=0
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] o=root 24502 24502 IN IP4 192.168.20.7
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] s=session
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] c=IN IP4 192.168.20.7
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] t=0 0
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] m=audio 15166 RTP/AVP 0 8 101
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] a=rtpmap:0 PCMU/8000
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] a=rtpmap:8 PCMA/8000
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] a=rtpmap:101 telephone-event/8000
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] a=fmtp:101 0-16
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] a=silenceSupp:off - - - -
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] a=ptime:20
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca] a=sendrecv
2009/09/12 16:28:42.036 DBG: [CID=0xbd53c8ca]
2009/09/12 16:28:42.038 DTL: [CID=0xbd53c8ca] IST(685357563) *** CREATED *** - IST|3f3542e54837e78975f7442676c71688@192.168.20.7|z9hG4bK1b081d6e|INVITE
2009/09/12 16:28:42.038 DTL: [CID=0xbd53c8ca] IST(685357563) Event(SIPMessage) - INVITE sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0
2009/09/12 16:28:42.038 DBG: [CID=0xbd53c8ca] TRANSACTION: (IST) INVITE sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0 State: 0
2009/09/12 16:28:42.039 DBG: [CID=0xbd53c8ca] Event: SIPStack::Enqueue(INVITE sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0)
2009/09/12 16:28:42.041 INF: [CID=0xbd53c8ca] >>> SIP/2.0 100 Trying Method(INVITE) DST: 192.168.20.7:5060:UDP SRC: 192.168.20.20:5060 enc=0 bytes=340
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca]
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca] SIP/2.0 100 Trying
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca] From: "250XXX6723" <sip:250XXX6723@192.168.20.7>;tag=as79db459b
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca] To: <sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061>
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca] Via: SIP/2.0/UDP 192.168.20.7:5060;branch=z9hG4bK1b081d6e;rport=5060;received=192.168.20.7
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca] CSeq: 102 INVITE
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca] Call-ID: 3f3542e54837e78975f7442676c71688@192.168.20.7
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca] Content-Length: 0
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca]
2009/09/12 16:28:42.041 DBG: [CID=0xbd53c8ca]
2009/09/12 16:28:42.041 PWL: [CID=0x00000000] Using Iface: 192.168.20.20 to send to Dest: 192.168.20.7
2009/09/12 16:28:42.042 DBG: [CID=0xbd53c8ca] Event: B2BUserAgent::ProcessEvent( INVITE sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0 )
2009/09/12 16:28:42.042 DBG: [CID=0xbd53c8ca] Event: Setting UA Core [Call] to handle event INVITE
2009/09/12 16:28:42.043 DTL: [CID=0xbd53c8ca] Event: ---> Inbound - INVITE sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 SIP/2.0
2009/09/12 16:28:42.043 DBG: [CID=0xbd53c8ca] Session CREATED
2009/09/12 16:28:42.043 INF: [CID=0xbd53c8ca] *** CREATED (UAS) CALL *** Call-ID: 3f3542e54837e78975f7442676c71688@192.168.20.7
2009/09/12 16:28:42.044 DBG: [CID=0xbd53c8ca] Multidirectional Session CREATED
2009/09/12 16:28:42.044 DBG: [CID=0xbd53c8ca] B2BUAConnection Created 0x0x9fc4d38
2009/09/12 16:28:42.044 DBG: [CID=0xbd53c8ca] *** COUNTERS *** (Constructor)ICT=0 NICT=0 IST=1 NIST=1 TIMERS=3 CALL=1 CONN=1 REG=0 RTP=0 QUEUE=0 CACHE=0 GC=2 TOTALCONN=14 TOTALREG=0 TOTALSZR=0 AVGDUR=0 HIGHDUR=0 IDLETIME=0
2009/09/12 16:28:42.045 DBG: [CID=0xbd53c8ca] *** NO REGISTRATION FOUND *** Fetching route through local database URI sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061
2009/09/12 16:28:42.045 INF: [CID=0xbd53c8ca] *** UPPER REGISTRATION FOUND *** -->> Callee: sip:250XXX6723@192.168.20.7 AOR: sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 BINDING: sip:5046@123.456.96.35:5060
2009/09/12 16:28:42.045 INF: [CID=0xbd53c8ca] *** STATIC ROUTE FOUND *** sip:x-reg-id-sip%3A5046%40123.456.96.35%3A5060@123.456.96.31:5061 >>> sip:5046@123.456.96.35:5060
2009/09/12 16:28:42.045 DBG: [CID=0xbd53c8ca] *** MESSAGE ARRIVAL *** for SIP Session 3f3542e54837e78975f7442676c71688@192.168.20.7
2009/09/12 16:28:42.046 DBG: [CID=0x4e67c6a7] CREATED via=192.168.20.20:5060 for target=192.168.20.20 protocol=UDP
2009/09/12 16:28:42.047 DBG: [CID=0xbd53c8ca] Session CREATED
2009/09/12 16:28:42.047 INF: [CID=0xbd53c8ca] *** CREATED (UAC) CALL *** 3f3542e54837e78975f7442676c71688@192.168.20.7-0x000e
2009/09/12 16:28:42.048 DTL: [CID=0xbd53c8ca] Resolving sip:5046@123.456.96.35:5060 -> 123.456.96.35
2009/09/12 16:28:42.048 PWL: [CID=0x00000000] RTP: Media Proxy Forced
2009/09/12 16:28:42.049 DBG: [CID=0x4e67c6a7] CREATED via=192.168.20.20:5060 for target=192.168.20.20 protocol=UDP
2009/09/12 16:28:42.049 PWL: [CID=0x00000000] RTP_UDP Session 1 created: 192.168.20.20:10052-10053 ssrc=4265122564
2009/09/12 16:28:42.050 PWL: [CID=0x00000000] RTP Adding session RTP_UDP
2009/09/12 16:28:42.050 PWL: [CID=0x00000000] RTP_UDP SetRemoteSocketInfo: session=1 data channel, new=0.0.0.0:0, local=192.168.20.20:10052-10053, remote=0.0.0.0:0-0
2009/09/12 16:28:42.050 PWL: [CID=0x00000000] RTP_UDP SetRemoteSocketInfo: session=1 control channel, new=0.0.0.0:1, local=192.168.20.20:10052-10053, remote=0.0.0.0:0-1
2009/09/12 16:28:42.050 PWL: [CID=0x00000000] RTP_UDP SetTemporaryRemoteSocketInfo: session=1 data channel, new=192.168.20.20:15166, local=192.168.20.20:10052-10053, remote=0.0.0.0:0-0
2009/09/12 16:28:42.050 PWL: [CID=0x00000000] RTP_UDP SetTemporaryRemoteSocketInfo: session=1 control channel, new=192.168.20.20:15167, local=192.168.20.20:10052-10053, remote=192.168.20.20:15166-15167
2009/09/12 16:28:42.050 INF: [CID=0xbd53c8ca] *** RTP Session CREATED *** l-addr=192.168.20.20 r-addr=192.168.20.7/192.168.20.20 r-port=15166
2009/09/12 16:28:42.051 DBG: [CID=0x4e67c6a7] CREATED via=123.456.96.31:5060 for target=123.456.96.35 protocol=UDP
2009/09/12 16:28:42.051 DBG: [CID=0xbd53c8ca] RTP: Second Leg offer being set from First Leg SDP
2009/09/12 16:28:42.052 PWL: [CID=0x00000000] RTP Found existing session 1
2009/09/12 16:28:42.052 DBG: [CID=0x4e67c6a7] CREATED via=123.456.96.31:5060 for target=123.456.96.31 protocol=UDP
2009/09/12 16:28:42.052 PWL: [CID=0x00000000] RTP_UDP Session 1 created: 123.456.96.31:10054-10055 ssrc=3790774483
2009/09/12 16:28:42.052 PWL: [CID=0x00000000] RTP Adding session RTP_UDP
2009/09/12 16:28:42.053 PWL: [CID=0x00000000] RTP Found existing session 1
2009/09/12 16:28:42.053 DBG: [CID=0xbd53c8ca] RTP: (Audio) SDP Offer being translated to 123.456.96.31:10054
2009/09/12 16:28:42.055 DTL: [CID=0xbd53c8ca] ICT(685357564) *** CREATED *** - ICT|3f3542e54837e78975f7442676c71688@192.168.20.7-0x000e|z9hG4bK04a5b500279ede119b72901e8b3272fb|INVITE
2009/09/12 16:28:42.056 DTL: [CID=0xbd53c8ca] IST(685357563) StateIdle->StateProceeding
2009/09/12 16:28:42.056 DTL: [CID=0xbd53c8ca] ICT(685357564) Event(SIPMessage) - INVITE sip:5046@123.456.96.35:5060 SIP/2.0
2009/09/12 16:28:42.057 DBG: [CID=0xbd53c8ca] TRANSACTION: (ICT) INVITE sip:5046@123.456.96.35:5060 SIP/2.0 State: 0
2009/09/12 16:28:42.058 INF: [CID=0xbd53c8ca] >>> INVITE sip:5046@123.456.96.35:5060 SIP/2.0 Method(INVITE) DST: 123.456.96.35:5060:UDP SRC: 123.456.96.31:5060 enc=0 bytes=873
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca]
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] INVITE sip:5046@123.456.96.35:5060 SIP/2.0
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] From: "250XXX6723" <sip:250XXX6723@192.168.20.7>;tag=as79db459b
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] To: <sip:5046@123.456.96.35:5060>
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Via: SIP/2.0/UDP 123.456.96.31:5060;iid=2340;branch=z9hG4bK04a5b500279ede119b72901e8b3272fb;uas-addr=123.456.96.35;rport
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] CSeq: 102 INVITE
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Call-ID: 3f3542e54837e78975f7442676c71688@192.168.20.7-0x000e
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Contact: <sip:250XXX6723@123.456.96.31>
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Date: Sat, 12 Sep 2009 16:28:42 GMT
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] User-Agent: OpenSBC v1.1.6-0
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Max-Forwards: 69
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Supported: replaces
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Content-Type: application/sdp
2009/09/12 16:28:42.058 DBG: [CID=0xbd53c8ca] Content-Length: 263

Hope that is enough to spot the problem ........ Thank you very much!

mehedi091

3 posts since
Sep 13, 2009

1. Sep 14, 2009 12:25 AM

in response to: cbntech

Re: Inbound calls not routed properly

Hi,

I have the similar problem. I use Huawei softswitch (softX3000) as sip server. I tried several configuration but incoming call can not possible. Now I followed your configuration file. Now softphone can not register in opensbc but outgoing call from this softphone is possible. I create sip trunk configuration and sip trunk registratio statusis ok.

Please suggest us.

cbntech

18 posts since
Aug 13, 2009

2. Sep 14, 2009 3:10 PM

in response to: mehedi091

Re: Inbound calls not routed properly

My configuration is meant for upper registration, OpenSBC sends the registration info to the registrar (which in my case is asterisk) ... Does your softphone register with your sip server ?

I am still hoping that someone else is going to jump in and help us :-)

joegen

519 posts since
Apr 28, 2007

3. Sep 14, 2009 10:46 PM

in response to: cbntech

Re: Inbound calls not routed properly

The last INVITE that was sent out is meant for the UA. However, that is exactly where you cut your log so there isnt much i could tell what happened to that INVITE based on the info you posted.

cbntech

18 posts since
Aug 13, 2009

4. Sep 15, 2009 12:33 PM

in response to: joegen

Re: Inbound calls not routed properly

Thank you joegen!

Attached is another log ...

OSBC external interface is 255.255.96.31, internal interface is 192.168.20.20

PBXinaflash (asterisk) is 192.168.20.7

Phone adapter is 255.255.96.35

Thanks!

Attachments:

Sept15log.txt (58.2 K)

cbntech

18 posts since
Aug 13, 2009

5. Oct 5, 2009 6:09 PM

in response to: cbntech

Re: Inbound calls not routed properly

For those who have the same problem, here is what solved it:

Under B2BUA-Routes, set Rewrite-TO-URI to false (uncheck that option).

Had one way problem after that, but disabling NAT on the phone adapter fixed it. Thanks to Nate187 for pointing me to the right direction, and big thanks to the developpers of that amazing piece of software (joegen ...)

PS: I have learned a lot about SIP trying to resolved that problem .... Thanks joegen

cbntech

18 posts since
Aug 13, 2009

6. Oct 6, 2009 7:39 PM

in response to: cbntech

Re: Inbound calls not routed properly

Back to starting point

... I thought I had everything in control, ... no, I realized that I had some ports forwarded to the phone adapter ..... so no, it did not work because of the SBC doing NAT traversal. Disabled all port forwarding, now I am back to square 1 ....

Phone registers no problem, outbound calls work fine, except one way audio, but inbound does not .... Please help again

Attached is the last trace

Attachments:

TraceOct609.txt (41.1 K)

joegen

519 posts since
Apr 28, 2007

7. Oct 6, 2009 10:03 PM

in response to: cbntech

Re: Inbound calls not routed properly

Ok. On item at a time. I can see that OpenSBC is sending the INVITE to 123.123.96.35:5060:UDP. I am assuming that 123.123.96.35 is the correct IP address of your external interface. So that part is correct. The second data we have is that OpenSBC thinks that port 5060 is the correct port to send the request to. If OpenSBC is doing NAT traversal, it would mean that port 5060 is the source of the REGISTER request. So the first thing you need to check are the following items

1. check the source port of the REGISTER packet. Is it 5060?

2. check that both contact and via address of the REGISTER request is the private IP address of your UA.

GEt back to me with your findings

cbntech

18 posts since
Aug 13, 2009

8. Oct 7, 2009 1:59 AM

in response to: joegen

Re: Inbound calls not routed properly

Thanks joegen for your reply, and your methodological approach; here is what I have:

OpenSBC is sending the INVITE to 123.123.96.35:5060:UDP which is the WAN IP of the router where the external UA is connected

1. check the source port of the REGISTER packet. Is it 5060? Yes it is 5060

2. check that both contact and via address of the REGISTER request is the private IP address of your UA. No... Both via and contact address of the register is the public IP address of the UA

2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] REGISTER sip:5069@192.168.20.7:5060 SIP/2.0
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] From: <sip:5069@123.123.96.31>;tag=1d3aad729fac1438o0
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] To: <sip:5069@123.123.96.31>
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Via: SIP/2.0/UDP 123.123.96.31:5060;branch=z9hG4bK76fcbfa83db1de119745fd64f2e345d7;uas-addr=172.20.20.7
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Via: SIP/2.0/UDP 123.123.96.35:2068;branch=z9hG4bK-cd4ed48a;rport=2068;received=123.123.96.35
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] CSeq: 7864 REGISTER
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Call-ID: da5de1dc-2ccf5acb@123.123.96.35
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Contact: <sip:x-reg-id-sip%3A5069%40123.123.96.35%3A5060@123.123.96.31:5062>;expires=3600
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] User-Agent: Linksys/PAP2T-3.1.15(LS)
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Max-Forwards: 70
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Authorization: Digest username="5069", realm="asterisk", nonce="06eccecf", uri="sip:123.123.96.31", algorithm=MD5, response="7562c563808bd4f23950b10a78491bb8"
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Supported: x-sipura
2009/10/06 23:28:45.001 DBG: [CID=0xbc4f59c4] Content-Length: 0

Thanks for your help !

joegen

519 posts since
Apr 28, 2007

9. Oct 7, 2009 2:14 AM

in response to: cbntech

Re: Inbound calls not routed properly

{quote:title=cbntech wrote:}{quote}

2. check that both contact and via address of the REGISTER request is the private IP address of your UA. No... Both via and contact address of the register is the public IP address of the UA

This is exactly what is causing the problem. For Far end NAT traversal to work, the UA using the SBC must be honest about their real IP addresses. In your case, the UA is masquerading as the external (public) IP addresses. This makes Op[enSBC beleives that both the UA and your NAT device are one and the same, and thus, would simply honor the contact address sent in the REGISTER. Disable all NAT options in your user agent should do the trick for you.

cbntech

18 posts since
Aug 13, 2009

10. Oct 7, 2009 2:13 PM

in response to: joegen

Re: Inbound calls not routed properly

Thanks a lot joegen! I am learning ...

I am using a PAP2T, defaulted, I don't know why the device does that .... There is absolutely no NAT support turned on on the phone adapter .... I will keep digging on Linksys site and let you know!

Again, thank you very much!

cbntech

18 posts since
Aug 13, 2009

11. Oct 8, 2009 4:58 AM

in response to: cbntech

Re: Inbound calls not routed properly

I will have to check the exact reason, but looks like the problem is fixed. Because I changed locations, I cannot tell exactly what made the difference:

In the UA I disabled the use of and outbound proxy ....

I plugged the UA in my home network, where I have a pfsense box as firewall .... automatic registration, incoming calls whithout a problem (had to enabled NAT on the asterisk box though ..)

Here is the register message: (via and contact have the private IP )

08:09:08.063 DBG: [CID=0x31342845] REGISTER sip:5067@192.168.20.20.7:5060 SIP/2.0
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] From: <sip:5067@123.123.96.31>;tag=1d478e728f9caa1co0
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] To: <sip:5067@123.123.96.31>
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Via: SIP/2.0/UDP 123.123.96.31:5060;branch=z9hG4bK16cb8e854fb2de119745fd64f2e345d7;uas-addr=192.168.20.7
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Via: SIP/2.0/UDP 10.244.244.15:5060;branch=z9hG4bK-42615e6b;rport=5060;received=XX.XXX.70.111
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] CSeq: 41686 REGISTER
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Call-ID: cbbc6842-2f117bc@10.244.244.15
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Contact: <sip:x-reg-id-sip%3A5067%4010.244.244.15%3A5060%3Bsend-addr%3DXX.XXX.70.111%3A5060@123.123.96.31:5062>;expires=60
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] User-Agent: Linksys/PAP2T-3.1.15(LS)
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Max-Forwards: 70
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Authorization: Digest username="5067", realm="asterisk", nonce="129462e2", uri="sip:123.123.96.31", algorithm=MD5, response="dbb080be5f6fb88bc17255304bb0b12a"
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Supported: x-sipura
2009/10/08 08:09:08.063 DBG: [CID=0x31342845] Content-Length: 0

Again, thanks a bunch, I am learning so many things .....

Message was edited by: cbntech

cbntech

18 posts since
Aug 13, 2009

12. Oct 9, 2009 2:16 PM

in response to: cbntech

Re: Inbound calls not routed properly

OK .... Back to work today, and looks like the problem is with the Linksys router I am using here ...

When plugged in the Linksys, the register requests are sent with the external IP in via and contact fields

When plugged in the pfsense box, UA sends the correct information, but when OSBC proxies the media, it does not seem to put in the right information, does not get the ACK and stops everything, leaving the UA out of the loop. I

Now my problem is how do I deal with these routers ? The system is suppose to be flexible so any device plugged in work right ?

Attached is a log of the call ....

Attachments:

rtplog.txt (41.3 K)

joegen

519 posts since
Apr 28, 2007

13. Oct 16, 2009 11:35 PM

in response to: cbntech

Re: Inbound calls not routed properly

Can't give you a reliable answer to this because you did not give a clear view of your routing strategy. I do not have an idea which network interface faces which UA. From the looks of it, opensbc is using interface address 192.168.20.20 for both sides. One thing that worries me here is that opensbc is designed to reside on a public interface and not a private one. Although it may be configured to work in a private environment, it would require a lot of tweaking up for it to work. If you are really looking for an answer to your issues, provide a network diagram of your routing strategy and give your ini with a thorough explanation why you configured it that way. Perhaps from there, we can tell what you did wrong.

cbntech

18 posts since
Aug 13, 2009

14. Oct 19, 2009 3:33 PM

in response to: joegen

Re: Inbound calls not routed properly

Thanks for your reply!

I actually did a complete reinstall of the system, cause was going to try the compilation with iproute2 support, but ended up following mpicher updated article (was not to sure about how to do it)

Anyway, attached is is my diagram ... OSBC has 2 NICs, one with public ip (123.123.50.31), the other with private(192.168.20.20)

Asterisk is at 192.168.20.7, UAs are at 123.123.50.35 and another one at 234.234.70.111

Right now (with thoses settings) outgoing calls are perfect, incoming calls ring the phone, but no audio, and call is disconnected after a few seconds.

Again, thank you for that amazing product and your help!

Attachments:

OSBC.png (59.1 K)
Incomintest_Oct19_00.txt (73.6 K)
OpenSBC.ini (2.8 K)

Go to original post 1 2 Previous Next

Go to original post

This Question is Answered

Sep 12, 2009 2:44 PM

Inbound calls not routed properly

Actions

More Like This