[cisco-voip] Authenticated SIP trunk

[Matt Slaga (US)]

What I mean by "not single line sip providers" is that most companies
are not going to purchase single sip trunk lines from a provider.  They
will go to a SIP wholesaler or SIP trunk provider, not manage 50 or so
individual line trunks.

The only people trying to do this is home lab users, and Cisco isn't
going to provide this type of functionality and R&D just to make home
lab users happy.



-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kelemen Zoltan
Sent: Tuesday, September 11, 2007 12:44 PM
To: Christian Hennrich
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Authenticated SIP trunk

I wonder what would they consider "not a small amount". When you think 
that one selling point in IP telephony used to be "free interoperability

with other VoIP networks", the thing is pretty difficult to obtain. 
True, once external VoIP link might not have been important at all, 
however, with the growth of companies (and even some "serious ones") 
offering cheap VoIP connectivity, mostly through SIP, not being able to 
interconnect to those with your new, shiny and expensive VoIP system 
just seems a bit ... underwhelming.
</flame>

I did such a thing once, inserting an Asterisk server between the CCM 
and the SIP provider (and thus let Asterisk handle authentication), 
however, for one reason or another, the thing wasn't really stable, so 
the idea was dropped (that same Asterisk box remains as a voicemail, 
though :) ). You might have more luck with a proper SIP server (Asterisk

being an IP PBX, but not a complete SIP implementation) or, perhaps if 
you can talk your provider into allowing unauthenticated connections 
from your IP (good luck with that but it's an idea, anyway)

regards,
  Zoltan

Matt Slaga (US) wrote:
>
> This cannot be done.  Cisco focuses on wholesale trunks, not on single

> line sip provider.  I have only been able to get outbound dialing to 
> work, and when I questioned the CCM BU about it, they said that is not

> even on their roadmap because of the small amount of requests.
>
>  
>
> *From:* cisco-voip-bounces at puck.nether.net 
> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Christian 
> Hennrich
> *Sent:* Tuesday, September 11, 2007 3:03 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Authenticated SIP trunk
>
>  
>
> Hi,
>
> I'm playing around with CM 6.0 and I'm trying to call over an carpo.de

> SIP trunk. Unfortunately this does not work.
>
> Has anyone succesfully configured CM 5.X or 6.X to use authenticated 
> SIP trunks? sipgate or any other free SIP provider?
>
> I have followed the Cisco manuals to configure the trunk in the 
> security guide, but with no success. A guidance would be very helpful.
>
> Cheers
> Christian
>
>
------------------------------------------------------------------------
>
> *Disclaimer: This e-mail communication and any attachments may contain

> confidential and privileged information and is for use by the 
> designated addressee(s) named above only. If you are not the intended 
> addressee, you are hereby notified that you have received this 
> communication in error and that any use or reproduction of this email 
> or its contents is strictly prohibited and may be unlawful. If you 
> have received this communication in error, please notify us 
> immediately by replying to this message and deleting it from your 
> computer. Thank you. *
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> 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

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.