Re: [SR-Users] ACK problem with FreeSwitch-Kamailio SBC implementation.
Hello,
do you have an alias to server IP address only? If yes, then all ports
will be matched locally and r-uri will be consumed as strict route.
If not, can you run with high debug mode and send the output of ack
routing here?
Cheers,
Daniel
On 1/17/11 9:39 PM, Ricardo Martinez wrote:
Hello.
I was wondering if someone can help me with some problem that I’m
having with the combination of FreeSwitch and Kamailio as SBC.
I’m having and ACK not routed by kamailio and dropped.
Here is the debug.
100.100.100.211:5060 http://100.100.100.211:5060 : Kamailio
100.100.100.211:5090 http://100.100.100.211:5090 : FreeSwitch
100.100.100.108 : Caller
100.100.100.212 : Calle
Request-Line: INVITE sip:02131234@100.100.100.211
mailto:sip%3A02131234@100.100.100.211 SIP/2.0
Method: INVITE
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
64.76.148.108:42772;branch=z9hG4bK-d8754z-da0b2e4b1b5d0843-1---d8754z-;rport
Max-Forwards: 70
Contact: sip:1234@64.76.148.108:42772
http://sip:1234@64.76.148.108:42772
To: sip:02131234@100.100.100.211
mailto:sip%3A02131234@100.100.100.211
From: camilasip:1234@100.100.100.211
mailto:sip%3A1234@100.100.100.211;tag=8422566b
Call-ID: MjY2NDY5NTE3OTk4MzdmMjE0YWQxNWQ4MWFmY2JhMWQ.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY,
MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: Bria release 2.2 stamp 45414
Content-Length: 388
Message Body
Session Description Protocol
Status-Line: SIP/2.0 100 trying -- your call is important to us
Status-Code: 100
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
64.76.148.108:42772;branch=z9hG4bK-d8754z-da0b2e4b1b5d0843-1---d8754z-;rport=42772
To: sip:02131234@100.100.100.211
mailto:sip%3A02131234@100.100.100.211
From: camilasip:1234@100.100.100.211
mailto:sip%3A1234@100.100.100.211;tag=8422566b
Call-ID: MjY2NDY5NTE3OTk4MzdmMjE0YWQxNWQ4MWFmY2JhMWQ.
CSeq: 1 INVITE
Server: kamailio (3.1.1 (i386/linux))
Content-Length: 0
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
64.76.148.108:42772;branch=z9hG4bK-d8754z-da0b2e4b1b5d0843-1---d8754z-;rport=42772
Record-Route: sip:100.100.100.211;lr=on
From: camila sip:1234@100.100.100.211
mailto:sip%3A1234@100.100.100.211;tag=8422566b
To: sip:02131234@100.100.100.211
mailto:sip%3A02131234@100.100.100.211;tag=pBZjZayFUeDSp
Call-ID: MjY2NDY5NTE3OTk4MzdmMjE0YWQxNWQ4MWFmY2JhMWQ.
CSeq: 1 INVITE
Contact: sip:02131234@100.100.100.211:5090;transport=udp
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-d41e649
2011-01-11 12-25-55 -0600
Accept: application/sdp
Message Body
Session Description Protocol
Request-Line: ACK sip:02131234@100.100.100.211:5090;transport=udp
SIP/2.0
Method: ACK
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
64.76.148.108:42772;branch=z9hG4bK-d8754z-182d537bcb534165-1---d8754z-;rport
Max-Forwards: 70
Route: sip:100.100.100.211;lr
Contact: sip:1234@64.76.148.108:42772
http://sip:1234@64.76.148.108:42772
To: sip:02131234@100.100.100.211
mailto:sip%3A02131234@100.100.100.211;tag=pBZjZayFUeDSp
From: camilasip:1234@100.100.100.211
mailto:sip%3A1234@100.100.100.211;tag=8422566b
Call-ID: MjY2NDY5NTE3OTk4MzdmMjE0YWQxNWQ4MWFmY2JhMWQ.
CSeq: 1 ACK
User-Agent: Bria release 2.2 stamp 45414
Content-Length: 0
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: True]
[Suspected resend of frame: 7]
Message Header
Via: SIP/2.0/UDP
64.76.148.108:42772;branch=z9hG4bK-d8754z-da0b2e4b1b5d0843-1---d8754z-;rport=42772
Record-Route: sip:100.100.100.211;lr=on
From: camila sip:1234@100.100.100.211
mailto:sip%3A1234@100.100.100.211;tag=8422566b
To: sip:02131234@100.100.100.211
mailto:sip%3A02131234@100.100.100.211;tag=pBZjZayFUeDSp
Call-ID: MjY2NDY5NTE3OTk4MzdmMjE0YWQxNWQ4MWFmY2JhMWQ.
CSeq: 1 INVITE
Contact: sip:02131234@100.100.100.211:5090;transport=udp
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-d41e649
2011-01-11 12-25-55 -0600
Accept: application/sdp
Message Body
Session Description Protocol
When I removed Freeswitch from the path the ACK is routed ok.
The ACK is routed by loose_route, but then it fails because the
if ( t_check_trans() ) {
What could be happening?
Regards,
Ricardo.-
*Ricardo Martínez **|* Ingeniero de Desarrollo
RedVoiss *|*rmarti...@redvoiss.net mailto:rmarti...@redvoiss.net
Santiago- Chile *|*+56 2 2408196
www.redvoiss.net http://www.redvoiss.net
[SR-Users] ACK problem with FreeSwitch-Kamailio SBC implementation.
Hello. I was wondering if someone can help me with some problem that I’m having with the combination of FreeSwitch and Kamailio as SBC. I’m having and ACK not routed by kamailio and dropped. Here is the debug. 100.100.100.211:5060 : Kamailio 100.100.100.211:5090 : FreeSwitch 100.100.100.108 : Caller 100.100.100.212 : Calle User Datagram Protocol, Src Port: 42772 (42772), Dst Port: sip (5060) Session Initiation Protocol Request-Line: INVITE sip:02131234@100.100.100.211sip%3A02131234@100.100.100.211SIP/2.0 Method: INVITE [Resent Packet: False] Message Header Via: SIP/2.0/UDP 64.76.148.108:42772 ;branch=z9hG4bK-d8754z-da0b2e4b1b5d0843-1---d8754z-;rport Max-Forwards: 70 Contact: sip:1234@64.76.148.108:42772 To: sip:02131234@100.100.100.211 sip%3A02131234@100.100.100.211 From: camilasip:1234@100.100.100.211 sip%3A1234@100.100.100.211 ;tag=8422566b Call-ID: MjY2NDY5NTE3OTk4MzdmMjE0YWQxNWQ4MWFmY2JhMWQ. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Content-Type: application/sdp User-Agent: Bria release 2.2 stamp 45414 Content-Length: 388 Message Body Session Description Protocol User Datagram Protocol, Src Port: sip (5060), Dst Port: 42772 (42772) Session Initiation Protocol Status-Line: SIP/2.0 100 trying -- your call is important to us Status-Code: 100 [Resent Packet: False] Message Header Via: SIP/2.0/UDP 64.76.148.108:42772 ;branch=z9hG4bK-d8754z-da0b2e4b1b5d0843-1---d8754z-;rport=42772 To: sip:02131234@100.100.100.211 sip%3A02131234@100.100.100.211 From: camilasip:1234@100.100.100.211 sip%3A1234@100.100.100.211 ;tag=8422566b Call-ID: MjY2NDY5NTE3OTk4MzdmMjE0YWQxNWQ4MWFmY2JhMWQ. CSeq: 1 INVITE Server: kamailio (3.1.1 (i386/linux)) Content-Length: 0 User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: INVITE sip:3031234@100.100.100.212:5060 SIP/2.0 Method: INVITE [Resent Packet: False] Message Header Record-Route: sip:100.100.100.211;lr=on Via: SIP/2.0/UDP 100.100.100.211;branch=z9hG4bK3916.41fc6fb3.0 Via: SIP/2.0/UDP 100.100.100.211:5090 ;rport=5090;branch=z9hG4bK1QH1XDH609cUm Max-Forwards: 66 From: camila sip:1234@100.100.100.211sip%3A1234@100.100.100.211 ;tag=QmrB15eKrQ3Bj To: sip:02131234@100.100.100.211 sip%3A02131234@100.100.100.211 Call-ID: 54a74b6a-9cf6-122e-05a0-0050bad00883 CSeq: 7304076 INVITE Contact: sip:mod_sofia@100.100.100.211:5090 User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-d41e649 2011-01-11 12-25-55 -0600 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Allow-Events: talk, hold, presence, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 200 X-FS-Support: update_display Remote-Party-ID: camila sip:1234@100.100.100.211sip%3A1234@100.100.100.211 ;party=calling;screen=yes;privacy=off Message Body Session Description Protocol User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 100 Trying Status-Code: 100 [Resent Packet: False] Message Header Via: SIP/2.0/UDP 100.100.100.211;branch=z9hG4bK3916.41fc6fb3.0;received=100.100.100.211 Via: SIP/2.0/UDP 100.100.100.211:5090 ;rport=5090;branch=z9hG4bK1QH1XDH609cUm Record-Route: sip:100.100.100.211;lr=on From: camila sip:1234@100.100.100.211sip%3A1234@100.100.100.211 ;tag=QmrB15eKrQ3Bj To: sip:02131234@100.100.100.211 sip%3A02131234@100.100.100.211 Call-ID: 54a74b6a-9cf6-122e-05a0-0050bad00883 CSeq: 7304076 INVITE Server: Thirdlane Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces, timer Require: timer Session-Expires: 1800;refresher=uas Contact: sip:3031234@100.100.100.212sip%3A3031234@100.100.100.212 Content-Length: 0 User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 OK Status-Code: 200 [Resent Packet: False] Message Header Via: SIP/2.0/UDP 100.100.100.211;branch=z9hG4bK3916.41fc6fb3.0;received=100.100.100.211 Via: SIP/2.0/UDP 100.100.100.211:5090 ;rport=5090;branch=z9hG4bK1QH1XDH609cUm Record-Route: sip:100.100.100.211;lr=on From: camila
