I see a couple of things that might be causing an issue. First, does 
your ITSP take 10 or 11 digits? 10 digit would be 847-382-7754 and 11 
would be 1-847-382-7754, you are sending 11 to them (not sure if this 
matters). Second, you are sending your internal caller ID to the ITSP, 
which is most like the reason why it's kicking you out. Set your Caller 
ID name and 10 digit number in your ITSP gateway settings in sipX then 
try it again.

Josh Patten
Assistant Network Administrator
Brazos County IT Dept.
(979) 361-4676


On 12/21/2009 10:09 AM, D. R. Lang wrote:
> Josh,
>
> Here is a packet trace.
>
> Duane
>
> -----Original Message-----
> From: Josh Patten [mailto:[email protected]]
> Sent: Monday, December 21, 2009 10:00 AM
> To: D. R. Lang; [email protected]
> Subject: Re: [sipx-users] ITSP outbound 602 Error
>
> It sometimes does. I would need a more complete trace to see if
> everything is right. Please don't forget to CC the list when responding
> to a mailing list post.
>
> Josh Patten
> Assistant Network Administrator
> Brazos County IT Dept.
> (979) 361-4676
>
>
> On 12/21/2009 9:54 AM, D. R. Lang wrote:
>    
>> Josh,
>> If calls orginate from the provider work on 5080, would that no indicate  
>> that is not necessary.  Dosent the outbound registration take care of that?
>>
>> Duane
>>
>> ________________________________________
>> From: Josh Patten [[email protected]]
>> Sent: Monday, December 21, 2009 9:52 AM
>> To: [email protected]; D. R. Lang
>> Subject: Re: [sipx-users] ITSP outbound 602 Error
>>
>> You need to inform your ITSP that they need to point SIP traffic to you
>> on port 5080 and not 5060.
>>
>> Josh Patten
>> Assistant Network Administrator
>> Brazos County IT Dept.
>> (979) 361-4676
>>
>>
>> On 12/21/2009 9:47 AM, D. R. Lang wrote:
>>
>>      
>>> I have version 4.04 running internally.  I can call the external trunk 
>>> lines and they forward calls to the internal hunt groups.  When dialing out 
>>> I get fast busy signals.  When packet tracing the output of the gateway I 
>>> see the following results.
>>> Registration to ITSP 200,  viewing the results both trunks are registered.
>>> 10.250.200.18 216.143.130.36 Request: REGISTER 
>>> sip:sip.voipyourphone.com:5062                           ! (trunk2)
>>> 10.250.200.18 216.143.130.36 Request: REGISTER 
>>> sip:sip.voipyourphone.com:5060                           !(trunk1)
>>> 216.143.130.36  10.250.200.18 Status: 407 Proxy Authentication Required
>>> 216.143.130.36  10.250.200.18 Status: 407 Proxy Authentication Required
>>> 10.250.200.18 216.143.130.36 Request: REGISTER 
>>> sip:sip.voipyourphone.com:5062                           !(trunk2 with 
>>> noucne)
>>> 10.250.200.18 216.143.130.36 Request: REGISTER 
>>> sip:sip.voipyourphone.com:5060                           !(trunk1 with 
>>> nounce)
>>> 216.143.130.36  10.250.200.18 Status: 200 OK                                
>>>                                                                        
>>> !(Trunk2 2 bindings one for 3cx and one for sipx)
>>> 216.143.130.36  10.250.200.18 Status:200 OK                                 
>>>                                                                        ! 
>>> Trunk1 2 bindings one for 3cx and one for sipx)
>>> Inbound Call
>>> 216.143.130.36  10.250.200.8 Request:INVITE sip:[email protected]:5060 
>>> rinstance=                                             !( 3cx  trunk1)
>>> 216.143.130.36  10.250.200.18 Request:INVITE sip:[email protected]:5060 
>>> rinstance=                                           !(spx Trunk1)
>>> 10.250.200.18 216.143.130.36 Status 180 Trying                              
>>>                                                                             
>>>                          !( sipx  trunk1)
>>> 10.250.200.8 216.143.130.36 Status 180 Trying                               
>>>                                                                             
>>>                           !( 3cx  trunk1)
>>> ...
>>> Phones ringing both systems
>>> Outbound Call
>>> 10.250.200.18 216.143.130.36 Request:  INVITE   
>>> [email protected]:5060 ; user=phone
>>> 216.143.130.36  10.250.200.18 Status: 100 Trying
>>> 216.143.130.36  10.250.200.18 Status: 603 Declined
>>> I can't get past this point.  The provider claims that Sipxecs is approved 
>>> but will not trouble shoot the packet stream.
>>>
>>> Duane Lang
>>> [email protected]
>>> _______________________________________________
>>> sipx-users mailing list [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users
>>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
>>> sipXecs IP PBX -- http://www.sipfoundry.org/
>>>
>>>
>>>        
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to