<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Hello,</div><div><br></div><div>I am having trouble understanding exactly how the top-hiding scenario does a call compared to one that simply uses the tm module to relay it. Because of this lack of understanding I can't even begin to understand the impact it would have on accounting.</div><div><br></div><div>I'm okay with tm-based configurations that relay calls from one side to the other. I have accounting configured to save a radius record in a mysql DB, and it works quite well. My goal is to augment my existing configuration in such a way to accomplish exactly what the scenario name would suggest – to hide the topology in the SIP headers. I'd like to mimic as much of my existing configuration as possible, yet invoke the scenario in such a way to accomplish the top-hiding part.</div><div><br></div><div>I've looked at the B2B examples, and while I can follow them for the most part, the big picture isn't clicking on how it all works. Perhaps someone has some hints to point me in the right direction?</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div></body></html>