SIP trunk termination to PSTN

[BIS]

Hi All,

I have no experience at all with SIP trunks, so this might be a dumb question, but here goes.

We have a partner who have SIP trunks (we only have ISDN30) - and they claim they cannot terminate to us (via a standard PSTN termination number).

Anyone know why this would be, and care to explain to me?

 

[montyzummer]

They may well be looking to present the digits in full E164 format so +44123456789 (in the case of the uk) , but all this depends on your architecture , you would usually have an SBC>session manager>CM and the sip trunks would terminate on the sbc , again usually digit handling is done on session manager.

You can terminate a sip trunk direct into CM but you are limited to protocols TCP or TLS and you have very little going on in the way of security in this setup.

What exactly is this sip trunk for ?

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[BIS]

Hi montyzummer,

Thanks for your reply. We don't have an SBC yet, we are being quoted EUR 1700.00 for a virtual one with 30 channels, plus some project management fees. Does that sound acceptable? Do you know if we can easily increase the amount of channels - is that just a licensing issue?

Sorry for what may be dumb questions, but SIP is new to us...

 

[montyzummer]

Pricing I am not that familiar with but that cost sounds a little high but not unreasonable for thirty channels ( somebody else may disagree) , I would make sure whatever SBC you go with that you have an Avaya approved model and one that is devconnect , this just means the interoperability has been assured and you will get support , the Avaya ASBCe is Avaya`s offering and the one I now work with and know and prefer to others on the market (purely because I have access to documentation and support from Avaya if needed and its obviously a supported known entity.)

Don't get fooled into being shoehorned into buying one sbc or the other as that is all the person quoting is familiar with , go with my above suggestions , as for increasing capacity , yes it is generally all down to licensing.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[montyzummer]

And again what is the exact requirement (end goal) as you may not actually need an SBC depending on the setup of the connectivity.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[BIS]

Thanks

End goal, I guess, is to have a working SIP trunk that others can terminate to.

 

[montyzummer]

Yes but what I mean is this sip trunk from the CM connecting to other equipment on your lan / wan /pstn , as a SBC is a edge device required to secure your internal stuff from unwanted external nasties.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[BIS]

Well here I go showing off my ignorance again then ..

We will get a SIP trunk from a provider, I assume it will terminate to the SBC. From there, it will need to go to CM, and somehow get converted to a VDN like a standard ISDN trunk would do with inc-call-hand treatment - is that also different?

 

[montyzummer]

ok so it can be done from inc t , but you will more likely put a session manager in the mix and all the digit manipulation is done from there and passed onto CM as a VDN station etc etc , have you already got or been told about session manager.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[BIS]

As we have never done SIP before - we do not have a session manager either :-(

I wonder what that will cost me...

 

[montyzummer]

Hardware for a session manager / system manager.... can be VMware , if you are going sip I would be seriously getting this included in any architecture if im not wrong no licensing cost per say.

APSS (SME)
ACSS (SME)
ACIS (UC)