[cisco-voip] Calls not going to second line

Lelio Fulgenzi lelio at uoguelph.ca
Tue May 12 18:44:39 EDT 2009


If you are using the classic same DN in a different partition model for busy calls, then you'll need to use the forwarding CSS. 

Line 1: DN=1234 PT=Line1_PT CSS=General_CSS (contains Line1_PT) 

    • Busy Target = 1234 Busy FWD CSS = Line1BusyTarget_CSS (contains Line1BusyTarget_PT) 

Line 2: DN=1234 PT=Line1BusyTarget_PT CSS=General_CSS (contains Line1_PT) 

That being said, the main reason people did this (as far as I know) was to get around the 2 call limit on phones. You forward to the second line so you can transfer these calls out. With multiple calls per line, this requirement (in this case) is no longer there. Just up your calls on your line. 




--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "gin Murray" <kinusca at gmail.com> 
To: "Duy Nguyen" <ccieid1ot at gmail.com> 
Cc: "Lelio Fulgenzii" <lelio at uoguelph.ca>, cisco-voip at puck.nether.net 
Sent: Tuesday, May 12, 2009 6:24:30 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Calls not going to second line 


I tried calling the second line from the phone itself and it goes to the first line only. 

Both my lines are configured with the same number say 1234. 


On Tue, May 12, 2009 at 3:16 PM, Duy Nguyen < ccieid1ot at gmail.com > wrote: 


If the second line is in null partition css forwarding isn't needed. When I said css has nothing to do with forwarding, I'm assuming he's basing on cssand the order of partions. 




Lelio Fulgenzi < lelio at uoguelph.ca > wrote: 

>in actuality, the CSS of the line (or the appropriate forwarding CSS if set) must be able to dial the target, or it won't work. 
> 
>try dialing the target from the line itself, until that works, your busy fwd rule won't either (if not using fwd css). 
> 
> 
>--- 
>Lelio Fulgenzi, B.A. 
>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
>"Bad grammar makes me [sic]" - Tshirt 
> 
> 
>----- Original Message ----- 
>From: "ccieid1ot" < ccieid1ot at gmail.com > 
>To: "gin Murray" < kinusca at gmail.com > 
>Cc: cisco-voip at puck.nether.net 
>Sent: Tuesday, May 12, 2009 5:56:10 PM GMT -05:00 US/Canada Eastern 
>Subject: Re: [cisco-voip] Calls not going to second line 
> 
>You have to set the CFNA or Busy to the second line. CSS has nothing 
>to do with it. 
> 
>On Tue, May 12, 2009 at 4:40 PM, gin Murray < kinusca at gmail.com > wrote: 
>> Hi, 
>> 
>> When teh first line is busy, teh calls are not going to teh Second line in 
>> VOIP Phones. 
>> 
>> The CSS is set for the fist line for busy to go the second extension and the 
>> no of busy lines (max) is set to 1. But the Calls are getting forward to teh 
>> VM. 
>> _______________________________________________ 
>> cisco-voip mailing list 
>> cisco-voip at puck.nether.net 
>> https://puck.nether.net/mailman/listinfo/cisco-voip 
>> 
>> 
>_______________________________________________ 
>cisco-voip mailing list 
> cisco-voip at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-voip 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090512/33001d9d/attachment.html>


More information about the cisco-voip mailing list