[cisco-voip] CUBE SIP Trunk IP Authentication
Mark Holloway
mh at markholloway.com
Mon Sep 3 21:36:35 EDT 2012
The scenario is a little confusing. You said the provider only accepts authentication from your IP address, and not username/password authentication, but at the same time you are saying CUBE needs to register to the provider. Usually registration to a provider means you are registering SIP credentials that include a username and password.
If what you need is your provider to see all SIP traffic coming from the same IP address then bind all sip traffic to a specific IP (for example, a loopback IP or WAN IP)
voice service voip
fax protocol pass-through g711ulaw
sip
bind all [source-interface]
In the event you did need to register authentication credentials to the provider it would be under "sip-ua"
sip-ua
credentials username 9495551000 password 551000 realm BroadWorks
authentication username 9495551000 password 551000 realm BroadWorks
no remote-party-id
set pstn-cause 3 sip-status 486
set pstn-cause 34 sip-status 486
set pstn-cause 47 sip-status 486
registrar dns:sip.itsp.com expires 3600
sip-server dns:sip.itsp.com
connection-reuse
On Sep 3, 2012, at 3:23 PM, Euan McGregor wrote:
> 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/61d18722/attachment.html>
More information about the cisco-voip
mailing list