atcomsystems.ca/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems SCMC with WE VoIP

Has anyone a manual for the programming in the SCMC. I have programmed the SCMC already so that WE VoIP works in my local WLAN. But I have no connection to my Samsung WLAN Controller and I can not use my WE VoIP in other WLANs. With the Office Serv we had a very good programming guide step by step.
Thanks.

I take it you don't have a we-voip install guide for SCMC... send me your email and i can send you one.

Hi, I have programmed my WeVoIP with the SCMC, but there are a few things, which doesn't work really good:
In the office serv I could use parameter 5.2.29 to replace the international prefix of my contacts in my mobile phone into the national format.
With the SCMC I only find, that I could make an access code with the international prefix without + and send this pattern to my location based routing. For example 49 to the SIP trunk. But then I can create an extension 49. And when I have customers who had stored a lot of inernational numbers in the smartphone I need for every international number a pattern. And then I can not unse all these pattern as extension numbers.
I tryed also to work with Outbound MCN but there I had no solution because of the + in the stored number.
Also it is very angry that I need a NAT traversal license to use WEVoIP outside my office.
Thanks.

NAT traversal license? Is that the same as our SBC license?

NAT traversal license you need, when you do not use the WAN interface. With WAN interface you need the SBC licence.
Our router has already a SBC inside so therefore we don't use the SBC. But with firmware 2 samsung has created a new license. And when you want to use WeVoIP in other WLANs you need the NAT traversal license.

Do you have any ideas concerning "translation" of +49... into 0...

Sorry i don't have a clue how to fix that.
If you have an SBC internally the Compact should have no clue that the We-voip is a remote user unless the client is reporting it..?

We also have a standalone SBC and it's handing everything off to the SCM-C as if it's local on the network, including we-voip users. So as far as the SCM-C is concerned all remote IP phones and we-voip users are on the local network.

That license is annoying though, not necessary.

But what I had forgotten to say, is, that I want to use the WeVoIP with ISDN trunk. And unfortunately I can not dial +49 for example with ISDN trunk. This works only with SIP trunk.

Any ideas? Thanks a lot!

You need to create an outbound MCN rule todo the digit manipulation, then apply that rule to the ISDN trunk route.

Trial and error combined with the route trace should tell you what you need to know

Hi nameless, I tryed already with the Outbound MCN, which I applied in the Priority Routing but without sucess.
When I do not use the pattern, I see in my WeVoIP Client the number 0+49xxxxxxx. When I use the pattern, I see, when I am dialing, the stored number +49xxxxxxxx.
In the Outbound MCN, I tryed already 0X49? --> 00 and other different combinations which were allowed, but without success.
In the Office Serv I used 0+49 --> 00, it works.
In the SCMC I can not use the +.

Thanks.

I found the guide from samsung about this.
PM me your email and i'll send it.

It's a number translation not an outbound MCN