leviticus Posted June 13, 2012 Report Share Posted June 13, 2012 We're using a multitenant installation with a single global trunk configured for NexVortex. (so far... secondary SIP provider probably on the horizon). Discovered that 800 calling was not functioning with our setup and turned to the headers as a possible fix. This was my end result configuration, which successfully dials standard and 800 numbers, as well as pulls the outbound caller ID from the extensions (desirable for our setup). Figured I'd post here for commentary and if anyone had suggestions/thoughts on it. Request-URI: Let the System Decide From: Extension ANI To: Let the system decide p-asserted-identity: Don't use p-preferred-identity: Don't use Remote-Party ID: Based on incoming call p-charging-vector: Don't use Privacy Indication: Don't use Similarly related: Does the ANI 'rollover/up' if not defined? The behavior I've seen seems to indicate this. Example: If I've set the headers to deliver the extension ANI, but there is no extension ANI defined, but there IS a domain ANI, it will present the domain ANI? - This is very helpful, as we can set the domain ANI per tenant, and if ever need be, a particular extension is easily assigned their own ANI. If a user dials an 'emergency number', which ANI (Trunk, Domain, or Extension) ANI is presented? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.