Hi guys, I have a kamailio load balancing requests across 2 Asterisk Servers, and all is working well. Only problem now is when utilizing feature codes to look to listen into calls using the chanspy application I am having issues. I am passing calls to *2222 into Asterisk, where an IVR answers the call, then sends an INVITE back to kamailio to check to see if the extension I want to listen into is in an active call (hash table), and the call will then be forwarded to the Asterisk in question and chanspy applied so it can be listened to. The problem I have is when I send an INVITE from Asterisk Server, and then kamailio sends an INVITE back to the same Asterisk Server I get the following failure in asterisk console; Not accepting call completion offers from call-forward recipient I appreciate its potentially more an Asterisk question but I wondered if anyone had experienced the same issue? I have setup a completely load balanced environment so dont want to use Primary/Secondary Server routing. Thanks Jon
On Tuesday 14 July 2015 11:04:59 Jonathan Hunter wrote:
The problem I have is when I send an INVITE from Asterisk Server, and then kamailio sends an INVITE back to the same Asterisk Server I get the following failure in asterisk console;
Is it just a warning or does the chanspy fail?
You could try the topoh module as workaround since the callid can be rewritten by it to appear as a new cal for asterisk.
You also could try to redirect the INVITE in kamailio (and allow promiscuos redirect for it), you might have to create a peer on asterisk for host=127.0.0.1 to make this redirect work correctly (and offcourse accept calls from/between the other asterisk machines).
Hi Daniel, It fails the call, well doesn't respond; 2015-07-14 10:49:38] NOTICE[15318]: app_dial.c:901 do_forward: Not accepting call completion offers from call-forward recipient Local/*33331022-MAGNORTH13@from-outside-00000001;1[2015-07-14 10:49:38] NOTICE[15318]: chan_local.c:973 local_call: No such extension/context *33331022-MAGNORTH13@from-outside while calling Local channel[2015-07-14 10:49:38] NOTICE[15318]: app_dial.c:1003 do_forward: Forwarding failed to dial 'Local/*33331022-MAGNORTH13@from-outside' The callid re-write is a good idea, as I tried it manually and it allowed connection, I will try that. I will also consider your other option. Many thanks for the prompt response. Jon
From: d.tryba@pocos.nl To: sr-users@lists.sip-router.org Date: Tue, 14 Jul 2015 13:19:48 +0200 Subject: Re: [SR-Users] Kamailio Load balancing Across Multiple Asterisk Servers -Chanspy
On Tuesday 14 July 2015 11:04:59 Jonathan Hunter wrote:
The problem I have is when I send an INVITE from Asterisk Server, and then kamailio sends an INVITE back to the same Asterisk Server I get the following failure in asterisk console;
Is it just a warning or does the chanspy fail?
You could try the topoh module as workaround since the callid can be rewritten by it to appear as a new cal for asterisk.
You also could try to redirect the INVITE in kamailio (and allow promiscuos redirect for it), you might have to create a peer on asterisk for host=127.0.0.1 to make this redirect work correctly (and offcourse accept calls from/between the other asterisk machines).
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
On Tuesday 14 July 2015 11:29:34 Jonathan Hunter wrote:
No such extension/context *33331022-MAGNORTH13@from-outside while calling Local channel[2015-07-14 10:49:38] NOTICE[15318]: app_dial.c:1003 do_forward: Forwarding failed to dial 'Local/*33331022-MAGNORTH13@from-outside'
This sounds like a dialplan error, but is out of the scope of this mailinglist :)
The callid re-write is a good idea, as I tried it manually and it allowed connection, I will try that. I will also consider your other option. Many thanks for the prompt response.
BTW I forgot to mention topoh might introduce problems with calls flowing more than once through a kamailio doing topology hiding (I'd advise not to use it)
Hi Daniel,topoh moduling and its working well for this scenario now, so thank you. However like you say enabling might introduce problems with call flow. Are there any other methods to modify/regenerate call-id header?
Other than that yes I will look at dialplan :) Thanks Jon
From: d.tryba@pocos.nl To: sr-users@lists.sip-router.org Date: Tue, 14 Jul 2015 13:53:25 +0200 Subject: Re: [SR-Users] Kamailio Load balancing Across Multiple Asterisk Servers -Chanspy
On Tuesday 14 July 2015 11:29:34 Jonathan Hunter wrote:
No such extension/context *33331022-MAGNORTH13@from-outside while calling Local channel[2015-07-14 10:49:38] NOTICE[15318]: app_dial.c:1003 do_forward: Forwarding failed to dial 'Local/*33331022-MAGNORTH13@from-outside'
This sounds like a dialplan error, but is out of the scope of this mailinglist :)
The callid re-write is a good idea, as I tried it manually and it allowed connection, I will try that. I will also consider your other option. Many thanks for the prompt response.
BTW I forgot to mention topoh might introduce problems with calls flowing more than once through a kamailio doing topology hiding (I'd advise not to use it)
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
-
Daniel Tryba -
Jonathan Hunter