Greetings All, I am attempting to fix a condition with camped calls where a camped calling party never transfers to a now idle user unless there is a DID assigned as well as extension. We have found that once the URL Dialing policy is added to the routing profile that the network server lookup succeeds. We have never enabled the URL Dialing policy on the Network Server routing profile except for testing in the lab. Can any of the BroadWorks users out there comment on the impact of enabling URL Dialing across the BroadWorks platform? James Hird Voice Engineer CDK Global, LLC 503.402.3795 (o) 503.309.5846 (c) James.hird at cdk.com Formerly ADP Dealer Services ---------------------------------------------------------------------- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
BroadSoft's "URL Dialing" is pretty important for several of the services. In particular, any time the Network Server receives an INVITE to route a call to an Application Server user sip:User at AppServer where User is a UserID, and AppServer identifies an application server. URL Dialing is necessary lately, but it'll also make your Network Server return Contacts in the 302 response that aren't helpful. For example, I've seen folks who used "starbucks.com" as a customer domain. Then when one of their users calls to sip:Bogus at starbucks.com, your App Server could do a DNS lookup, and you'll find INVITE's being attempted to 98.99.252.71, with SNMP traps when that call fails. Even worse if your firewall allows them through. Even worse if your firewall has a default SIP ALG that opens a global pinhole allowing anything on the Internet to reply when the trusted side sends out a SIP INVITE to the Internet <http://www.juniper.net/documentation/en_US/junos11.4/topics/task/configurati...>. In this case, I vote you fix the problem by blocking outbound (trusted-to-untrusted) SIP in the firewall. --- mailto:mark at ecg.co tel:+1-229-316-0013 http://ecg.co/lindsey
On Mar 2, 2015, at 13:47 , Hird, James <James.Hird at cdk.com> wrote:
Greetings All,
I am attempting to fix a condition with camped calls where a camped calling party never transfers to a now idle user unless there is a DID assigned as well as extension. We have found that once the URL Dialing policy is added to the routing profile that the network server lookup succeeds.
We have never enabled the URL Dialing policy on the Network Server routing profile except for testing in the lab. Can any of the BroadWorks users out there comment on the impact of enabling URL Dialing across the BroadWorks platform?
James Hird Voice Engineer CDK Global, LLC 503.402.3795 (o) 503.309.5846 (c) James.hird at cdk.com
Formerly ADP Dealer Services
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (2)
-
James.Hird＠cdk.com -
lindsey＠e-c-group.com