| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
Thanks Scott, Sort of guessed it and have configured the IP address in dns.nslookup works on all domains. But still the SIP BYE is not sent out.
RegardsOn Wed, Jan 15, 2014 at 12:15 AM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
Looks like the stack cannot resolve the Contact address from the INIVITE:sip:mavodi-0-7e-8-5-ffffffff-@tas.vz.mavenir.lab:5060;transport=udp
since there is a port number on the URI, your DNS server would need to be able to resolve a host (A) record for: tas.vz.mavenir.labScottOn Tue, Jan 14, 2014 at 1:36 PM, Lei Park <leipark77@xxxxxxxxx> wrote:Thanks Scott for the reply.It could take some time to get the STACK level logs. However I have the logs printed DUM callbacks in my application.On DUM callbacks when I print SipMessage for incoming INVITE, 180, 200 and outgoing BYE. Route in BYE is present and its same as Record-Route in the original INVITE.Logs collected on DUM callbacks.One question: How does the sip stack determine the IP address on outgoing SIP message?::onOffer callbackINVITE sip:+1111111111@xxxxxxxxxxxxxx;transport=tcp;lr;cause=408 SIP/2.0^MVia: SIP/2.0/UDP icscf.vz.mavenir.lab:5060;rport=5060;branch=z9hG4bKmavodi-0-52-2b-3-e0ff00ff-6260b662f78b848;received=10.1.62.109^MVia: SIP/2.0/TCP scscf.vz.mavenir.lab:5070;branch=z9hG4bKmavodi-0-4c-6e-4-e0f10001-6fef0fc91dceabb2^MVia: SIP/2.0/UDP tas.vz.mavenir.lab:5060;received=10.1.62.102;rport=5060;branch=z9hG4bKmavodi-0-7e-8-5-ffffffff-676580728-16416^MMax-Forwards: 68^MRoute: <sip:10.1.62.104:5060;lr>^MRecord-Route: <sip:mavodi-0-4c-6e-4-1f0001-@xxxxxxxxxxxxxxxxxxxx:5070;lr>^MContact: <sip:mavodi-0-7e-8-5-ffffffff-@xxxxxxxxxxxxxxxxxx:5060;transport=udp>^MTo: sip:9910000705@xxxxxxxxxxxxxx^MFrom: sip:9910000704@xxxxxxxxxxxxxx;tag=mavodi-0-7e-8-5-ffffffff-_0050568E9010-4020-33ed2700-1b-52d62632-35d0b^MCall-ID: 0050568E9010-4020-33ed2700-1a-52d62632-35a90^MCSeq: 1 INVITE^MAllow: INVITE, BYE, CANCEL, ACK, SUBSCRIBE, NOTIFY, PUBLISH, MESSAGE, REFER, REGISTER, UPDATE^MContent-Type: application/sdp^MSupported: replaces, norefersub, 100rel^MUser-Agent: Vippie/4.5.9 (Android 4.0.3) Mavenir UAG/v2.1 PCSCF/v2.1-13042703o^MRequest-Disposition: no-fork, no-fork, no-fork^MP-Asserted-Identity: sip:9910000704@xxxxxxxxxxxxxx^MAccept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"^MHistory-Info: <sip:9910000705@xxxxxxxxxxxxxx;transport=tcp;lr>;index=1^MHistory-Info: <sip:+1111111111@xxxxxxxxxxxxxx;cause=408;lr;transport=tcp>;index=1.1^MP-Charging-Vector: icid-value=0.274.92-1389766170.719;orig-ioi=31333;icid-generated-at=10.1.62.108;orig-ioi=Type3Orig^MP-Charging-Function-Addresses: ccf=192.168.1.1;ecf=192.168.1.1;ccf=192.168.1.1;ecf=192.168.1.1^MContent-Length: 467^M::onReadyToSend() callbackSIP/2.0 180 Ringing^MVia: SIP/2.0/UDP icscf.vz.mavenir.lab:5060;rport=5060;branch=z9hG4bKmavodi-0-52-2b-3-e0ff00ff-6260b662f78b848;received=10.1.62.109^MVia: SIP/2.0/TCP scscf.vz.mavenir.lab:5070;branch=z9hG4bKmavodi-0-4c-6e-4-e0f10001-6fef0fc91dceabb2^MVia: SIP/2.0/UDP tas.vz.mavenir.lab:5060;received=10.1.62.102;rport=5060;branch=z9hG4bKmavodi-0-7e-8-5-ffffffff-676580728-16416^MRecord-Route: <sip:mavodi-0-4c-6e-4-1f0001-@xxxxxxxxxxxxxxxxxxxx:5070;lr>^MContact: <sip:+1111111111>^MTo: <sip:9910000705@xxxxxxxxxxxxxx>;tag=02ce6810^MFrom: sip:9910000704@xxxxxxxxxxxxxx;tag=mavodi-0-7e-8-5-ffffffff-_0050568E9010-4020-33ed2700-1b-52d62632-35d0b^MCall-ID: 0050568E9010-4020-33ed2700-1a-52d62632-35a90^MCSeq: 1 INVITE^MContent-Length: 0^M::onReadyToSend() callbackSIP/2.0 200 OK^MVia: SIP/2.0/UDP icscf.vz.mavenir.lab:5060;rport=5060;branch=z9hG4bKmavodi-0-52-2b-3-e0ff00ff-6260b662f78b848;received=10.1.62.109^MVia: SIP/2.0/TCP scscf.vz.mavenir.lab:5070;branch=z9hG4bKmavodi-0-4c-6e-4-e0f10001-6fef0fc91dceabb2^MVia: SIP/2.0/UDP tas.vz.mavenir.lab:5060;received=10.1.62.102;rport=5060;branch=z9hG4bKmavodi-0-7e-8-5-ffffffff-676580728-16416^MRecord-Route: <sip:mavodi-0-4c-6e-4-1f0001-@xxxxxxxxxxxxxxxxxxxx:5070;lr>^MContact: <sip:+1111111111>^MTo: <sip:9910000705@xxxxxxxxxxxxxx>;tag=02ce6810^MFrom: sip:9910000704@xxxxxxxxxxxxxx;tag=mavodi-0-7e-8-5-ffffffff-_0050568E9010-4020-33ed2700-1b-52d62632-35d0b^MCall-ID: 0050568E9010-4020-33ed2700-1a-52d62632-35a90^MCSeq: 1 INVITE^MAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, INVITE, REGISTER, ACK, CANCEL, BYE, INFO^MContent-Type: application/sdp^MContent-Length: 324^M::onReadyToSend() callbacksip:mavodi-0-7e-8-5-ffffffff-@xxxxxxxxxxxxxxxxxx:5060;transport=udp SIP/2.0^MVia: SIP/2.0/ ;branch=z9hG4bK-524287-1---2f85c73b10c02677;rport^MMax-Forwards: 70^MRoute: <sip:mavodi-0-4c-6e-4-1f0001-@xxxxxxxxxxxxxxxxxxxx:5070;lr>^MContact: <sip:+1111111111>^MTo: sip:9910000704@xxxxxxxxxxxxxx;tag=mavodi-0-7e-8-5-ffffffff-_0050568E9010-4020-33ed2700-1b-52d62632-35d0b^MFrom: <sip:9910000705@xxxxxxxxxxxxxx>;tag=02ce6810^MCall-ID: 0050568E9010-4020-33ed2700-1a-52d62632-35a90^MCSeq: 2 BYE^MReason: SIP;text=User Hung Up^MContent-Length: 0^MThanks in advance.On Mon, Jan 13, 2014 at 8:41 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
Perhaps there is no route to the target (remote Contact). Can you post a DEBUG or STACK level log?ScottOn Mon, Jan 13, 2014 at 3:48 AM, Lei Park <leipark77@xxxxxxxxx> wrote:
_______________________________________________Facing an issue where BYE is not sent out.An incoming session is established completely. (resiprocate stack has received an incoming INVITE, and responded with 100, 180 and 200, and also has received ACK for 200).After some time I hangup the session using resip::InviteSessionHandle->end(InviteSession::UserHangup); My application also receives the callbacks onReadyToSend() for BYE and onTerminated() with reasonCode = 3, which is as expected.But the wireshark dump on this machine does not show any SIP BYE being sent out and even the remote end does not receive any SIP BYE.Can any one help out please?ThanksPark
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/