[Kamailio-Users] Kamailio 1.4.3 Carrierroute BYE does not

unknown at 1.org unknown at 1.org
Tue Feb 17 05:06:05 CET 2009


Hello:

I have this scenario:

I already rad about the bye2bye, the dialog module, i was not able to
see any light there.


Here is the scenario


A--GW--------Kamailio(carrierroute)---------GW1---B
                          |--------------GW2
                          |--------------GW3 (etc)

the capture

                      |<-------------BYE----
-<----NOTHING HERE<<<-|


the By does go back if the B user hangs
it is not even attempted in the kamailio, per the traces.
the BY generates records in the CRD from B side
if i hang manually the bye generates CDR records from the A side.

Again the Bye is understood by the kamailio and generates the CDR
records, that is Not the problem, the Problem is i have the user A in
silence, i am talking about the Signaling Only, not Media, no NAT.

I even tried the mediaproxy (just trying)

the config is like the:
http://voipembedded.com/resources/openser_cr.cfg

i added 

        if (has_totag()) {
                # sequential request withing a dialog should
                # take the path determined by record-routing
                if (loose_route()) {
                       # mark routing logic in request
                        append_hf("P-hint: rr-enforced\r\n");
                      if (is_method("BYE")) {
                                setflag(1); # do accounting ...
                                setflag(3); # ... even if the
transaction fails
                          exit;
                       }
                        route(10);
                } else {
                        /* uncomment the following lines if you want to
enable presence */
                        ##if (is_method("SUBSCRIBE") && $rd ==
"your.server.ip.address") {
                        ##      # in-dialog subscribe requests
                        ##      route(200);
                        ##      exit;
                        ##}
                        if ( is_method("ACK") ) {
                                if ( t_check_trans() ) {
                                        # non loose-route, but stateful
ACK; must be an ACK after a 487 or e.g. 404 from upstream server
                                        t_relay();
                                        exit;
                                } else {
                                        # ACK without matching
transaction ... ignore and discard.\n");
                                        xlog("L_WARN", "[$mi] discarding
ACK\n");
                                        exit;
                                }


this is the main difference for now, i changed to use as a basis example
the Example 1.45. Configuration example - Routing to user tree.
same results.

i tried adding the record_route in the invite also, same result.


At this point i have no clue what i am missing.

Please let me know if this should work or not, and if yes, based in that
basic example, what i should add.





More information about the Users mailing list