[cisco-voip] SIP-Trunk with To-Header

[Mark Holloway]

This is why we use Acme Packet Session Directors (SBC's) between our Broadworks platform and ISR routers running CUBE.  The Acme SD can re-write the request URI so the CPE device does not need to route on the To header. I know Verizon is using Broadworks but I am not certain if they are using Acme.

On Mar 17, 2010, at 9:53 AM, Erin Mikelson wrote:

> I just worked with the CUBE BU, CUSP BU, Cisco Advanced Services, TAC, and my Channel SE team about this.
>  
> Bottom line, CUBE and CUCM cannot route on the TO field.
>  
> We ran into the same issue. Telco wanted to send a generic request-URI and have us route on the TO field. The Cisco Unified Sip Proxy server can do this. However, CUBE, CUCM, CVP etc. cannot. And yes, I did get my hands on a TCL script for CUBE, which worked on the inbound to replace the Request-URI with the TO field so everything else would work. BUT, we ran into other issues.
>  
> For example, when routing to a busy phone or a non-registered phone, the SIP messages would die at CUBE. CUBE with the TCL script would not pass them back to the SIP Proxy or back to the Telco. Cisco said that the TCL script (which they provided) is not supported and that I needed to engage development to come up with a script that will take into consideration all the SIP Messages.
>  
> Also, neither CUSP, CUBE, nor CUCM can replace the Request-URI with the value in the TO field. 
>  
> The telco did come through with a way that they can replace the Request-URI with the DNIS when routing calls in. Hooray for Verizon. :)
>  
> In any case, I've learned a lot about SIP and the SIP Proxy server, which seems to be a cool little box.
>  
> Erin
> 
> Hotmail: Trusted email with powerful SPAM protection. Sign up now. _______________________________________________
> 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/20100317/4aacecae/attachment.html>