Currently inbound calls are coming in from our ITSP, hitting our sipbridge, but then from the bridge they are not routing to our core server . The exact 'problem' Invite is shown below:
Time: 2010-07-23T20:09:21.080716Z Frame: 90 /tmp/trace.EOm21552/_.sipXproxy.trace.xml:6838 /tmp/trace.EOm21552/_.sipXproxy.trace.xml:6841 /tmp/trace.EOm21552/_.sipXproxy.trace.xml:6851 /tmp/trace.EOm21552/_.sipXproxy.trace.xml:6855 Source: nem-ma-sipbrg2.nem.ne.nrt-SipXProxy Dest: 167.182.58.214:5060 INVITE sip:[email protected] SIP/2.0 Record-Route: <sip:172.16.53.53:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EMzQ4ODkwNDU1OS00NT QzNjA%60.900_ntap%2Aid%7EMjEyNzUtMA%60%60%21dc5a97cb93c30ffb879d481bcee5c52d > Max-Forwards: 20 Session-Expires: 3600;refresher=uac Supported: timer, 100rel To: <sip:[email protected]> From: "TALBOT PETER " <sip:[email protected]>;tag=3488904559-454360 P-Asserted-Identity: "TALBOT PETER "<sip:[email protected]:5060> Call-Id: [email protected] Cseq: 1 INVITE Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE Via: SIP/2.0/UDP 172.16.53.53;branch=z9hG4bK-XX-0109hrzSMD1M8O8ikx2_9YL8gw Via: SIP/2.0/UDP 72.8.55.29:5060;branch=z9hG4bK61eef155c5a9b65b2267ceee86a7727b;id=21275-0 Contact: <sip:[email protected]:5060;x-sipX-nonat> Expires: 180 Call-Info: <sip:72.8.55.29>;method="NOTIFY;Event=telephone-event;Duration=1000" Allow-Events: call-info Allow-Events: presence Allow-Events: line-seize Allow-Events: dialog Allow-Events: refer Allow-Events: message-summary Content-Type: application/sdp Content-Length: 244 Date: Fri, 23 Jul 2010 20:09:19 GMT X-Sipx-Handled: X172.16.53.53-167.182.58.214 v=0 o=nextone-msx-1 15504610 15504610 IN IP4 72.8.55.29 s=sip call c=IN IP4 72.8.55.251 t=0 0 m=audio 30248 RTP/AVP 0 101 c=IN IP4 172.16.53.53 a=rtpmap:101 telephone-event/8000 a=ptime:20 a=x-sipx-ntap:X172.16.53.53-167.182.58.214;0 167.182.58.214 is the external address of 172.16.53.53 (sipbbrg2). We do have the 167.182.58 subnet listed as a possible intranet, and this brg server is separate (sitting on a dmz) from our core primary server. Peter Talbot "The information in this electronic mail message is the sender's confidential business and may be legally privileged. It is intended solely for the addressee(s). Access to this internet electronic mail message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful." "The sender believes that this E-mail and any attachments were free of any virus, worm, Trojan horse, and/or malicious code when sent. This message and its attachments could have been infected during transmission. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective and remedial action about viruses and other defects. The sender's employer is not liable for any loss or damage arising in any way from this message or its attachments." [v1.0.07.109]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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/
