[cisco-voip] Incoming SIP Calls to CUBE not working correctly

[Nick Matthews]

Hi Zahid,

Something doesn't add up here - the provider should be sending the
reply back to exactly what we've put in the contact header, and we
should be listening on that IP:port.

In 12.4(20)T and later you can change the listen port - but only to a
single port:

voice service voip
sip
listen-port non-secure <port>

You would need to change both sides contact port for CUBE if this is a
SIP-SIP CUBE.


It may be more likely that you have a SIP fixup or NAT issue than any
type of listen port issue.

-nick

On Sun, Aug 16, 2009 at 6:26 PM, Zahid Hassan<zhassan at gmx.net> wrote:
> Dear All,
>
>
>
> Is there a way to change the INVITE port to non 5060  ?
>
> My provider is saying that my CUBE is dropping calls
> because its not accepting INVITE from non 5060 ports.
>
> The port for the INVITE and contact header do not match and their ACK for
> The 200 OK go to port 5060 and my CUBE is not getting the ACK they send.
> I should change the INVITE port from a non 5060 so it matches what the CUBE
> sends in the contact header.
>
>
> Any input of comment on this will be greatly appreciated.
>
>
> Regards,
>
>
> Zahid
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>