<div dir="ltr">Hi,<div><br></div><div><span style="font-size:12.0pt;font-family:"Times New Roman","serif";
mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:
EN-US;mso-bidi-language:AR-SA">Check this step:</span></div><div><span style="font-size:12.0pt;font-family:"Times New Roman","serif";
mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:
EN-US;mso-bidi-language:AR-SA"> <span style="mso-spacerun:yes"> </span><span style="mso-spacerun:yes"> </span></span></div><div><span style="font-size:12.0pt;font-family:"Times New Roman","serif";
mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:
EN-US;mso-bidi-language:AR-SA">Subscribing IP Phones to Cisco
Extension Mobility</span></div><div><span class="Apple-style-span" style="font-family: 'Times New Roman'; font-size: 16px;"><br></span><br></div><div><p class="psnstepnext">To subscribe extension mobility to the IP phone, go to the
Related Links drop-down list box in the upper, right corner of the window and
choose Subscribe/Unsubscribe Services; then, click Go. </p>
<p class="psbstepbody"><a name="wp1271745"></a>A separate Subscribed Cisco IP Phone
Services window displays. </p>
<p class="psnstepnext"><a name="wp1271769"></a><span style="mso-no-proof:yes"><img width="5" height="2" src="file:///C:/DOCUME~1/ISA~1.MAT/LOCALS~1/Temp/msohtmlclip1/01/clip_image002.gif" alt="http://www.cisco.com/en/US/i/templates/blank.gif"></span>From
the Select a Service drop-down list box, choose the service to which you want
this IP phone to subscribe. </p>
<p class="psnstepnext"><a name="wp1271797"></a><span style="mso-no-proof:yes"><img width="5" height="2" src="file:///C:/DOCUME~1/ISA~1.MAT/LOCALS~1/Temp/msohtmlclip1/01/clip_image002.gif" alt="http://www.cisco.com/en/US/i/templates/blank.gif"></span>Click
Next. </p>
<p class="psnstepnext"><a name="wp1271809"></a><span style="mso-no-proof:yes"><img width="5" height="2" src="file:///C:/DOCUME~1/ISA~1.MAT/LOCALS~1/Temp/msohtmlclip1/01/clip_image002.gif" alt="http://www.cisco.com/en/US/i/templates/blank.gif"></span>Click
Subscribe. </p>
<p class="psnstepnext"><a name="wp1271821"></a><span style="mso-no-proof:yes"><img width="5" height="2" src="file:///C:/DOCUME~1/ISA~1.MAT/LOCALS~1/Temp/msohtmlclip1/01/clip_image002.gif" alt="http://www.cisco.com/en/US/i/templates/blank.gif"></span>The
new service(s) displays under Subscribed Services. </p>
<p class="psnstepnext"><a name="wp1271839"></a><span style="mso-no-proof:yes"><img width="5" height="2" src="file:///C:/DOCUME~1/ISA~1.MAT/LOCALS~1/Temp/msohtmlclip1/01/clip_image002.gif" alt="http://www.cisco.com/en/US/i/templates/blank.gif"></span>Click
Save.</p><p class="psnstepnext">Regards</p><p class="psnstepnext">Isa Mattar</p><div class="gmail_quote">On Wed, Dec 3, 2008 at 6:10 AM, <span dir="ltr"><<a href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Send cisco-voip mailing list submissions to<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cisco-voip-owner@puck.nether.net">cisco-voip-owner@puck.nether.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cisco-voip digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Extension Mobility (Hasan Khan)<br>
2. Re: Forwarding To extension in Unity (Matthew J. Hughes)<br>
3. Re: Securing Voice networks (Mark Holloway)<br>
4. Test --- please ignore (Hasan Khan)<br>
5. Re: Extension Mobility (Ryan Ratliff)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 2 Dec 2008 14:37:44 -0800 (PST)<br>
From: Hasan Khan <<a href="mailto:hasan_asghar@yahoo.com">hasan_asghar@yahoo.com</a>><br>
Subject: [cisco-voip] Extension Mobility<br>
To: "<a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Message-ID: <<a href="mailto:264164.60620.qm@web33404.mail.mud.yahoo.com">264164.60620.qm@web33404.mail.mud.yahoo.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello,<br>
<br>
For doing extension mobility, I have done the followiing.<br>
<br>
1) Activate the extension mobility from Cisco Unified Serviceability (Tools -- Service Activation). I have done this step for publisher and as well as for all subscribers.<br>
2) On publisher, went to Device -- Device Settings -- Phone Services and configure service with URL.<br>
<br>
Shouldn't I see the extension mobility service on my phone? Right now, I don't see the service on my phones.<br>
<br>
Any idea, what should I do to see the service on the phones?<br>
<br>
Thanks,<br>
Hasan<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/c1080c84/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/c1080c84/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 2 Dec 2008 15:43:25 -0800<br>
From: "Matthew J. Hughes" <<a href="mailto:mattjhughes@gmail.com">mattjhughes@gmail.com</a>><br>
Subject: Re: [cisco-voip] Forwarding To extension in Unity<br>
To: "James Buchanan" <<a href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>><br>
Cc: "<a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Message-ID:<br>
<<a href="mailto:ea211ea30812021543p72f8c704rf2e5c69c1a7931e3@mail.gmail.com">ea211ea30812021543p72f8c704rf2e5c69c1a7931e3@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Thanks for the help, I am having trouble in the transfer rules knowing what<br>
digits to send it to to forward to a external DID, i tried the 9 prefix but<br>
that doesnt seem to work, the system is integrated with CCM6, but I am<br>
unsure if it has a method of dialing out on its own. Whenever I attept to<br>
use the transfer rule it just says the box is busy and to leave a message.<br>
<br>
On Tue, Dec 2, 2008 at 2:33 PM, James Buchanan <<a href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>> wrote:<br>
<br>
> Hello,<br>
><br>
><br>
><br>
> Setup a System Contact in Unity Connection. In Unity, use a call handler<br>
> with that extension and with a transfer rule to the number.<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
><br>
><br>
> James<br>
><br>
><br>
><br>
> *From:* <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:<br>
> <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] *On Behalf Of *Matthew J. Hughes<br>
> *Sent:* Tuesday, December 02, 2008 3:33 PM<br>
> *To:* <a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a><br>
> *Subject:* [cisco-voip] Forwarding To extension in Unity<br>
><br>
><br>
><br>
> Is it possible to forward to a phone number that is not associated with a<br>
> voicemail box in Unity or Unity Connection? I have not been able to find a<br>
> way to do this in Unity Connection 2, maybe Unity Connection 7? This would<br>
> seem like a standard Phone Tree feature. Thanks for the help in advance.<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/9e490db6/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/9e490db6/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 2 Dec 2008 16:44:21 -0700<br>
From: "Mark Holloway" <<a href="mailto:mh@markholloway.com">mh@markholloway.com</a>><br>
Subject: Re: [cisco-voip] Securing Voice networks<br>
To: "'Jason Aarons \(US\)'" <<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>>, "'Lelio<br>
Fulgenzi'" <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>>, "'Scott Voll'" <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>><br>
Cc: 'cisco-voip' <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Message-ID: <002001c954d7$e6e83810$b4b8a830$@com><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
You can also use VRF Lite which allows you to use VRF's without using MPLS.<br>
<br>
<br>
<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Jason Aarons (US)<br>
Sent: Tuesday, December 02, 2008 4:36 PM<br>
To: Lelio Fulgenzi; Scott Voll<br>
Cc: cisco-voip<br>
Subject: Re: [cisco-voip] Securing Voice networks<br>
<br>
<br>
<br>
VRF is the backbone of how MPLS works. Your network routes are in a private<br>
VRF that only you can see. If they can hack or mis-configure the VRF then<br>
your routes could be advertised to a hack is the security worst case<br>
scenario with MPLS. I believe you can filter a VRF into another VRF but<br>
haven't seen that myself. I went thru backbone service provider MPLS<br>
training, did all the labs and haven't used VRF much since then.<br>
<br>
<br>
<br>
_____<br>
<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Lelio Fulgenzi<br>
Sent: Tuesday, December 02, 2008 6:07 PM<br>
To: Scott Voll<br>
Cc: cisco-voip<br>
Subject: Re: [cisco-voip] Securing Voice networks<br>
<br>
<br>
<br>
The term is VRF. <a href="http://en.wikipedia.org/wiki/VRF" target="_blank">http://en.wikipedia.org/wiki/VRF</a><br>
<br>
I'm still not clear as to the difference, but from what I understand, they<br>
are logically two separate networks and go beyond the level of seperation<br>
that VLANs provide. For example, you can have two VRF domains and route them<br>
across your network, both with the same IP address space but still logically<br>
separated. What I don't know, is whether you can somehow route between two<br>
VRF domains (if that's even what you call them).<br>
<br>
For now, we are using ACLs, and for the most part they work, but it's not<br>
ideal. Putting things behind a firewall makes sense, but with multiple data<br>
centres, you have to ensure that the voice servers can communicate with each<br>
other unhindered/unblocked. There are also some issues with respect to<br>
asymetrical routing which I think is an issue for us.<br>
<br>
Until Cisco comes up with a recommended design for putting their voice<br>
servers behind firewalls in multiple data centres, I think people will be<br>
clamoring.<br>
<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
"Bad grammar makes me [sic]" - Tshirt<br>
<br>
<br>
----- Original Message -----<br>
From: "Scott Voll" <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>><br>
To: "<<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Sent: Tuesday, December 2, 2008 5:56:59 PM GMT -05:00 US/Canada Eastern<br>
Subject: [cisco-voip] Securing Voice networks<br>
<br>
I have multiple Voice networks that I would like to put behind my FWSM. At<br>
CIPTUG (pass the mic) i asked the question of how others were doing it and I<br>
thought they were using VFR. is that the right term?<br>
<br>
<br>
<br>
Can someone give me a run down of how they are doing it?<br>
<br>
<br>
<br>
Thanks<br>
<br>
<br>
<br>
Scott<br>
<br>
<br>
_______________________________________________ cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
_____<br>
<br>
Disclaimer: This e-mail communication and any attachments may contain<br>
confidential and privileged information and is for use by the designated<br>
addressee(s) named above only. If you are not the intended addressee, you<br>
are hereby notified that you have received this communication in error and<br>
that any use or reproduction of this email or its contents is strictly<br>
prohibited and may be unlawful. If you have received this communication in<br>
error, please notify us immediately by replying to this message and deleting<br>
it from your computer. Thank you.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/30d8475b/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/30d8475b/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 2 Dec 2008 15:02:39 -0800 (PST)<br>
From: Hasan Khan <<a href="mailto:hasan_asghar@yahoo.com">hasan_asghar@yahoo.com</a>><br>
Subject: [cisco-voip] Test --- please ignore<br>
To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Message-ID: <<a href="mailto:211213.50920.qm@web33403.mail.mud.yahoo.com">211213.50920.qm@web33403.mail.mud.yahoo.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/32b03309/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/32b03309/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 2 Dec 2008 21:07:55 -0500<br>
From: Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>><br>
Subject: Re: [cisco-voip] Extension Mobility<br>
To: Hasan Khan <<a href="mailto:hakhan@tricolour.queensu.ca">hakhan@tricolour.queensu.ca</a>><br>
Cc: "<a href="mailto:cisco-voip@puck-nether.net">cisco-voip@puck-nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
Message-ID: <<a href="mailto:6DA0EF5E-AFC6-455E-BB5A-017E10E43B56@cisco.com">6DA0EF5E-AFC6-455E-BB5A-017E10E43B56@cisco.com</a>><br>
Content-Type: text/plain; charset="us-ascii"; Format="flowed";<br>
DelSp="yes"<br>
<br>
You need to subscribe the phones to the EM service before it will<br>
show up on the phone.<br>
<br>
-Ryan<br>
<br>
On Dec 2, 2008, at 5:37 PM, Hasan Khan wrote:<br>
<br>
Hello,<br>
<br>
For doing extension mobility, I have done the followiing.<br>
<br>
1) Activate the extension mobility from Cisco Unified Serviceability<br>
(Tools -- Service Activation). I have done this step for publisher<br>
and as well as for all subscribers.<br>
2) On publisher, went to Device -- Device Settings -- Phone Services<br>
and configure service with URL.<br>
<br>
Shouldn't I see the extension mobility service on my phone? Right<br>
now, I don't see the service on my phones.<br>
<br>
Any idea, what should I do to see the service on the phones?<br>
<br>
Thanks,<br>
Hasan<br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/c87aaf47/attachment.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20081202/c87aaf47/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
<br>
End of cisco-voip Digest, Vol 62, Issue 31<br>
******************************************<br>
</blockquote></div><br></div></div>