[cisco-voip] CUBE SIP Trunk IP Authentication

[Paul]

Euan,

What he means is that your gateway must be configured for all of its SIP traffic to be bound to one IP address. This IP address is what you will tell your ITSP you will be using to connect to them. The ITSP will then ONLY accept your SIP traffic from that IP address. If your CUBE is using NAT behind an ASA then one of the public IP addresses you have connected to the ASA will have to be the address you tell your ITSP you'll be using for connectivity. 

You can use this for reference...

http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-sipsip.html


depending on the number of SIP sessions required by your site, you'll have to purchase an appropriate CUBE license for the number of simultaneous sessions needed...

________________________________
 From: Euan McGregor <euan at mcgregor.co>
To: "Mike Wilusz, (miwilusz)" <miwilusz at cisco.com>; cisco-voip at puck.nether.net 
Sent: Monday, September 3, 2012 5:47 PM
Subject: Re: [cisco-voip] CUBE SIP Trunk IP Authentication
 

Thanks Mike, 
It is a BE 3000 so all I can do is point the PSTN connection to the router. Not sure what you mean by pointing the call manager to the bound interface that interface is the WAN port of the router which is directly behind the firewall. 
Apologies if I have missed the point still new to this stuff. 
Thanks
Euan
On Sep 3, 2012 10:15 PM, "Mike Wilusz (miwilusz)" <miwilusz at cisco.com> wrote:

Just ensure that your CUCM is pointing to the same bind interface.  Keep in mind the messages will still flow out likely the internal interface, but the IP inside the message will be from the bind interface.  Anything else I can help with, let me know.
>
>
>-mike
>
>From: Euan McGregor <euan at mcgregor.co>
>Date: Monday, September 3, 2012 5:12 PM
>To: Michael Wilusz <miwilusz at cisco.com>
>Subject: Re: [cisco-voip] CUBE SIP Trunk IP Authentication
>
>
>
>Hi Mike, 
>
>
>Thanks for that, yes the provider is simply basing the authentication on the source IP. Will that not affect the SIP trunk going the other way back to call manager if I specifically bind it to an external port on the CUBE?
>
>
>Regards,
>
>
>Euan
>
>
>On Mon, Sep 3, 2012 at 9:53 PM, Mike Wilusz (miwilusz) <miwilusz at cisco.com> wrote:
>
>Euan,
>>
>>
>>I think "IP Authentication" can mean a few different things.  I have seen it mostly mean that the provider is not requiring a username/password, but that you must send all SIP messages from a pre-allowed IP address, typically your WAN interface.  On CUBE, you'll need to use the bind command to bind the SIP messages to the interface with the IP address that is allowed by the carrier.  Take a look here:  http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb_1142_ps5640_TSD_Products_Configuration_Guide_Chapter.html
>>
>>
>>-mike
>>
>>From: Euan McGregor <euan at mcgregor.co>
>>Date: Monday, September 3, 2012 3:23 PM
>>To: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
>>Subject: [cisco-voip] CUBE SIP Trunk IP Authentication
>>
>>
>>
>>Hello, 
>>
>>
>>This may be in the archives but I can't see anything.
>>
>>
>>I have a customer site who I am trying to setup a CUBE and a SIP trunk but the provider only accepts IP authentication from our IP address and not username and password authentication. I have searched Google but I cannot find any documentation on how to get the CUBE (881) to register to the provider (Pulsant here in the UK).
>>
>>
>>Can anyone point me in the direction of a config, document or even a heads up how to get it to work?
>>
>>
>>Thanks in advance.
>>
>>
>>Regards,
>>
>>
>>Euan
> 
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120903/5d3805d1/attachment.html>