Hello everyone,
I'm just curious as to see what some of you guys do in regards to
handling a Re-Invite that comes back downstream to a NATTED UAC.
For example, call scenario:
UAC -> Kamailio (Fix Nated Contact) -> PSTN
Re-Invite Occurs:
PSTN -> Kamailio -> UAC
UAC (200 OK w/ NAT RFC1918 contact) -> Kamailio (branch flags at this point
are not notifying of NAT, due to the downstream direction of the INVITE, so
RFC1918 address exists, but does not fix_nated_contact) -> PSTN
PSTN does not appropriately ACK.
So, what are your guys solutions for solving this problem?
Is the best way to add an attribute onto the contact header sent in original
INVITE? Are there other ways of handling? What is the best, cleanest
method. Possible to handle with AVP's?
Thanks in advanced for all of your input!
Sincerely,
Brandon
Hi, am I the only person receiving an auto-reply mail from
acabrera(a)sintys.gov.ar with subject "Ausente" ("Away") for each mail sent to
this list (and perhaps to others)?
I've already sent him a direct mail. However, why do people use such auto-
reply stuf in mail?? this is mail, an asynchronous communication, the receipt
can read the mail whenever he prefers, not need to tell me "I'm away now".
grrrr
--
Iñaki Baz Castillo <ibc(a)aliax.net>
Hello,
Please refer to sip trace: http://pastebin.org/86010.
On LINE 294, PSTN sends the Re-INVITE
On LINE 378, REGISTRAR sends 200 OK to SIP SBC (with RFC 1918 Address, that
is being relayed from the UAC that also sends this same address upon 200 OK
of the Re-Invite).
Let me know if this makes sense, this trace was taken on the SBC.
Hello All,
I need a working example for sending all request to another sip server using
kamailio.
X-lite-->TLS(7161)-->Kamailio-->UDP(5060)-->SIP Server-->PSTN Number. i have
attached my cfg file. The problem is when i dialed any pstn number
everything working fine except the by msg. If the caller send BYE callee get
hangup but if Calle send BYE caller never hangup the call. i got the
following msg on my log file
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_msg:
method: <BYE>
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_msg:
uri: <sip:91131@192.168.10.2:5060>
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_msg:
version: <SIP/2.0>
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=2
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field:
cseq <CSeq>: <1> <BYE>
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:core:parse_via_param: found param type 232, <branch> =
<z9hG4bk010213101521011481381407>; state=16
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_via: end
of header reached, state=5
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
via found, flags=2
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
this is the first via
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:receive_msg:
After parse_msg...
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:receive_msg:
preparing to run routing scripts...
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=100
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to_param:
tag=b23c1531
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to: end
of header reached, state=29
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to:
display={"91131"}, ruri={sip:91131@192.168.10.2:5060}
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field:
<To> [51]; uri=[sip:91131@192.168.10.2:5060]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field:
to body ["91131"<sip:91131@192.168.10.2:5060>]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field:
content_length=0
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field:
found end of header
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:maxfwd:is_maxfwd_present: max_forwards header not found!
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:core:check_via_address: params 192.168.10.2, 192.168.10.2, 0
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=80
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:siputils:has_totag:
totag found
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=200
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:is_preloaded:
is_preloaded: No
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if host==us: 12==13 && [192.168.10.2] == [192.168.10.1]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if port 5060 matches port 5060
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if host==us: 12==13 && [192.168.10.2] == [192.168.10.1]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if port 7161 matches port 5060
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
no match for: [192.168.10.2:5060]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_aliases:
no match for: [0:192.168.10.2:5060]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:check_self:
host != me
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if host==us: 13==13 && [192.168.10.1] == [192.168.10.1]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if port 5060 matches port 5060
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
match found for: [192.168.10.1:5060]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:check_self:
host == me
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:after_loose:
Topmost route URI: 'sip:192.168.10.1;r2=on;lr=on;nat=yes' is me
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if host==us: 13==13 && [192.168.10.1] == [192.168.10.1]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
checking if port 7161 matches port 7161
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:grep_sock_info:
match found for: [192.168.10.1:7161]
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=200
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:get_hdr_field:
found end of header
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:find_next_route:
No next Route HF found
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:rr:after_loose: no
next URI found
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:rr:check_route_param: params are <;r2=on;lr=on;nat=yes>
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=40
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to_param:
tag=01021310150514813644546133
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to: end
of header reached, state=29
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_to:
display={"911317434"}, ruri={sip:911317434@192.168.10.1:5060}
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:siputils:has_totag:
totag found
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_newtran:
transaction on entrance=0xffffffff
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=ffffffffffffffff
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=78
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_lookup_request:
start searching: hash=850, isACK=0
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_lookup_request:
proceeding to pre-RFC3261 transaction matching
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_lookup_request:
no transaction found
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:tm:run_reqin_callbacks: trans=0xb615b5f8, callback type 1, id 0 entered
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:parse_headers:
flags=78
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:mk_proxy: doing
DNS lookup...
*Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:core:get_send_socket: force_send_socket of different proto (1)!
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
WARNING:core:get_send_socket: protocol/port mismatch*
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:set_timer:
relative timeout is 500000
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:tm:insert_timer_unsafe: [4]: 0xb615b744 (46600000)
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:set_timer:
relative timeout is 30
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:tm:insert_timer_unsafe: [0]: 0xb615b760 (76)
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_relay_to: new
transaction fwd'ed
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:tm:t_unref:
UNREF_UNSAFE: after is 0
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]:
DBG:core:destroy_avp_list: destroying list (nil)
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8808]: DBG:core:receive_msg:
cleaning up
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]: DBG:tm:utimer_routine:
timer routine:4,tl=0xb615b744 next=(nil), timeout=46600000
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]:
DBG:tm:retransmission_handler: retransmission_handler : request resending
(t=0xb615b5f8, BYE sip:9 ... )
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]: DBG:tm:set_timer:
relative timeout is 1000000
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]:
DBG:tm:insert_timer_unsafe: [5]: 0xb615b744 (47600000)
Feb 1 04:27:29 ser /usr/local/sbin/kamailio[8809]:
DBG:tm:retransmission_handler: retransmission_handler : done
Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]: DBG:tm:utimer_routine:
timer routine:5,tl=0xb615b744 next=(nil), timeout=47600000
Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]:
DBG:tm:retransmission_handler: retransmission_handler : request resending
(t=0xb615b5f8, BYE sip:9 ... )
Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]: DBG:tm:set_timer:
relative timeout is 2000000
Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]:
DBG:tm:insert_timer_unsafe: [6]: 0xb615b744 (49600000)
Feb 1 04:27:30 ser /usr/local/sbin/kamailio[8809]:
DBG:tm:retransmission_handler: retransmission_handler : done
I have set it up the Radius for Kamailio, it works fine, until the
Radius server goes down it did not go down for a while, when tis
happes the Kamailio server stops processing any calls.
I do not think is a normal behaviour, probably a bug, can anybody
please tell me if this is expected behave in kamailio. or was already
noticed before and was already fixed in a later release.
Is possible to point to more than 2 radius servers in parallel?
NOTE: i was running radius and DB in parallel with no issues, until
the RADIUS server goes down.
__________________________
O
Hello all,
I've run into an issue of Mar 2009:
http://lists.kamailio.org/pipermail/users/2009-March/022143.html
This seems to be unresolved in v1.5.4, the then presented work-around via
modparam("pua_dialoginfo", "override_lifetime", 600)
still works fine. The question is whether this should work differently
nowadays, or if notice should be put into the docs?
Best regards,
Martin
Hello all,
two questions regarding alias_db:
1) How do I make use of the append_branches function of alias_db? Trying to
insert two or more aliases is not possible in the current db layout (
UNIQUE KEY `alias_idx` (`alias_username`,`alias_domain`) ). The idea was to
enable simple db-based parallel branching ("group call") via alias_db by
inserting one or more users to one alias. This seems not possible.
2) Use of alias_db "breaks" presence_dialog, because dialog matching is
based on from / to header (instead from / final AoR after alias_db_lookup()
), thus presence_dialog events cannot be created and PUBLISHed to end
devices. I was wondering whether it would be sufficient to uac_replace_from
in branch_route[] before the final t_relay work around this, or if there is
another solution out there?
Many thanks and best regards,
Martin
Hello,
On 2/2/10 1:18 PM, alex pappas wrote:
> Hi Daniel,
>
> I'm capturing with tcpdump the packets when they live the server and I
> don't see the extra header added.
>
are you having the rpid value in subscriber table? Is it loaded via
load_credentials of auth_db or do you set the right avp in script?
Have you tried append_hf()? Seems you want to add r-uri to rpid, which
is easier via append_hf() then.
Cheers,
Daniel
> Cheers
> Alex
>
>
>
> On Tue, Feb 2, 2010 at 12:24 PM, Daniel-Constantin Mierla
> <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
>
> Hi Alex,
>
>
> On 2/2/10 11:04 AM, alex pappas wrote:
>
> Dear friends,
>
> I'm trying to give to a user the option to have privacy in a
> call. I'm trying to do that by adding an extra header with:
> append_rpid_hf("sip",
> ";party=calling;id-type=subscriber;privacy=off;screen=no");
>
> I'm using this header in the begining of the kamailio.cfg
>
> if(($rU=="99999") || ($rU=="77777"))
> {
> append_rpid_hf("sip",
> "$ru;party=calling;id-type=subscriber;privacy=off;screen=no");
> xlog("alx ------- We have rU match
> --------");
> }
>
> When I see the sip messages I don't see this extra header
> added into it.
>
> Does anyone had experience in this ?
>
> the header is visible when the message is forwarded. To see it
> immediately, but only in 3.0.0, you can use msg_apply_changes().
>
> Cheers,
> Daniel
>
>
> --
> Daniel-Constantin Mierla
> eLearning class for Kamailio 3.0.0
> Starting Feb 8, 2010
> * http://www.asipto.com/
>
>
--
Daniel-Constantin Mierla
eLearning class for Kamailio 3.0.0
Starting Feb 8, 2010
* http://www.asipto.com/