[cisco-voip] SIP trunk dropping calls

[Mark Holloway]

Not all providers reject calls with no From number on the SIP trunk.  We use Broadworks and for customers who want to send anything other than one of their DID's we enable Unscreened Calling.  It requires a Trunk Group Identifier to be set in Broadworks and CUBE must be used to inject the TGI into the registration and invite messages.


On Dec 7, 2009, at 12:24 PM, ccieid1ot wrote:

> I do know that the SIP provider will drop the call if there's no ANI.
> 
> On Fri, Dec 4, 2009 at 6:22 PM, Nick Matthews <matthnick at gmail.com> wrote:
>> As well - csim is not a great testing tool for VOIP protocols.  I
>> would not depend on it.
>> 
>> -nick
>> 
>> On Fri, Dec 4, 2009 at 7:21 PM, Nick Matthews <matthnick at gmail.com> wrote:
>>> You need to explain the call flow more.  All I see here is that you
>>> have two cisco gateways, one makes a call, gets ringback, does media
>>> negotiation, and then hangs up 20 seconds after the ringback comes in.
>>>  Why does the user not answer within 20 seconds?  What's on the other
>>> sides of both of these sip connections?
>>> 
>>> 
>>> -nick
>>> 
>>> On Fri, Dec 4, 2009 at 5:45 PM, Ali El Moussaoui <mousawi.ali at gmail.com> wrote:
>>>> Hello,
>>>> 
>>>> We installed an IPIP gateway and am trying one of the SIP legs using CSIM
>>>> but i am not able to figure out why calls are failing although all sip
>>>> messages seems correct.
>>>> 
>>>> The full trace is attacehd i appreciate any help.
>>>> 
>>>> Regards,
>>>> Ali
>>>> _______________________________________________
>>>> 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
>> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip