*Edited to remove MMC numbers*

Anybody have a programming check list for getting SIP Trunks to work properly? I got them to connect with the SIP provider's server (I get the 'Yes' in "SIP Server Available" field). I also get dial tone when accessing the SIP Trunks via 8501, but I cannot complete any calls properly. I placed the assigned phone number in the DID table as well. Incoming calls get an error message about circuits being busy, and outgoing calls come back into the phone system no matter what I dial. I've tried using the manual to get the incoming & outgoing VOIP digit mmc's set up, but as most of you probably know, those manuals are not always detailed enough.

Any help would be much appreciated.

System is OS7200 v. 4.42a

Eric

PM Sent

downgrade to 4.30i
I believe samsung is now aware of the 4.4X problem across all OS7XXX and are looking into it. Simply put your SIP trunks will not stay registered to the provider no matter what you do.

I would be careful making statements like you did. We are running v4.42a with SIP trunks from Broadvox and we do not have a problem. There is an issue, but to say SIP doesn't work on v4.42a is wrong.

Thanks for the responses, guys. I finally got the incoming calls working properly. However, still struggling with outgoing. Calls ring out to the proper number and get connected, but no audio in either direction. Working with our SIP provider and our Distributor's tech to iron that out...I'm thinking a port issue as that's usually the case with good connections lacking audio in ITP and Softphone scenarios. Thanks again for taking the time to reply.

Lol, that came out wrong, no dig meant to Samsung. Just pointing out their is an issue with sip on 4.4x, but 4.30 runs flawlessly.

Running back to 4.30 on a 7200-S isn't possible so it is good news that at least it works.

Anyone that has cheat sheets and that can send them to [email protected] we would appreciate it.

We are just finally starting to do SIP. The cost advantages and flexibility just cannot be ignored any longer.

I would be curious to see how people are doing getting faxes to work via SIP-only services like Broadvox.

No problems via the Officeserv systems out to an SLI port? I wish the SIP providers would provide E-faxing as part of their packages. That would seem like a no brainer.

Then there is the ultimate test - postage dial up machines.

When you guys convert to SIP do you keep faxes with the local telco or do you 'go for it' . I know Linksys makes a T38 to fax converter also.

Samsung supports T38 for faxes.

As far as the registration dropping, we had that problem with 4.41b on the 7030/7100, and 4.42b on the 7200. A temp version c for both has been released down here that works fine. I have upgraded a couple of systems that I had previously downgraded to 4.30 and they are working great.

Other modem type devices, like EFTPOS for eample dont seem to work properly, and on testing the system doesnt recognise them as fax tones, so it doesnt use the T38 protocol.

We usually keep at least one standard PSTN line connected to the system for the main advertised number, diverting on busy to the new SIP lines, plus the fax line for the fax and EFTPOS machines.

From experience the SIP lines will go off the air from time to time, due to modems rebooting, internet dropouts etc so we like to keep the legacy lines there as a backup.

Broadvox admits that it does not do FAX well and suggest that you keep copper for your FAX/.

Thanks for all the posts. Finally got it to work without a hitch by rolling back to software v 4.30. The only change I had to make was stripping the + they were sending along with the DID.

What about customers that use Efax.com or MyFax.com? A SIP call calls in on a Broadvox SIP VDID - can you just forward it out to the Myfax assigned 800 number? Do you think that would be OK?

Dave with your eftpos issue, have you tried forcing g.711 (since you insist on a dedicated adsl service bandwidth shouldn't be an issue)?

Though I do know that optus wont support eftpos on their vodsl pstn service (at least the small business one which cant even do a line hunt properly)

Yeah, I have tried forcing to g711 for the EFTPOS, it was an improvement but was still only about 2 in 3 transactions worked, and the ones that did work took close to a minute to complete, compared to 15 to 20 seconds on a PSTN line.

My office 7100 v4.46a is dropping SIP service now and then. I wish Samsung would fix that with a Beta. Going back to 4.30 is ok for now though.

I can confirm the downgrade works, just downgraded our office 7200, still running an MCP, to 4.30i and so far (as of 4:45pm today_) I haven't had to reboot the switch to get the sip trunk to start taking inbound calls..... so there is some truth to 4.30i being the "sip savior"

-Andy