I had asked callcentric about some of my attempts they responded to me about the calls they saw as follows:
> Aug 19, 2012 11:02 PM : Customer service > Hello, > > At this time, we see that our system is unable to route your call as dialed, > and we see the following in our trace: > > 23:55:04 Rx udp:69.140.220.18:5060 > INVITE sip:**275*883975*[email protected] SIP/2.0 > Via: SIP/2.0/UDP > 192.168.230.233:5060;rport;branch=z9hG4bKPjc2a16e1f-d764-43f7-aca1-f481393bef72 > Max-Forwards: 70 > From: > <sip:[email protected]>;tag=69239813-9a39-40f1-aec9-e44fb0465560 > To: <sip:**275*883975*[email protected]> > Contact: <sip:[email protected]:5060> > Call-ID: faab11d4-a330-4095-9974-aa14d0d3b602 > CSeq: 345 INVITE > Allow: PRACK, SUBSCRIBE, NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, UPDATE, > INFO, REGISTER, OPTIONS, M > ESSAGE > Supported: replaces, 100rel > Proxy-Authorization: Digest username="17772646853", realm="callcentric.com", > nonce="08d3aba5f5a16fdc > ef8bccfa31014c34", uri="sip:**275*883975*[email protected]", > response="a4fa5b4a4ea6eb1ac3 > 763741f20380c1", algorithm=MD5 > Content-Type: application/sdp > Content-Length: 369 > > v=0 > o=DHD-Z560 3554409304 0 IN IP4 192.168.230.233 > s=sflphone > c=IN IP4 192.168.230.233 > t=0 0 > m=audio 47992 RTP/AVP 3 110 111 112 9 0 8 > a=rtpmap:3 GSM/8000 > a=rtpmap:110 speex/8000 > a=rtpmap:111 speex/16000 > a=rtpmap:112 speex/32000 > a=rtpmap:9 G722/8000 > a=rtpmap:0 PCMU/8000 > a=rtpmap:8 PCMA/8000 > a=sendrecv > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-15 > -------------------------------------------------------------------------------- > 23:55:04 Tx udp:69.140.220.18:5060 > SIP/2.0 100 Trying > v: SIP/2.0/UDP > 192.168.230.233:5060;rport=5060;branch=z9hG4bKPjc2a16e1f-d764-43f7-aca1-f481393bef72; > received=69.140.220.18 > f: <sip:[email protected]>;tag=69239813-9a39-40f1-aec9-e44fb0465560 > t: <sip:**275*883975*[email protected]> > i: faab11d4-a330-4095-9974-aa14d0d3b602 > CSeq: 345 INVITE > l: 0 > > -------------------------------------------------------------------------------- > 23:55:04 Tx udp:69.140.220.18:5060 > SIP/2.0 100 Trying > v: SIP/2.0/UDP > 192.168.230.233:5060;rport=5060;branch=z9hG4bKPjc2a16e1f-d764-43f7-aca1-f481393bef72; > received=69.140.220.18 > f: <sip:[email protected]>;tag=69239813-9a39-40f1-aec9-e44fb0465560 > t: <sip:**275*883975*[email protected]> > i: faab11d4-a330-4095-9974-aa14d0d3b602 > CSeq: 345 INVITE > Warning: 392 64.34.162.221:5060 "Noisy feedback tells: pid=4134 > req_src_ip=204.11.192.39 req_src_po > rt=5060 in_uri=sip:*883975*@sipbroker.com out_uri=sip:*883975*@sipbroker.com > via_cnt==2" > l: 0 > > -------------------------------------------------------------------------------- > 23:55:05 Tx udp:69.140.220.18:5060 > SIP/2.0 484 Address Incomplete > v: SIP/2.0/UDP > 192.168.230.233:5060;rport=5060;branch=z9hG4bKPjc2a16e1f-d764-43f7-aca1-f481393bef72; > received=69.140.220.18 > f: <sip:[email protected]>;tag=69239813-9a39-40f1-aec9-e44fb0465560 > t: <sip:**275*883975*[email protected]>;tag=as181b560e > i: faab11d4-a330-4095-9974-aa14d0d3b602 > CSeq: 345 INVITE > Supported: replaces, timer > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO > l: 0 > > The "484 Incomplete Address" simply indicates that the SIP URI > "**275*883975*[email protected]" is invalid. > > As mentioned previously, as this method is highly non-standard and not > supported, it does go beyond the scope of our support. > > With that said, there is not much more that we can suggest to attempt to get > this working. > > If you have any other questions, please let us know. Perhaps the above is more meaningful to someone here than it is to me and will help getting things working. Dave _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
