I added port 8060 to my SBC config and have the customer connect to either 5060
or 8060. Port 8060 will by pass a SIP ALG. My SBC (Acme Packet) still
communicated to Broadsoft on 5060. It is an easy change to the acme
sip-interface config
sip-interface
state enabled
realm-id accessBWORKS
description
sip-port
address A.B.C.D
port 5060
transport-protocol UDP
tls-profile
allow-anonymous registered
ims-aka-profile
sip-port
address A.B.C.D
port 5060
transport-protocol TCP
tls-profile
allow-anonymous registered
ims-aka-profile
sip-port
address A.B.C.D
port 8060
transport-protocol UDP
tls-profile
allow-anonymous registered
ims-aka-profile
[…]
--
Matthew S. Crocker
President
Crocker Communications, Inc.
PO BOX 710
Greenfield, MA 01302-0710
E: [email protected]
P: (413) 746-2760
F: (413) 746-3704
W: http://www.crocker.com
On Jun 26, 2014, at 10:34 AM, Feby Francis <[email protected]> wrote:
> <image001.gif>
> Experts,
>
> I have a customer who travels a lot and uses our softphone offering, I need a
> solution to overcome the situations when the port 5060 is blocked.
>
> Is there any work around to solve the port blocking problems? We use standard
> 5060 on the SBC and my switch vendor is Broadsoft.
>
>
> Thanks for all the help and advices,
> Feby Francis
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
