I have been trying to accomplish a couple tasks with Kamailio over the past month with no luck. What I need is a bit of one-on-one training with someone who knows the lay of the land. If you do this kind of consulting and can use Skype with possibly a shared-screen terminal, please drop me an email with your rate.
I need similar assistance. Drop me an email, too! -- Mark Sidell Partner Forte, Inc. 919-942-7068 fax 919-969-2844 www.forteinc.com
See http://www.kamailio.org/w/business-directory/ and http://www.kamailio.org/w/business/ for consultants. regards Klaus Am 28.02.2011 22:57, schrieb Pete Ashdown:
I have been trying to accomplish a couple tasks with Kamailio over the past month with no luck. What I need is a bit of one-on-one training with someone who knows the lay of the land. If you do this kind of consulting and can use Skype with possibly a shared-screen terminal, please drop me an email with your rate.
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Greetings, I'm having trouble getting parallel forking to work with aliasdb. I'm running kamailio 3.2 with the standard kamailio.cfg script. I have found that if an alias points to a set of addresses that all reference local devices that are registered with the server, kamailio sends an invitation to the first device in the set (the one that the aliasdb lookup function sets to the ruri, but does *not* invite any of the other devices in the set, which aliasdb adds as branches. However, if one of the other aliases points to a non-local address, such as a PSTN address, kamailio does correctly invite the non-local address in parallel with the first alias address, which is a local device. It seems as if kamailio is ignoring invitations that it is in effect sending to itself via the additional parallel branches. I would expect that to call a branch in parallel, kamailio would need to do a lookup on the branch address and rewrite it to send the invitation to the registered device. But none of that seems to be happening. There must be some additional configuration change required to make this work. Any suggestions? -- Mark Sidell Partner Forte, Inc. 919-942-7068 fax 919-969-2844 www.forteinc.com
Greetings, Here's another problem I'm having with kamailio 3.2 and the standard kamailio.cfg script. If the calling device is NATed, everything works fine if the original call gets connected. That is, the INVITE sent to the called device has the correct NAT fixups applied. But if the called device fails to answer and the script runs route[TOVOICEMAIL], the call connects, but the INVITE sent to the voicemail server doesn't have the NAT fixup applied. The result is that the audio is connected in only one direction. It would appear that some rtpproxy function needs to get called to apply the fixups prior to sending the INVITE to the voicemail server. I've tried adding calls to route(NATMANAGE) at various places, but to no avail. Any ideas? -- Mark Sidell Partner Forte, Inc. 919-942-7068 fax 919-969-2844 www.forteinc.com
Hi, I can see you've tried calling route[NATMANAGE] just before the route[TOVOICEMAIL] ! and that didn't work. Can you paste your configuration as well as a SIP trace for a voicemail call ! some logs of the same calls will help too. Regards, Sammy On Wed, May 9, 2012 at 9:10 PM, <x-kamailio@sidell.org> wrote:
Greetings,
Here's another problem I'm having with kamailio 3.2 and the standard kamailio.cfg script.
If the calling device is NATed, everything works fine if the original call gets connected. That is, the INVITE sent to the called device has the correct NAT fixups applied.
But if the called device fails to answer and the script runs route[TOVOICEMAIL], the call connects, but the INVITE sent to the voicemail server doesn't have the NAT fixup applied. The result is that the audio is connected in only one direction.
It would appear that some rtpproxy function needs to get called to apply the fixups prior to sending the INVITE to the voicemail server. I've tried adding calls to route(NATMANAGE) at various places, but to no avail.
Any ideas?
-- Mark Sidell Partner Forte, Inc. 919-942-7068 fax 919-969-2844 www.forteinc.com
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
participants (4)
-
Klaus Darilion -
Pete Ashdown -
SamyGo -
x-kamailio＠sidell.org