I'm not a Samsung dealer, but please don’t ignore the request for help

Thank You.

A little background…
We have purchased OfficeServ 500 for the building we're managing to supply phone services to tenants.

We installed and maintained it ourselves right from the beginning. All of as a techies with considerable experience in IT and telephony.

Naturally none of the dealers (and Samsung themselves here in Melbourne) want to deal with us or provide us with any help whatsoever. Maybe that’s no the case outside Australia so I’m hopping someone will help me out.

We bought MGI2 from Samsung (without support ) and have it going here perfectly.

We have Samsung's VoIP phones working just fine.
We have SIP trunking working to offload all long distance and International calls to our asterisk server just fine.

The problem is that SIP implementation of OfficeServ 500 is not complete.
It does not support REGISTER command.
It does not use username/password either for inbound or outbound calls, it just uses the station's number as a username without password.

So our asterisk system is configured accordingly.

Connecting SIP phones to OfficeServ would not be a good idea because you cannot authenticate the incoming connection.

For some reason MMC840 is ignored for SIP connections and PABX allows any SIP user/pass to connect to it.

After some digging around we found that there MMC839 (SIP AUTH) is probably what we need. But it is disabled (Invalid Data) on our software.

So the question I’m asking is:

How to configure SIP on OfficeServ to accept inbound SIP with user/pass configured in MMC840 only (no un-authenticated connections)

The relevant versions on PBX:
MCP 2.13L
SCP/LCP 2.07
MGI2 1.21

Please help us with this issue.
There is not many IP certified dealers in OZ and the ones who are don’t really know much about SIP, MGI2 and OfficeServ because, i quote "You're bloody first one to install it mate". There are installations of MGI card but only to connect Samsung phones to it, so far, I have not seen anyone doing SIP trunking or SIP serving.

Thank you in advance for your help.

Regards
Boris

Can anyone help us our with the SIP problem we have?
Or at least point us in the right direction?

Any help would be greatly appreciated.

Unfortunately none of them know much about connecting SIP phones to OfficeServ 500.

None even heard of MMC840 yet is is there.

Any attemts to find out how to activate it or in wich version of software it is activated are fruitless..

We also had the same questions as you, but i believe even the later Samung software still does not support SIP authentication.

What is MMC 839 as we don;t have this option on MCP2 V2.37??

We would like to set up a SIP server like yoursleves. Can you please provide information on the programming of your Asterisk so we can do the same

Thank you

quote:

---

Originally posted by Boris:
Hi,

I'm not a Samsung dealer, but please don’t ignore the request for help

Thank You.

A little background…
We have purchased OfficeServ 500 for the building we're managing to supply phone services to tenants.

We installed and maintained it ourselves right from the beginning. All of as a techies with considerable experience in IT and telephony.

Naturally none of the dealers (and Samsung themselves here in Melbourne) want to deal with us or provide us with any help whatsoever. Maybe that’s no the case outside Australia so I’m hopping someone will help me out.

We bought MGI2 from Samsung (without support ) and have it going here perfectly.

We have Samsung's VoIP phones working just fine.
We have SIP trunking working to offload all long distance and International calls to our asterisk server just fine.

The problem is that SIP implementation of OfficeServ 500 is not complete.
It does not support REGISTER command.
It does not use username/password either for inbound or outbound calls, it just uses the station's number as a username without password.

So our asterisk system is configured accordingly.

Connecting SIP phones to OfficeServ would not be a good idea because you cannot authenticate the incoming connection.

For some reason MMC840 is ignored for SIP connections and PABX allows any SIP user/pass to connect to it.

After some digging around we found that there MMC839 (SIP AUTH) is probably what we need. But it is disabled (Invalid Data) on our software.

So the question I’m asking is:

How to configure SIP on OfficeServ to accept inbound SIP with user/pass configured in MMC840 only (no un-authenticated connections)

The relevant versions on PBX:
MCP 2.13L
SCP/LCP 2.07
MGI2 1.21

Please help us with this issue.
There is not many IP certified dealers in OZ and the ones who are don’t really know much about SIP, MGI2 and OfficeServ because, i quote "You're bloody first one to install it mate". There are installations of MGI card but only to connect Samsung phones to it, so far, I have not seen anyone doing SIP trunking or SIP serving.

Thank you in advance for your help.

Regards
Boris

[This message has been edited by Boris (edited February 04, 2005).]

---

quote:

---

Originally posted by Boris:
Hi,

I'm not a Samsung dealer, but please don’t ignore the request for help

Thank You.

A little background…
We have purchased OfficeServ 500 for the building we're managing to supply phone services to tenants.

We installed and maintained it ourselves right from the beginning. All of as a techies with considerable experience in IT and telephony.

Naturally none of the dealers (and Samsung themselves here in Melbourne) want to deal with us or provide us with any help whatsoever. Maybe that’s no the case outside Australia so I’m hopping someone will help me out.

We bought MGI2 from Samsung (without support ) and have it going here perfectly.

We have Samsung's VoIP phones working just fine.
We have SIP trunking working to offload all long distance and International calls to our asterisk server just fine.

The problem is that SIP implementation of OfficeServ 500 is not complete.
It does not support REGISTER command.
It does not use username/password either for inbound or outbound calls, it just uses the station's number as a username without password.

So our asterisk system is configured accordingly.

Connecting SIP phones to OfficeServ would not be a good idea because you cannot authenticate the incoming connection.

For some reason MMC840 is ignored for SIP connections and PABX allows any SIP user/pass to connect to it.

After some digging around we found that there MMC839 (SIP AUTH) is probably what we need. But it is disabled (Invalid Data) on our software.

So the question I’m asking is:

How to configure SIP on OfficeServ to accept inbound SIP with user/pass configured in MMC840 only (no un-authenticated connections)

The relevant versions on PBX:
MCP 2.13L
SCP/LCP 2.07
MGI2 1.21

Please help us with this issue.
There is not many IP certified dealers in OZ and the ones who are don’t really know much about SIP, MGI2 and OfficeServ because, i quote "You're bloody first one to install it mate". There are installations of MGI card but only to connect Samsung phones to it, so far, I have not seen anyone doing SIP trunking or SIP serving.

Thank you in advance for your help.

Regards
Boris

[This message has been edited by Boris (edited February 04, 2005).]

---

You can only do SIP trunking with the 500R2, not SIP station.

Meaning you can only get one phone to work unless you hook it up to a SIP server (like you did) but Samsung wont support ANY SIP servers.

You need to talk to a man named Neville Thomas. He is in the US (Dallas) and he is the VoIP develper for Samsung's BCS division (in Dallas).

Good luck and let me know how it goes...

Samsung is waiting to enable this until they feel they will not lose sales of their IP keysets.

I have used a SIP Proxy from I3 to do the auth piece and SIP trunking in the samsung.

You can use virtual stations in the 500 and forward them to the SIP trunk group. This allows you to dial the SIP phone. Use the DID table to direct calls out through the pstn.

The only problem is that you can not make a SIP phone part of a Hunt group because it is a virtual station fowarded.

I hope this helps