Josh, Here is a packet trace.
Duane -----Original Message----- From: Josh Patten [mailto:jpat...@co.brazos.tx.us] Sent: Monday, December 21, 2009 10:00 AM To: D. R. Lang; sipx-users@list.sipfoundry.org 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 [jpat...@co.brazos.tx.us] > Sent: Monday, December 21, 2009 9:52 AM > To: sipx-users@list.sipfoundry.org; 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:xxx...@75.150.xxx.xxx:5060 >> rinstance= !( 3cx trunk1) >> 216.143.130.36 10.250.200.18 Request:INVITE sip:xxx...@75.150.xxx.xxx: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 >> 1847xxx...@voipyourphone.com: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 >> d...@hmnets.com >> _______________________________________________ >> sipx-users mailing list sipx-users@list.sipfoundry.org >> 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/ >> > >
10-250-200-18capture.pcap
Description: 10-250-200-18capture.pcap
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
