[cisco-voip] Assistance if you are able.
Brian Meade
bmeade90 at vt.edu
Wed Sep 7 15:18:57 EDT 2022
You'll want your re-routing CSS on the Remote Destination Profile to target
a partition/route pattern going to your SBC for Direct Routing. If you're
using CUBE and not a dedicated CUBE for Direct Routing, probably worth
using some sort of prefix like 5555 and match that to send calls to MS
Teams. You can put that prefix right on the route pattern.
On Tue, Sep 6, 2022 at 6:39 PM Tim Smith <tim.smith at enject.com.au> wrote:
> Hi Terry,
>
> I would probably try and avoid SNR.
> I think overall, it's going to give you problems.
> I think experience is going to be better if people are fully running on
> one or the other - and you just route between them.
> If you are moving away from Cisco.. what's the reasoning for still ringing
> a desk phone?
>
> What SBC are you using for Teams?
>
> Cheers,
>
> Tim
>
>
> On Wed, 7 Sept 2022 at 07:12, Terry Oakley <Terry.Oakley at rdpolytech.ca>
> wrote:
>
>> We are adding MS Teams voice to our Cisco environment. What I am
>> hoping to do is use the feature of Single Number Reach (SNR) with Remote
>> destination so that callers into our PRI will continue to be handled by the
>> CUCM but also ring at the MS Teams voice device if setup. So what I am
>> trying to do is take a call from the PSTN into the CUCM and using Single
>> Number Reach ring the Cisco phone (if present) and also send the call out
>> to the trunk and SBC to be sent to the MS Teams voice device. I have
>> been able to get the SNR to work to my cell phone but I have hit a mental
>> block, namely me, in now making this work to move the call to the SBC via
>> the configured trunk.
>>
>>
>>
>> I am thinking I need to setup a translation pattern to make this work but
>> I am only about 67% sure I am heading in the right direction. The other
>> issue is that our Cisco support has been canceled in an effort to save
>> money so I am working on a production system with very little support.
>> Such fun.
>>
>>
>>
>> Any assistance would be wonderfully accepted.
>>
>>
>>
>> Terry
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> _______________________________________________
> 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/20220907/96341f7b/attachment.htm>
More information about the cisco-voip
mailing list