i have a simple ivr app that tries first to connect to one callee using python ivr call
self.connectCallee(self.to_uri, self.to_uri) if response to that call is > 300, the app gives self.to_uri a new value and makes the above ivr call again. this has used to work fine in earlier sems releases. now when i tested this app, i found two problems with the second INVITE that self.connectCallee call generated: U 2013/09/04 09:46:25.458589 192.98.102.10:5090 -> 192.98.102.10:5060 INVITE sip:[email protected] SIP/2.0. Via: SIP/2.0/UDP 192.98.102.10:5090;branch=z9hG4bKIyHuWaha;rport. From: "Juha Heinanen" <sip:[email protected]>;tag=38C48178-5226D73A000A1389-90256700. To: sip:[email protected];tag=c02670ad1171fe45d9ff9a27d6c2cb82-678b. the problems are 1) sems sends the second INVITE request to wrong IP:port (= 192.98.102.10:5060) whereas it should go to next_hop=192.98.102.10:5070 next_hop_1st_req=yes like the first INVITE did. 2) the second INVITE contains ;tag in To URI although it is initial request. i would really appreciate if someone had time to figure out, what has gone wrong and fix the above issues. -- juha _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
