YMSL Posted January 12, 2009 Report Share Posted January 12, 2009 Runnig 3.1.2 on Windows Box - CallCenter licence Now that agent can log in and out I am trying to use a Key on our SAP962/SPA942 Agent phone to display status, either loged in or loged out just like a service flag will do. for service flag we are usign "fnc=sd+blf+cp;nme=Reception;sub=30@192.168.0.1;usr=30@192.168.0.1;vid=1" if service flag is "clear" Lamp is Green if service flag is "Set" lamp is Red I tried the same wuth agent presence but since the it is usign "*64/*65" I need 2 phone buttons and it is not working well. Any idea on how to create a beaviour or a function that will accomplish the same visual result If agent is logged "in" lamp will go Green If Agent is logges "out" lamp will go Red Looking at the XML file I can view agent status, but is is not very elegent! Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 12, 2009 Report Share Posted January 12, 2009 Runnig 3.1.2 on Windows Box - CallCenter licence Now that agent can log in and out I am trying to use a Key on our SAP962/SPA942 Agent phone to display status, either loged in or loged out just like a service flag will do. for service flag we are usign "fnc=sd+blf+cp;nme=Reception;sub=30@192.168.0.1;usr=30@192.168.0.1;vid=1" if service flag is "clear" Lamp is Green if service flag is "Set" lamp is Red I tried the same wuth agent presence but since the it is usign "*64/*65" I need 2 phone buttons and it is not working well. Any idea on how to create a beaviour or a function that will accomplish the same visual result If agent is logged "in" lamp will go Green If Agent is logges "out" lamp will go Red Looking at the XML file I can view agent status, but is is not very elegent! The code for the login and logout may be the same. If that is the case, then calling that code will toggle the state. Maybe that helps? Quote Link to comment Share on other sites More sharing options...
YMSL Posted January 12, 2009 Author Report Share Posted January 12, 2009 The code for the login and logout may be the same. If that is the case, then calling that code will toggle the state. Maybe that helps? This could have been the solution BUT, Web interface does not allow to have duplication code, If I try the web interface is telling me "Dupilcate" Can we change the feature code someplace else? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 13, 2009 Report Share Posted January 13, 2009 This could have been the solution BUT, Web interface does not allow to have duplication code, If I try the web interface is telling me "Dupilcate" Can we change the feature code someplace else? Ehhhh.... Okay, maybe temporarily turn Javascript off. Or you can also use a handcraftet URL like this: http://yourpbx/dom_feature_codes.htm?editd...gent_logout=*75. Quote Link to comment Share on other sites More sharing options...
YMSL Posted January 13, 2009 Author Report Share Posted January 13, 2009 Ehhhh.... Okay, maybe temporarily turn Javascript off. Or you can also use a handcraftet URL like this: http://yourpbx/dom_feature_codes.htm?editd...gent_logout=*75. This does the trick. Only one little down, Lamp is not changing color either if logedin or out any idea on where to look? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 14, 2009 Report Share Posted January 14, 2009 This does the trick. Only one little down, Lamp is not changing color either if logedin or out any idea on where to look? Hmm. Maybe you can post the XML documents that the PBX sends to the phone when the state changes (the body of the NOFIFY messages). Then we can see if the phone should believe that the resource is "active". Quote Link to comment Share on other sites More sharing options...
YMSL Posted January 14, 2009 Author Report Share Posted January 14, 2009 Hmm. Maybe you can post the XML documents that the PBX sends to the phone when the state changes (the body of the NOFIFY messages). Then we can see if the phone should believe that the resource is "active". Not a problem, what level of logs will do? certenally not "0" Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 14, 2009 Report Share Posted January 14, 2009 Not a problem, what level of logs will do? certenally not "0" You need to log the SIP packets, SUBSCRIBE/NOTIFY. They are usually logged on level 7, unless you monitor a specifc IP address. Quote Link to comment Share on other sites More sharing options...
YMSL Posted January 14, 2009 Author Report Share Posted January 14, 2009 You need to log the SIP packets, SUBSCRIBE/NOTIFY. They are usually logged on level 7, unless you monitor a specifc IP address. here it is: Log In [7] 2009/01/14 13:20:27: SIP Rx udp:10.0.1.1:44143: INVITE sip:*64@10.0.1.1 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-d5380752 From: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 To: "Agent Log" <sip:*64@10.0.1.1> Call-ID: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 101 INVITE Max-Forwards: 70 Contact: "Test User1" <sip:22@10.0.1.5:5060> Expires: 240 User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 385 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 46919 46919 IN IP4 10.0.1.5 s=- c=IN IP4 10.0.1.5 t=0 0 m=audio 61042 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [7] 2009/01/14 13:20:27: SIP Tx udp:10.0.1.1:44143: SIP/2.0 100 Trying v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-d5380752;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 i: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 101 INVITE l: 0 [7] 2009/01/14 13:20:27: SIP Tx udp:10.0.1.1:44143: SIP/2.0 401 Authentication Required v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-d5380752;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 i: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 101 INVITE User-Agent: pbxnsip-PBX/3.1.2.3120 WWW-Authenticate: Digest realm="10.0.1.1",nonce="8459ee06553585fc7eef947239f58021",domain="sip:*64@10.0.1.1",algorithm=MD5 l: 0 [7] 2009/01/14 13:20:27: SIP Rx udp:10.0.1.1:44143: ACK sip:*64@10.0.1.1 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-d5380752 From: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 To: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 Call-ID: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 101 ACK Max-Forwards: 70 Contact: "Test User1" <sip:22@10.0.1.5:5060> User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 0 [7] 2009/01/14 13:20:27: SIP Rx udp:10.0.1.1:44143: INVITE sip:*64@10.0.1.1 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-947ebfc2 From: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 To: "Agent Log" <sip:*64@10.0.1.1> Call-ID: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 102 INVITE Max-Forwards: 70 Authorization: Digest username="22",realm="10.0.1.1",nonce="8459ee06553585fc7eef947239f58021",uri="sip:*64@10.0.1.1",algorithm=MD5,response="193078f40553d959c5ff7278c0e479c7" Contact: "Test User1" <sip:22@10.0.1.5:5060> Expires: 240 User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 385 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 46919 46919 IN IP4 10.0.1.5 s=- c=IN IP4 10.0.1.5 t=0 0 m=audio 61042 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [7] 2009/01/14 13:20:27: Set packet length to 20 [6] 2009/01/14 13:20:27: Sending RTP for bd49bbbc-d8d3013a@10.0.1.5#45e65484b2 to 10.0.1.5:61042 [7] 2009/01/14 13:20:27: SIP Tx udp:10.0.1.1:44143: SIP/2.0 100 Trying v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-947ebfc2;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 i: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 102 INVITE l: 0 [5] 2009/01/14 13:20:27: Agent 22@192.168.0.1 logged in [7] 2009/01/14 13:20:27: Set packet length to 20 [7] 2009/01/14 13:20:27: SIP Tx udp:10.0.1.1:44143: SIP/2.0 200 Ok v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-947ebfc2;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 i: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 102 INVITE m: <sip:22@10.0.1.1:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.1.2.3120 c: application/sdp l: 300 v=0 o=- 992 992 IN IP4 10.0.1.1 s=- c=IN IP4 10.0.1.1 t=0 0 m=audio 57988 RTP/AVP 0 8 18 2 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:2 g726-32/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv [7] 2009/01/14 13:20:27: Last message repeated 2 times [7] 2009/01/14 13:20:27: SIP Rx udp:10.0.1.1:44143: ACK sip:22@10.0.1.1:5060 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-27875cf1 From: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 To: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 Call-ID: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 102 ACK Max-Forwards: 70 Authorization: Digest username="22",realm="10.0.1.1",nonce="8459ee06553585fc7eef947239f58021",uri="sip:*64@10.0.1.1",algorithm=MD5,response="193078f40553d959c5ff7278c0e479c7" Contact: "Test User1" <sip:22@10.0.1.5:5060> User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 0 [7] 2009/01/14 13:20:27: Last message repeated 2 times [6] 2009/01/14 13:20:27: Sending RTP for bd49bbbc-d8d3013a@10.0.1.5#45e65484b2 to 10.0.1.1:33302 [7] 2009/01/14 13:20:27: Receiving DTMF on codec 101 [7] 2009/01/14 13:20:29: SIP Tx udp:10.0.1.1:44143: BYE sip:22@10.0.1.5:5060 SIP/2.0 v: SIP/2.0/UDP 10.0.1.1:5060;branch=z9hG4bK-3b03a83bf01942c3e4d9057aa69b0539;rport f: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 t: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 i: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 1392 BYE Max-Forwards: 70 m: <sip:22@10.0.1.1:5060> RTP-RxStat: Dur=1,Pkt=68,Oct=11696,Underun=0 RTP-TxStat: Dur=1,Pkt=65,Oct=11180 l: 0 [7] 2009/01/14 13:20:29: SIP Rx udp:10.0.1.1:44143: SIP/2.0 200 OK t: "Test User1" <sip:22@10.0.1.1>;tag=d94749d42b590a02o0 f: "Agent Log" <sip:*64@10.0.1.1>;tag=45e65484b2 i: bd49bbbc-d8d3013a@10.0.1.5 CSeq: 1392 BYE v: SIP/2.0/UDP 10.0.1.1:5060;branch=z9hG4bK-3b03a83bf01942c3e4d9057aa69b0539 Server: Linksys/SPA962-6.1.3(a) Content-Length: 0 [7] 2009/01/14 13:20:29: Call bd49bbbc-d8d3013a@10.0.1.5#45e65484b2: Clear last request [5] 2009/01/14 13:20:29: BYE Response: Terminate bd49bbbc-d8d3013a@10.0.1.5 Log Out [7] 2009/01/14 13:19:26: SIP Rx udp:10.0.1.1:44143: INVITE sip:*64@10.0.1.1 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-a0743bf1 From: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 To: "Agent Log" <sip:*64@10.0.1.1> Call-ID: db814912-b65dcc15@10.0.1.5 CSeq: 101 INVITE Max-Forwards: 70 Contact: "Test User1" <sip:22@10.0.1.5:5060> Expires: 240 User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 385 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 40832 40832 IN IP4 10.0.1.5 s=- c=IN IP4 10.0.1.5 t=0 0 m=audio 61040 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [7] 2009/01/14 13:19:26: SIP Tx udp:10.0.1.1:44143: SIP/2.0 100 Trying v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-a0743bf1;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 i: db814912-b65dcc15@10.0.1.5 CSeq: 101 INVITE l: 0 [7] 2009/01/14 13:19:26: SIP Tx udp:10.0.1.1:44143: SIP/2.0 401 Authentication Required v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-a0743bf1;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 i: db814912-b65dcc15@10.0.1.5 CSeq: 101 INVITE User-Agent: pbxnsip-PBX/3.1.2.3120 WWW-Authenticate: Digest realm="10.0.1.1",nonce="27dcfb81c5b5fac696203b03e441ac0d",domain="sip:*64@10.0.1.1",algorithm=MD5 l: 0 [7] 2009/01/14 13:19:26: SIP Rx udp:10.0.1.1:44143: ACK sip:*64@10.0.1.1 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-a0743bf1 From: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 To: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 Call-ID: db814912-b65dcc15@10.0.1.5 CSeq: 101 ACK Max-Forwards: 70 Contact: "Test User1" <sip:22@10.0.1.5:5060> User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 0 [7] 2009/01/14 13:19:26: SIP Rx udp:10.0.1.1:44143: INVITE sip:*64@10.0.1.1 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-383ae20d From: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 To: "Agent Log" <sip:*64@10.0.1.1> Call-ID: db814912-b65dcc15@10.0.1.5 CSeq: 102 INVITE Max-Forwards: 70 Authorization: Digest username="22",realm="10.0.1.1",nonce="27dcfb81c5b5fac696203b03e441ac0d",uri="sip:*64@10.0.1.1",algorithm=MD5,response="4e5fdc5b0226f2c4977b5d838242a66a" Contact: "Test User1" <sip:22@10.0.1.5:5060> Expires: 240 User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 385 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: replaces Content-Type: application/sdp v=0 o=- 40832 40832 IN IP4 10.0.1.5 s=- c=IN IP4 10.0.1.5 t=0 0 m=audio 61040 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [7] 2009/01/14 13:19:26: Set packet length to 20 [6] 2009/01/14 13:19:26: Sending RTP for db814912-b65dcc15@10.0.1.5#e480ae1024 to 10.0.1.5:61040 [7] 2009/01/14 13:19:26: SIP Tx udp:10.0.1.1:44143: SIP/2.0 100 Trying v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-383ae20d;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 i: db814912-b65dcc15@10.0.1.5 CSeq: 102 INVITE l: 0 [5] 2009/01/14 13:19:26: Agent 22@192.168.0.1 logged out [7] 2009/01/14 13:19:26: Set packet length to 20 [7] 2009/01/14 13:19:26: SIP Tx udp:10.0.1.1:44143: SIP/2.0 200 Ok v: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-383ae20d;rport=44143;received=10.0.1.1 f: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 t: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 i: db814912-b65dcc15@10.0.1.5 CSeq: 102 INVITE m: <sip:22@10.0.1.1:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.1.2.3120 c: application/sdp l: 304 v=0 o=- 22278 22278 IN IP4 10.0.1.1 s=- c=IN IP4 10.0.1.1 t=0 0 m=audio 56528 RTP/AVP 0 8 18 2 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:2 g726-32/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv [7] 2009/01/14 13:19:26: Last message repeated 2 times [7] 2009/01/14 13:19:26: SIP Rx udp:10.0.1.1:44143: ACK sip:22@10.0.1.1:5060 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-d46f0f5b From: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 To: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 Call-ID: db814912-b65dcc15@10.0.1.5 CSeq: 102 ACK Max-Forwards: 70 Authorization: Digest username="22",realm="10.0.1.1",nonce="27dcfb81c5b5fac696203b03e441ac0d",uri="sip:*64@10.0.1.1",algorithm=MD5,response="4e5fdc5b0226f2c4977b5d838242a66a" Contact: "Test User1" <sip:22@10.0.1.5:5060> User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 0 [6] 2009/01/14 13:19:26: Sending RTP for db814912-b65dcc15@10.0.1.5#e480ae1024 to 10.0.1.1:44917 [7] 2009/01/14 13:19:26: Receiving DTMF on codec 101 [7] 2009/01/14 13:19:26: SIP Rx udp:10.0.1.1:44143: ACK sip:22@10.0.1.1:5060 SIP/2.0 Via: SIP/2.0/UDP 10.0.1.5:5060;branch=z9hG4bK-d46f0f5b From: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 To: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 Call-ID: db814912-b65dcc15@10.0.1.5 CSeq: 102 ACK Max-Forwards: 70 Authorization: Digest username="22",realm="10.0.1.1",nonce="27dcfb81c5b5fac696203b03e441ac0d",uri="sip:*64@10.0.1.1",algorithm=MD5,response="4e5fdc5b0226f2c4977b5d838242a66a" Contact: "Test User1" <sip:22@10.0.1.5:5060> User-Agent: Linksys/SPA962-6.1.3(a) Content-Length: 0 [7] 2009/01/14 13:19:28: SIP Tx udp:10.0.1.1:44143: BYE sip:22@10.0.1.5:5060 SIP/2.0 v: SIP/2.0/UDP 10.0.1.1:5060;branch=z9hG4bK-e7bfb34b595b3c02257b7de0abe51546;rport f: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 t: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 i: db814912-b65dcc15@10.0.1.5 CSeq: 26363 BYE Max-Forwards: 70 m: <sip:22@10.0.1.1:5060> RTP-RxStat: Dur=1,Pkt=63,Oct=10836,Underun=0 RTP-TxStat: Dur=1,Pkt=64,Oct=11008 l: 0 [7] 2009/01/14 13:19:28: SIP Rx udp:10.0.1.1:44143: SIP/2.0 200 OK t: "Test User1" <sip:22@10.0.1.1>;tag=92f5eceeaeb019e9o0 f: "Agent Log" <sip:*64@10.0.1.1>;tag=e480ae1024 i: db814912-b65dcc15@10.0.1.5 CSeq: 26363 BYE v: SIP/2.0/UDP 10.0.1.1:5060;branch=z9hG4bK-e7bfb34b595b3c02257b7de0abe51546 Server: Linksys/SPA962-6.1.3(a) Content-Length: 0 [7] 2009/01/14 13:19:28: Call db814912-b65dcc15@10.0.1.5#e480ae1024: Clear last request [5] 2009/01/14 13:19:28: BYE Response: Terminate db814912-b65dcc15@10.0.1.5 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 14, 2009 Report Share Posted January 14, 2009 Well, I don't see a lot of traffic, but no NOTIFY... Either that is the problem or the logging wasn't turned on the that. It would be good to see also the SUBSCRIBE for the resource. Quote Link to comment Share on other sites More sharing options...
YMSL Posted January 15, 2009 Author Report Share Posted January 15, 2009 Well, I don't see a lot of traffic, but no NOTIFY... Either that is the problem or the logging wasn't turned on the that. It would be good to see also the SUBSCRIBE for the resource. I have Logs settings all "on" (everything) Please see the attached file for logs details Logs.txt Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.