ZOMBIE SIP Extensions
-
Dear All,
any advice for this problem , i have Elastix 2.4 and when i call from extension to extension i get the below error in the asterisk cli :
== Spawn extension (macro-hangupcall, s, 51) exited non-zero on 'Parked/SIP/800-00000018<ZOMBIE>' in macro 'hangupcall' == Spawn extension (from-internal, h, 1) exited non-zero on 'Parked/SIP/800-00000018<ZOMBIE> -
Here is the code comment on that Zombie flag:
This is a seriously wacked out operation. We're essentially putting the guts of
the clone channel into the original channel. Start by killing off the original
channel's backend. I'm not sure we're going to keep this function, because
while the features are nice, the cost is very high in terms of pure nastiness. -
Are your calls working or failing?
-
@scottalanmiller said in ZOMBIE SIP Extensions:
Are your calls working or failing?
The Calls are Failing.
-
All extensions or just some?
-
@scottalanmiller said in ZOMBIE SIP Extensions:
All extensions or just some?
Only one extension works and the others no.
-
Let me explain what i have done.
i have two sites with the below details :
Site A :
This is the Asterisk Server and OpenVPN Server at the same time.
Lan IP Address is : 192.168.1.250
VPN IP Address is : 192.168.70.1Site B :
This is a VM to act as an OpenVPN Client and Forward the packets of the Phones to
Asterisk in Site ALan IP Address is : 192.168.1.100
VPN IP Address is : 192.168.70.10Actions:
Site B :
route add -net 192.168.70.0/24 gw 192.168.1.100 echo "net.ipv4.ip_forward = 1" >>/etc/sysctl.confSite A :
iptables -t nat -A POSTROUTING -s 192.168.70.0/24 -o etho -j MASQUERADE echo "net.ipv4.ip_forward = 1" >>/etc/sysctl.conf -
Could your issue be that you are using the 192.168.1.0/24 for the LAN networks at both sites?
Generally, site A would be 192.168.1.0/24, and site B would be something like 192.168.10.0/24.
-
@dafyre said in ZOMBIE SIP Extensions:
Could your issue be that you are using the 192.168.1.0/24 for the LAN networks at both sites?
Generally, site A would be 192.168.1.0/24, and site B would be something like 192.168.10.0/24.
That is most certainly the problem, assuming that he is using a /24 in both places.
-
Well, he could be trying to do a poor mans MPLS / transparent VPN thing..
You can do this if you really know your routing well.
