Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
According to TAC CM will try to allocate a non-trusted MTP if it fails to allocate a TRP/MTP. SR: 630004281 in case any Cisco people would like to take a look. On Tue, Apr 22, 2014 at 7:29 PM, Anthony Holloway avholloway+cisco-v...@gmail.com wrote: Wouldn't setting it to false, cause it to not be required, and thus break your VPN solution when it isn't invoked? On Tue, Apr 22, 2014 at 4:16 PM, Erick Wellnitz ewellnitzv...@gmail.comwrote: After collecting traces and sending them off to TAC, we found that the Fail Call If Trusted Relay Point Allocation Fails https://10.2.146.20/ccmadmin/serviceParamEdit.do?server=63a3b20b-c06e-4957-a9be-9f98feb64114service=0showall=true#[image: Required Field] service parameter was set to true. It seems to be working properly after changing this to false. On Fri, Apr 18, 2014 at 11:12 AM, Justin Steinberg jsteinb...@gmail.comwrote: Any change device mobility could be in play for this user changing the device pool/region ? On Fri, Apr 18, 2014 at 11:12 AM, Brian Meade bmead...@vt.edu wrote: There's some scenarios where you do not get a media resource list exhausted alert. One scenario is where the CCM service has an incorrect count of available resources and you just see the MTP fail to send an OpenReceiveChannelAck or send one saying it failed to open a port. In that case, CUCM didn't think the media resources were actually exhausted so no alert. We'll need to see CCM traces for one of these calls to see what is actually happening. Have you tried resetting the MTP? Brian On Fri, Apr 18, 2014 at 10:55 AM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Ryan, When you mention stuck sessions do you mean x number of stuck sessions preventing further allocation of resources or this particular device has a stuck session? If it were the first scenario, wouldn't I get a media list exhausted alert from RTMT? On Fri, Apr 18, 2014 at 7:36 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
Wouldn't setting it to false, cause it to not be required, and thus break your VPN solution when it isn't invoked? On Tue, Apr 22, 2014 at 4:16 PM, Erick Wellnitz ewellnitzv...@gmail.comwrote: After collecting traces and sending them off to TAC, we found that the Fail Call If Trusted Relay Point Allocation Fails https://10.2.146.20/ccmadmin/serviceParamEdit.do?server=63a3b20b-c06e-4957-a9be-9f98feb64114service=0showall=true#[image: Required Field] service parameter was set to true. It seems to be working properly after changing this to false. On Fri, Apr 18, 2014 at 11:12 AM, Justin Steinberg jsteinb...@gmail.comwrote: Any change device mobility could be in play for this user changing the device pool/region ? On Fri, Apr 18, 2014 at 11:12 AM, Brian Meade bmead...@vt.edu wrote: There's some scenarios where you do not get a media resource list exhausted alert. One scenario is where the CCM service has an incorrect count of available resources and you just see the MTP fail to send an OpenReceiveChannelAck or send one saying it failed to open a port. In that case, CUCM didn't think the media resources were actually exhausted so no alert. We'll need to see CCM traces for one of these calls to see what is actually happening. Have you tried resetting the MTP? Brian On Fri, Apr 18, 2014 at 10:55 AM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Ryan, When you mention stuck sessions do you mean x number of stuck sessions preventing further allocation of resources or this particular device has a stuck session? If it were the first scenario, wouldn't I get a media list exhausted alert from RTMT? On Fri, Apr 18, 2014 at 7:36 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
MTP looks fine. No stuck sessions. Test calls connect and release as expcted. I'll have to wait until we get another report to pull new traces. On Fri, Apr 18, 2014 at 2:20 PM, Erick Wellnitz ewellnitzv...@gmail.comwrote: The entire scenario is the phone worked for several weeks via VPN. It stopped working so the user brought it back for us to troubleshoot. These are non-technical users which I'm not excited about but I digress. Plugged it into the internet GW at the office and it worked perfect. Sent it back to the user and it worked for 3 days. The users don't have access to change anything in the system but we have way too many people with admin access that I suppose someone could be changing this phone without realizing it. I'm out of the office until Monday. I'll check the MTP and review the traces then. On Fri, Apr 18, 2014 at 11:12 AM, Justin Steinberg jsteinb...@gmail.comwrote: Any change device mobility could be in play for this user changing the device pool/region ? On Fri, Apr 18, 2014 at 11:12 AM, Brian Meade bmead...@vt.edu wrote: There's some scenarios where you do not get a media resource list exhausted alert. One scenario is where the CCM service has an incorrect count of available resources and you just see the MTP fail to send an OpenReceiveChannelAck or send one saying it failed to open a port. In that case, CUCM didn't think the media resources were actually exhausted so no alert. We'll need to see CCM traces for one of these calls to see what is actually happening. Have you tried resetting the MTP? Brian On Fri, Apr 18, 2014 at 10:55 AM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Ryan, When you mention stuck sessions do you mean x number of stuck sessions preventing further allocation of resources or this particular device has a stuck session? If it were the first scenario, wouldn't I get a media list exhausted alert from RTMT? On Fri, Apr 18, 2014 at 7:36 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.commailto:ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.commailto:ewellnitzv...@gmail.com wrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.commailto:rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.commailto:ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.netmailto:cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
Ryan, When you mention stuck sessions do you mean x number of stuck sessions preventing further allocation of resources or this particular device has a stuck session? If it were the first scenario, wouldn't I get a media list exhausted alert from RTMT? On Fri, Apr 18, 2014 at 7:36 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.comwrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
There's some scenarios where you do not get a media resource list exhausted alert. One scenario is where the CCM service has an incorrect count of available resources and you just see the MTP fail to send an OpenReceiveChannelAck or send one saying it failed to open a port. In that case, CUCM didn't think the media resources were actually exhausted so no alert. We'll need to see CCM traces for one of these calls to see what is actually happening. Have you tried resetting the MTP? Brian On Fri, Apr 18, 2014 at 10:55 AM, Erick Wellnitz ewellnitzv...@gmail.comwrote: Ryan, When you mention stuck sessions do you mean x number of stuck sessions preventing further allocation of resources or this particular device has a stuck session? If it were the first scenario, wouldn't I get a media list exhausted alert from RTMT? On Fri, Apr 18, 2014 at 7:36 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.comwrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
Any change device mobility could be in play for this user changing the device pool/region ? On Fri, Apr 18, 2014 at 11:12 AM, Brian Meade bmead...@vt.edu wrote: There's some scenarios where you do not get a media resource list exhausted alert. One scenario is where the CCM service has an incorrect count of available resources and you just see the MTP fail to send an OpenReceiveChannelAck or send one saying it failed to open a port. In that case, CUCM didn't think the media resources were actually exhausted so no alert. We'll need to see CCM traces for one of these calls to see what is actually happening. Have you tried resetting the MTP? Brian On Fri, Apr 18, 2014 at 10:55 AM, Erick Wellnitz ewellnitzv...@gmail.comwrote: Ryan, When you mention stuck sessions do you mean x number of stuck sessions preventing further allocation of resources or this particular device has a stuck session? If it were the first scenario, wouldn't I get a media list exhausted alert from RTMT? On Fri, Apr 18, 2014 at 7:36 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
The entire scenario is the phone worked for several weeks via VPN. It stopped working so the user brought it back for us to troubleshoot. These are non-technical users which I'm not excited about but I digress. Plugged it into the internet GW at the office and it worked perfect. Sent it back to the user and it worked for 3 days. The users don't have access to change anything in the system but we have way too many people with admin access that I suppose someone could be changing this phone without realizing it. I'm out of the office until Monday. I'll check the MTP and review the traces then. On Fri, Apr 18, 2014 at 11:12 AM, Justin Steinberg jsteinb...@gmail.comwrote: Any change device mobility could be in play for this user changing the device pool/region ? On Fri, Apr 18, 2014 at 11:12 AM, Brian Meade bmead...@vt.edu wrote: There's some scenarios where you do not get a media resource list exhausted alert. One scenario is where the CCM service has an incorrect count of available resources and you just see the MTP fail to send an OpenReceiveChannelAck or send one saying it failed to open a port. In that case, CUCM didn't think the media resources were actually exhausted so no alert. We'll need to see CCM traces for one of these calls to see what is actually happening. Have you tried resetting the MTP? Brian On Fri, Apr 18, 2014 at 10:55 AM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Ryan, When you mention stuck sessions do you mean x number of stuck sessions preventing further allocation of resources or this particular device has a stuck session? If it were the first scenario, wouldn't I get a media list exhausted alert from RTMT? On Fri, Apr 18, 2014 at 7:36 AM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: Stuck sessions on the MTP perhaps or leaked calls in UCM? You're going to have to dig into traces to confirm. -Ryan On Apr 17, 2014, at 10:52 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
Re: [cisco-voip] MTP allocation failure - CDDR cause code 47
Well, identical except for MAC and description. It worked for three days now it fails. The last successful call allocated the MTP without issue. I personally tested it a dozen or so times before giving it back to the user. On Thu, Apr 17, 2014 at 9:45 PM, Erick Wellnitz ewellnitzv...@gmail.comwrote: Super copy identical. On Thu, Apr 17, 2014 at 4:33 PM, Ryan Ratliff (rratliff) rratl...@cisco.com wrote: 47 = codec mismatch Is it _really_ identical? -Ryan On Apr 17, 2014, at 4:02 PM, Erick Wellnitz ewellnitzv...@gmail.com wrote: I have a VPN phones configured to use a trused relay point in order to provide connectivity to other VPN phones. One of the phones gets fast busy and traces show MTP allocation failure. This was the only phone trying ot utilize this MTP and is identical to other VPN phones that work as expected. Any ideas? Thanks! ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip ___ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
