<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div>It is ok to have those blank, but configuring them will help unity catch calls made by unity that somehow come back to unity and possibly rejecting those type of call flows. <br><br>This paste is from a cisco discussion forum post where a cisco engineer explains it, there is a bug id below to with some more details:<br><br><span><a target="_blank"
href="http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=Unified%20Communications&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd66a99/0">http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=Unified%20Communications&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd66a99/0</a></span><br><br>"By default Unity will try to match the caller ID on incoming calls to
the extension numbers you've entered for each port in UTIM.
Unfortunately, caller ID alone is not reliable. For example, if Unity
transfers a call out across a trunk or TIE line and that call gets
forwarded back to Unity, we might expect to see the transferring port
as the incoming caller ID. In this case, we don't want to reject the
call. To handle this, Unity will only reject calls that have caller ID
matching a dedicated outdial port (i.e. a port that is not configured
to answer and hence transfer calls). So to take full advantage of this
feature, you'll first want to configure dedicated outbound ports for
Notification, TRaP and MWI calls. Then you'll want to ensure these
ports have extension numbers entered for them in the UTIM. Details of
this implementation can be found in CSCdu64641. <br>
<br>Of course there are still cases where the above method is
insufficient. For example, if a notification call from Unity goes out
to a cell phone that is forwarded back to Unity the original caller ID
(Unity's extension) may not show up on the forwarded call. To help
accommodate cases like this, a new tone-detect based feature was added
in 4.0(4). Check out the "Reject Forwarded Notification DTMF Tone"
setting in the Advanced Settings Tool. Unfortunately, this will only
help with Notification calls. TRaP calls as you mentioned will not be
impacted.
"<br><br>----- Original Message ----<br>From: Zevier Thoran <zthoran@yahoo.com><br>To: Cisco Voip <cisco-voip@puck.nether.net><br>Sent: Thursday, April 13, 2006 9:26:45 PM<br>Subject: [cisco-voip] Unity - CallManager integration Fluke<br><br>Hi,<br>While setting Unity - CallManager integration in the Utim tool, my integration works fine even when the 'Extension' fields for the 'Port' numbers are blank? Do I need to fill them up or is my integration working as a fluke?<br>Thanks<br>-Zevier<br><p> </p><hr size="1">Blab-away for as little as 1ยข/min. Make <a target="_blank" id="bodyLinks" href="http://us.rd.yahoo.com/mail_us/taglines/postman2/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com"> PC-to-Phone Calls</a> using Yahoo! Messenger with Voice.<div>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br><a target="_blank"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></div></div></div></div></body></html>