CobaltFlux Posted May 26, 2008 Report Share Posted May 26, 2008 Using the PSTN FXO lines it seems that our CS410 only picks up the Caller ID sometimes. I have been testing it with my cell phone (trying to get the special autoattendant to pick up). I had this issue with 2913 and now I just updated to 2914. It seems that after a reboot it will pick up the Caller ID at least once. Could this be a problem with my analog lines? Or is there some setting I am missing? I apologize. I'm not trying to be a nusance here, just trying to get the most out of the system. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 26, 2008 Report Share Posted May 26, 2008 Using the PSTN FXO lines it seems that our CS410 only picks up the Caller ID sometimes. I have been testing it with my cell phone (trying to get the special autoattendant to pick up). I had this issue with 2913 and now I just updated to 2914. It seems that after a reboot it will pick up the Caller ID at least once. How long is the line? What is the carrier? "Sometimes" sounds like a analog problem. Also, set the log level high and turn PSTN logging on (after that you need another reboot). Then you may see the messages about the Caller-ID in the log. Quote Link to comment Share on other sites More sharing options...
CobaltFlux Posted May 26, 2008 Author Report Share Posted May 26, 2008 We are the 4th unit in a row of buildings and the junction to the phone company is in the first unit. There is probably about 100 feet from the appliance to junction in our unit then another 200-300 feet to a second junction box and finally another 100-200 feet of cable to the junction where it connects to the phone company's cable. So, I wouldn't be surprised if we have some poor wiring. We had issues getting our T1 line set up and we have had problems with our DSL line and some coss-talking with an unknown line (not one of ours) in the past. Our phone company is Qwest. I set the log to high and I'm not seeing anything about the Caller-ID (unless it receives the caller-ID). I have turned off logging on everything but IVR events, trunk events, and PSTN Gateway events. Here is what the log looks like when the Caller-ID works: [3] 2008/05/26 12:43:32: PSTN: Channel 0 going to RING [5] 2008/05/26 12:43:35: PSTN: eVAPI_CALLER_ID_DETECTED_EVENT [5] 2008/05/26 12:43:35: PSTN: Received on 0: DATE:0526, TIME: 1243 [5] 2008/05/26 12:43:35: PSTN: Received on 0: Caller-ID 801xxxxx52 [5] 2008/05/26 12:43:35: PSTN: Received on 0: Name COBALT FLUX INC [5] 2008/05/26 12:43:35: Identify trunk (IP address/port and domain match) 1 [5] 2008/05/26 12:43:35: PSTN: Response code: 100 [7] 2008/05/26 12:43:35: Received call from cell phone 801xxxxx52 [5] 2008/05/26 12:43:35: PSTN: Response code: 200 [5] 2008/05/26 12:43:35: PSTN: RTP destination=100007f [5] 2008/05/26 12:43:35: PSTN: RTP destination=56052 [5] 2008/05/26 12:43:35: PSTN: RTP OOB codec=101 [6] 2008/05/26 12:43:35: PSTN: Start call on 0 [5] 2008/05/26 12:43:35: PSTN: Channel 0 goes offhook [3] 2008/05/26 12:43:35: PSTN: Channel 0 going to TALKING [5] 2008/05/26 12:43:35: PSTN: Country Code set to 64 [5] 2008/05/26 12:43:35: PSTN: Tone Detection set to 0 [5] 2008/05/26 12:43:35: PSTN: Response code: 200 [5] 2008/05/26 12:43:40: PSTN: Received LoopInterrupt (remote hung up) signal on channel 0 [3] 2008/05/26 12:43:40: PSTN: Channel 0: Hangup [5] 2008/05/26 12:43:40: PSTN: Channel 0 goes onhook [5] 2008/05/26 12:43:40: PSTN: enable_callerid 0 [3] 2008/05/26 12:43:40: PSTN: Channel 0 going to GO_ONHOOK [5] 2008/05/26 12:43:40: PSTN: Response code: 200 [3] 2008/05/26 12:43:41: PSTN: Channel 0 going to IDLE no caller-id: [3] 2008/05/26 12:33:37: PSTN: Channel 0 going to RING [3] 2008/05/26 12:33:42: PSTN: Channel 0 going to NO_RING [3] 2008/05/26 12:33:43: PSTN: Channel 0 going to RING [5] 2008/05/26 12:33:43: Identify trunk (IP address/port and domain match) 1 [5] 2008/05/26 12:33:43: PSTN: Response code: 100 [7] 2008/05/26 12:33:43: Attendant: Goto night service 701 [5] 2008/05/26 12:33:43: PSTN: Response code: 200 [5] 2008/05/26 12:33:43: PSTN: RTP destination=100007f [5] 2008/05/26 12:33:43: PSTN: RTP destination=50492 [5] 2008/05/26 12:33:43: PSTN: RTP OOB codec=101 [6] 2008/05/26 12:33:43: PSTN: Start call on 0 [5] 2008/05/26 12:33:43: PSTN: Channel 0 goes offhook [3] 2008/05/26 12:33:43: PSTN: Channel 0 going to TALKING [5] 2008/05/26 12:33:43: PSTN: Country Code set to 64 [5] 2008/05/26 12:33:43: PSTN: Tone Detection set to 0 [5] 2008/05/26 12:33:43: PSTN: Response code: 200 [5] 2008/05/26 12:33:53: PSTN: Received LoopInterrupt (remote hung up) signal on channel 0 [3] 2008/05/26 12:33:53: PSTN: Channel 0: Hangup [5] 2008/05/26 12:33:53: PSTN: Channel 0 goes onhook [5] 2008/05/26 12:33:53: PSTN: enable_callerid 0 [3] 2008/05/26 12:33:53: PSTN: Channel 0 going to GO_ONHOOK [5] 2008/05/26 12:33:53: PSTN: Response code: 200 [3] 2008/05/26 12:33:54: PSTN: Channel 0 going to IDLE If it is a cable related issue then it will take some time to fix. I can replace the cable inside our building but I will have to ask the landlord about the rest of it. In the mean time, is there a way for a caller to get Direct Inward Access like that provided when it recognizes your cell phone number? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 26, 2008 Report Share Posted May 26, 2008 We are the 4th unit in a row of buildings and the junction to the phone company is in the first unit. There is probably about 100 feet from the appliance to junction in our unit then another 200-300 feet to a second junction box and finally another 100-200 feet of cable to the junction where it connects to the phone company's cable. So, I wouldn't be surprised if we have some poor wiring. We had issues getting our T1 line set up and we have had problems with our DSL line and some coss-talking with an unknown line (not one of ours) in the past. Hmm. Before changing the cable, maybe it is worth to play with the input gain and/or get a FXO signal booster. Maybe there is also a simple way of getting the cables measured out, the good news about FXO is that it is stoneage technology and there is so much stuff out there for this. If it is a cable related issue then it will take some time to fix. I can replace the cable inside our building but I will have to ask the landlord about the rest of it. In the mean time, is there a way for a caller to get Direct Inward Access like that provided when it recognizes your cell phone number? Well, those features rely on the Caller-ID detection... The only thing that you can do is setting up a "calling card" account and dial into it (maybe through the AA), then enter the extension number, PIN and then you can place outbound calls from there. Quote Link to comment Share on other sites More sharing options...
CobaltFlux Posted May 28, 2008 Author Report Share Posted May 28, 2008 I have tried playing with the input gains to no avail. I have yet to buy a signal booster. However, while I was playing with the input gains, I noticed that everytime I restarted the system the Caller-ID worked for the first call. After that, it seems that almost every call is missing the Caller-ID. Do you think there may be some other issue going on? I was having some issues with cross-talk that I cleared up almost completely by rerunning a couple of cables but it didn't seem to clear up the Caller-ID problem. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 28, 2008 Report Share Posted May 28, 2008 However, while I was playing with the input gains, I noticed that everytime I restarted the system the Caller-ID worked for the first call. After that, it seems that almost every call is missing the Caller-ID. Do you think there may be some other issue going on? The only thing that rings a bell is that the polarity change detection is off in the beginning (by default). This is because the gateway wants to "learn" if it is available or not. Maybe on next reboot try to turn it off and see if that makes a difference. Quote Link to comment Share on other sites More sharing options...
CobaltFlux Posted July 2, 2008 Author Report Share Posted July 2, 2008 I tried the things you suggested except for the FXO signal booster (which I'm not sure exactly what kind of device you mean) and I still do not have Caller ID. I put off trying to fix it for a while as it isn't completely necessary. However, I have some time now and would like to see if we cam figure something out. In my tests lately, I can only get the caller id to work after boot and not again. However, I noticed in the PSTN logging that there is a line about Caller id. After every call hangs up the line "PSTN: enable_callerid 0" comes up. Is this disabling the caller id after every call? If so, it would explain why it works the first time if the default of callerid is enabled. Any ideas? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 2, 2008 Report Share Posted July 2, 2008 I tried the things you suggested except for the FXO signal booster (which I'm not sure exactly what kind of device you mean) and I still do not have Caller ID. I put off trying to fix it for a while as it isn't completely necessary. However, I have some time now and would like to see if we cam figure something out. In my tests lately, I can only get the caller id to work after boot and not again. However, I noticed in the PSTN logging that there is a line about Caller id. After every call hangs up the line "PSTN: enable_callerid 0" comes up. Is this disabling the caller id after every call? If so, it would explain why it works the first time if the default of callerid is enabled. No, that log message just says that it (re-)enabled caller-ID detection. Maybe you can try to incrase the log level? Please restart the box after that, so that the FXO subsystem can pick the change up. Also, if possible use version 2933. That seems (so far) to be the best regarding caller-ID. Quote Link to comment Share on other sites More sharing options...
kshan22 Posted July 8, 2008 Report Share Posted July 8, 2008 Hi, I setup my CS410 and everything is running smoothly accept the caller id. I do not seem to be able to get caller-id whenever I received inbound calls from the PSTN. So I am not able to know who is calling me or who left me a voicemail. I tested all the 4 lines that I have by plugging it into an analog phone and calling it from my cellphone. I was able to see the caller-id of my cellphone. This mean that the pstn carrier is sending the caller-id correctly. I then plugged into the CS410 and call into FXOs but do not see the caller id but keep getting anonymous. I am currently using the latest version of the software already. I think that caller-id has been pass to pbxnsip but it is not picking up. Do I need to enable something or there are some configuration that I should do. I have been working on this for days and do not seem to have a clue. I have attached my log file. Will be glad if there are some assistance. ----Logfile----- 9] 2008/01/01 09:20:09: Last message repeated 18 times [9] 2008/01/01 09:20:09: Resolve 1030: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:20:09: Resolve 1030: a udp 192.168.1.67 2051 [9] 2008/01/01 09:20:09: Resolve 1030: udp 192.168.1.67 2051 [9] 2008/01/01 09:20:09: Resolve 1031: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:20:09: Resolve 1031: a udp 192.168.1.66 5060 [9] 2008/01/01 09:20:09: Resolve 1031: udp 192.168.1.66 5060 [7] 2008/01/01 09:20:21: SIP Rx udp:127.0.0.1:5062: INVITE sip:65474227@localhost;user=phone SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5062 From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1189641421 To: <sip:65474227@localhost;user=phone> Call-ID: ab2b36c2@fxo Contact: <sip:127.0.0.1:5062> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 137 v=0 o=root 0 0 IN IP4 1.1.1.2 s=- c=IN IP4 1.1.1.2 t=0 0 m=audio 2052 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=ptime:20 [7] 2008/01/01 09:20:21: UDP: Opening socket on port 50110 [7] 2008/01/01 09:20:21: UDP: Opening socket on port 50111 [5] 2008/01/01 09:20:21: Identify trunk (IP address/port and domain match) 1 [9] 2008/01/01 09:20:21: Resolve 1032: aaaa udp 127.0.0.1 5062 [9] 2008/01/01 09:20:21: Resolve 1032: a udp 127.0.0.1 5062 [9] 2008/01/01 09:20:21: Resolve 1032: udp 127.0.0.1 5062 [7] 2008/01/01 09:20:21: SIP Tx udp:127.0.0.1:5062: SIP/2.0 100 Trying Via: SIP/2.0/UDP 127.0.0.1:5062 From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1189641421 To: <sip:65474227@localhost;user=phone>;tag=ba1adf3fc3 Call-ID: ab2b36c2@fxo CSeq: 1 INVITE Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 8, 2008 Report Share Posted July 8, 2008 Any chance to get PSTN logging? Hint: You need to reboot the device to get them after enabling them in the web interface... Quote Link to comment Share on other sites More sharing options...
kshan22 Posted July 8, 2008 Report Share Posted July 8, 2008 Any chance to get PSTN logging? Hint: You need to reboot the device to get them after enabling them in the web interface... Sure, I will get it and post it here tomorrow. Thanks for the reply. kshan22 Quote Link to comment Share on other sites More sharing options...
kshan22 Posted July 9, 2008 Report Share Posted July 9, 2008 Hi, I activated the PSTN logging in under the system -> logging -> Log PSTN Gateway events: YES. save it and then clear the old log. Then I power off and on the CS410. Below is what I got. Am I doing the right thing and is this what is required? -Logfile- 9] 2008/01/01 09:34:20: Resolve 947: udp 192.168.1.67 2051 [9] 2008/01/01 09:34:23: Resolve 948: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:34:23: Resolve 948: a udp 192.168.1.66 5060 [9] 2008/01/01 09:34:23: Resolve 948: udp 192.168.1.66 5060 [9] 2008/01/01 09:34:35: Resolve 949: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:34:35: Resolve 949: a udp 192.168.1.67 2051 [9] 2008/01/01 09:34:35: Resolve 949: udp 192.168.1.67 2051 [7] 2008/01/01 09:34:38: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-6fubf4krsr01;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3010 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:34:38: Resolve 950: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:34:38: Resolve 950: a udp 192.168.1.67 2051 [9] 2008/01/01 09:34:38: Resolve 950: udp 192.168.1.67 2051 [7] 2008/01/01 09:34:38: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-6fubf4krsr01;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3010 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 32 Content-Length: 0 [9] 2008/01/01 09:34:38: Resolve 951: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:34:38: Resolve 951: a udp 192.168.1.66 5060 [9] 2008/01/01 09:34:38: Resolve 951: udp 192.168.1.66 5060 [9] 2008/01/01 09:34:51: Resolve 952: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:34:51: Resolve 952: a udp 192.168.1.67 2051 [9] 2008/01/01 09:34:51: Resolve 952: udp 192.168.1.67 2051 [9] 2008/01/01 09:34:53: Resolve 953: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:34:53: Resolve 953: a udp 192.168.1.66 5060 [9] 2008/01/01 09:34:53: Resolve 953: udp 192.168.1.66 5060 [9] 2008/01/01 09:35:06: Resolve 954: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:35:06: Resolve 954: a udp 192.168.1.67 2051 [9] 2008/01/01 09:35:06: Resolve 954: udp 192.168.1.67 2051 [9] 2008/01/01 09:35:08: Resolve 955: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:35:08: Resolve 955: a udp 192.168.1.66 5060 [9] 2008/01/01 09:35:08: Resolve 955: udp 192.168.1.66 5060 [7] 2008/01/01 09:35:08: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-0fyrroxr6lqk;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3011 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:35:08: Resolve 956: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:35:08: Resolve 956: a udp 192.168.1.67 2051 [9] 2008/01/01 09:35:08: Resolve 956: udp 192.168.1.67 2051 [7] 2008/01/01 09:35:08: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-0fyrroxr6lqk;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3011 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 32 Content-Length: 0 [9] 2008/01/01 09:35:21: Resolve 957: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:35:21: Resolve 957: a udp 192.168.1.67 2051 [9] 2008/01/01 09:35:21: Resolve 957: udp 192.168.1.67 2051 [9] 2008/01/01 09:35:23: Resolve 958: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:35:23: Resolve 958: a udp 192.168.1.66 5060 [9] 2008/01/01 09:35:23: Resolve 958: udp 192.168.1.66 5060 [9] 2008/01/01 09:35:37: Resolve 959: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:35:37: Resolve 959: a udp 192.168.1.66 5060 [9] 2008/01/01 09:35:37: Resolve 959: udp 192.168.1.66 5060 [9] 2008/01/01 09:35:38: Resolve 960: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:35:38: Resolve 960: a udp 192.168.1.67 2051 [9] 2008/01/01 09:35:38: Resolve 960: udp 192.168.1.67 2051 [7] 2008/01/01 09:35:38: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-eqiz8xc0rrom;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3012 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:35:38: Resolve 961: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:35:38: Resolve 961: a udp 192.168.1.67 2051 [9] 2008/01/01 09:35:38: Resolve 961: udp 192.168.1.67 2051 [7] 2008/01/01 09:35:38: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-eqiz8xc0rrom;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3012 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 28 Content-Length: 0 [9] 2008/01/01 09:35:52: Resolve 962: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:35:52: Resolve 962: a udp 192.168.1.66 5060 [9] 2008/01/01 09:35:52: Resolve 962: udp 192.168.1.66 5060 [9] 2008/01/01 09:35:52: Resolve 963: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:35:52: Resolve 963: a udp 192.168.1.67 2051 [9] 2008/01/01 09:35:52: Resolve 963: udp 192.168.1.67 2051 [9] 2008/01/01 09:36:07: Resolve 964: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:36:07: Resolve 964: a udp 192.168.1.67 2051 [9] 2008/01/01 09:36:07: Resolve 964: udp 192.168.1.67 2051 [9] 2008/01/01 09:36:07: Resolve 965: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:36:07: Resolve 965: a udp 192.168.1.66 5060 [9] 2008/01/01 09:36:07: Resolve 965: udp 192.168.1.66 5060 [7] 2008/01/01 09:36:08: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-wfo76fdd894c;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3013 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:36:08: Resolve 966: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:36:08: Resolve 966: a udp 192.168.1.67 2051 [9] 2008/01/01 09:36:08: Resolve 966: udp 192.168.1.67 2051 [7] 2008/01/01 09:36:08: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-wfo76fdd894c;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3013 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 28 Content-Length: 0 [9] 2008/01/01 09:36:21: Resolve 967: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:36:21: Resolve 967: a udp 192.168.1.66 5060 [9] 2008/01/01 09:36:21: Resolve 967: udp 192.168.1.66 5060 [9] 2008/01/01 09:36:22: Resolve 968: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:36:22: Resolve 968: a udp 192.168.1.67 2051 [9] 2008/01/01 09:36:22: Resolve 968: udp 192.168.1.67 2051 [9] 2008/01/01 09:36:37: Resolve 969: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:36:37: Resolve 969: a udp 192.168.1.66 5060 [9] 2008/01/01 09:36:37: Resolve 969: udp 192.168.1.66 5060 [7] 2008/01/01 09:36:38: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-mtoie2vaydkz;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3014 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:36:38: Resolve 970: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:36:38: Resolve 970: a udp 192.168.1.67 2051 [9] 2008/01/01 09:36:38: Resolve 970: udp 192.168.1.67 2051 [7] 2008/01/01 09:36:38: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-mtoie2vaydkz;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3014 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 31 Content-Length: 0 [9] 2008/01/01 09:36:38: Resolve 971: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:36:38: Resolve 971: a udp 192.168.1.67 2051 [9] 2008/01/01 09:36:38: Resolve 971: udp 192.168.1.67 2051 [9] 2008/01/01 09:36:52: Resolve 972: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:36:52: Resolve 972: a udp 192.168.1.66 5060 [9] 2008/01/01 09:36:52: Resolve 972: udp 192.168.1.66 5060 [9] 2008/01/01 09:36:54: Resolve 973: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:36:54: Resolve 973: a udp 192.168.1.67 2051 [9] 2008/01/01 09:36:54: Resolve 973: udp 192.168.1.67 2051 [9] 2008/01/01 09:37:07: Resolve 974: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:37:07: Resolve 974: a udp 192.168.1.66 5060 [9] 2008/01/01 09:37:07: Resolve 974: udp 192.168.1.66 5060 [7] 2008/01/01 09:37:08: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-cexpsaoe5ycb;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3015 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:37:08: Resolve 975: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:37:08: Resolve 975: a udp 192.168.1.67 2051 [9] 2008/01/01 09:37:08: Resolve 975: udp 192.168.1.67 2051 [7] 2008/01/01 09:37:08: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-cexpsaoe5ycb;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3015 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 32 Content-Length: 0 [9] 2008/01/01 09:37:08: Resolve 976: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:37:08: Resolve 976: a udp 192.168.1.67 2051 [9] 2008/01/01 09:37:08: Resolve 976: udp 192.168.1.67 2051 [9] 2008/01/01 09:37:21: Resolve 977: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:37:21: Resolve 977: a udp 192.168.1.66 5060 [9] 2008/01/01 09:37:21: Resolve 977: udp 192.168.1.66 5060 [9] 2008/01/01 09:37:23: Resolve 978: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:37:23: Resolve 978: a udp 192.168.1.67 2051 [9] 2008/01/01 09:37:23: Resolve 978: udp 192.168.1.67 2051 [9] 2008/01/01 09:37:37: Resolve 979: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:37:37: Resolve 979: a udp 192.168.1.66 5060 [9] 2008/01/01 09:37:37: Resolve 979: udp 192.168.1.66 5060 [9] 2008/01/01 09:37:38: Resolve 980: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:37:38: Resolve 980: a udp 192.168.1.67 2051 [9] 2008/01/01 09:37:38: Resolve 980: udp 192.168.1.67 2051 [7] 2008/01/01 09:37:38: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-5wu7capmyn9q;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3016 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:37:38: Resolve 981: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:37:38: Resolve 981: a udp 192.168.1.67 2051 [9] 2008/01/01 09:37:38: Resolve 981: udp 192.168.1.67 2051 [7] 2008/01/01 09:37:38: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-5wu7capmyn9q;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3016 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 32 Content-Length: 0 [9] 2008/01/01 09:37:51: Resolve 982: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:37:51: Resolve 982: a udp 192.168.1.66 5060 [9] 2008/01/01 09:37:51: Resolve 982: udp 192.168.1.66 5060 [9] 2008/01/01 09:37:54: Resolve 983: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:37:54: Resolve 983: a udp 192.168.1.67 2051 [9] 2008/01/01 09:37:54: Resolve 983: udp 192.168.1.67 2051 [9] 2008/01/01 09:38:05: Resolve 984: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:38:05: Resolve 984: a udp 192.168.1.66 5060 [9] 2008/01/01 09:38:05: Resolve 984: udp 192.168.1.66 5060 [7] 2008/01/01 09:38:08: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-au0udh5wvo8v;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3017 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:38:08: Resolve 985: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:38:08: Resolve 985: a udp 192.168.1.67 2051 [9] 2008/01/01 09:38:08: Resolve 985: udp 192.168.1.67 2051 [7] 2008/01/01 09:38:08: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-au0udh5wvo8v;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3017 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 28 Content-Length: 0 [9] 2008/01/01 09:38:09: Resolve 986: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:38:09: Resolve 986: a udp 192.168.1.67 2051 [9] 2008/01/01 09:38:09: Resolve 986: udp 192.168.1.67 2051 [9] 2008/01/01 09:38:20: Resolve 987: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:38:20: Resolve 987: a udp 192.168.1.66 5060 [9] 2008/01/01 09:38:20: Resolve 987: udp 192.168.1.66 5060 [9] 2008/01/01 09:38:23: Resolve 988: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:38:23: Resolve 988: a udp 192.168.1.67 2051 [9] 2008/01/01 09:38:23: Resolve 988: udp 192.168.1.67 2051 [9] 2008/01/01 09:38:35: Resolve 989: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:38:35: Resolve 989: a udp 192.168.1.66 5060 [9] 2008/01/01 09:38:35: Resolve 989: udp 192.168.1.66 5060 [9] 2008/01/01 09:38:38: Resolve 990: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:38:38: Resolve 990: a udp 192.168.1.67 2051 [9] 2008/01/01 09:38:38: Resolve 990: udp 192.168.1.67 2051 [7] 2008/01/01 09:38:38: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-qg6250bro8xx;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3018 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:38:38: Resolve 991: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:38:38: Resolve 991: a udp 192.168.1.67 2051 [9] 2008/01/01 09:38:38: Resolve 991: udp 192.168.1.67 2051 [7] 2008/01/01 09:38:38: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-qg6250bro8xx;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3018 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 31 Content-Length: 0 [9] 2008/01/01 09:38:50: Resolve 992: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:38:50: Resolve 992: a udp 192.168.1.66 5060 [9] 2008/01/01 09:38:50: Resolve 992: udp 192.168.1.66 5060 [9] 2008/01/01 09:38:54: Resolve 993: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:38:54: Resolve 993: a udp 192.168.1.67 2051 [9] 2008/01/01 09:38:54: Resolve 993: udp 192.168.1.67 2051 [9] 2008/01/01 09:39:05: Resolve 994: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:05: Resolve 994: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:05: Resolve 994: udp 192.168.1.66 5060 [9] 2008/01/01 09:39:08: Resolve 995: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:39:08: Resolve 995: a udp 192.168.1.67 2051 [9] 2008/01/01 09:39:08: Resolve 995: udp 192.168.1.67 2051 [7] 2008/01/01 09:39:08: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-g45chbxi6a6n;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3019 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:39:08: Resolve 996: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:39:08: Resolve 996: a udp 192.168.1.67 2051 [9] 2008/01/01 09:39:08: Resolve 996: udp 192.168.1.67 2051 [7] 2008/01/01 09:39:08: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-g45chbxi6a6n;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3019 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 31 Content-Length: 0 [9] 2008/01/01 09:39:20: Resolve 997: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:20: Resolve 997: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:20: Resolve 997: udp 192.168.1.66 5060 [9] 2008/01/01 09:39:23: Resolve 998: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:39:23: Resolve 998: a udp 192.168.1.67 2051 [9] 2008/01/01 09:39:23: Resolve 998: udp 192.168.1.67 2051 [9] 2008/01/01 09:39:35: Resolve 999: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:35: Resolve 999: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:35: Resolve 999: udp 192.168.1.66 5060 [9] 2008/01/01 09:39:38: Resolve 1000: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:39:38: Resolve 1000: a udp 192.168.1.67 2051 [9] 2008/01/01 09:39:38: Resolve 1000: udp 192.168.1.67 2051 [7] 2008/01/01 09:39:38: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-bg0157rxs7e7;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3020 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:39:38: Resolve 1001: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:39:38: Resolve 1001: a udp 192.168.1.67 2051 [9] 2008/01/01 09:39:38: Resolve 1001: udp 192.168.1.67 2051 [7] 2008/01/01 09:39:38: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-bg0157rxs7e7;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3020 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 30 Content-Length: 0 [7] 2008/01/01 09:39:41: SIP Rx udp:192.168.1.66:5060: INVITE sip:66687600@192.168.1.64;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-wzx6i0v9sfcb;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone> Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:102@192.168.1.66:5060;line=utmn2liy>;flow-id=1 P-Key-Flags: keys="3" User-Agent: IP150/1.5 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer Supported: timer, 100rel, replaces, callerid Session-Expires: 3600;refresher=uas Min-SE: 90 Content-Type: application/sdp Content-Length: 449 v=0 o=root 464796854 464796854 IN IP4 192.168.1.66 s=call c=IN IP4 192.168.1.66 t=0 0 m=audio 16690 RTP/AVP 18 8 0 2 3 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:x55uJCqZRnWpNPv7jlcjxhZNtRzh2XToQbMy0/oZ a=rtpmap:18 g729/8000 a=rtpmap:8 pcma/8000 a=rtpmap:0 pcmu/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:4 g723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=encryption:optional a=sendrecv [7] 2008/01/01 09:39:41: UDP: Opening socket on port 59892 [7] 2008/01/01 09:39:41: UDP: Opening socket on port 59893 [8] 2008/01/01 09:39:41: Could not find a trunk (1 trunks) [9] 2008/01/01 09:39:41: Resolve 1002: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1002: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1002: udp 192.168.1.66 5060 [7] 2008/01/01 09:39:41: SIP Tx udp:192.168.1.66:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-wzx6i0v9sfcb;rport=5060 From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 1 INVITE Content-Length: 0 [9] 2008/01/01 09:39:41: Resolve 1003: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1003: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1003: udp 192.168.1.66 5060 [7] 2008/01/01 09:39:41: SIP Tx udp:192.168.1.66:5060: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-wzx6i0v9sfcb;rport=5060 From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 1 INVITE User-Agent: 3rivers-PBX/3.0.0.2898 WWW-Authenticate: Digest realm="192.168.1.64",nonce="4ec333afd4812cb7f19805dd4402d051",domain="sip:66687600@192.168.1.64;user=phone",algorithm=MD5 Content-Length: 0 [7] 2008/01/01 09:39:41: SIP Rx udp:192.168.1.66:5060: ACK sip:66687600@192.168.1.64;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-wzx6i0v9sfcb;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 1 ACK Max-Forwards: 70 Contact: <sip:102@192.168.1.66:5060;line=utmn2liy>;flow-id=1 Content-Length: 0 [7] 2008/01/01 09:39:41: SIP Rx udp:192.168.1.66:5060: INVITE sip:66687600@192.168.1.64;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-e9sm9u1q7i5g;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone> Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 2 INVITE Max-Forwards: 70 Contact: <sip:102@192.168.1.66:5060;line=utmn2liy>;flow-id=1 P-Key-Flags: keys="3" User-Agent: IP150/1.5 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer Supported: timer, 100rel, replaces, callerid Session-Expires: 3600;refresher=uas Min-SE: 90 Authorization: Digest username="102",realm="192.168.1.64",nonce="4ec333afd4812cb7f19805dd4402d051",uri="sip:66687600@192.168.1.64;user=phone",response="32c7dba6bc8201a36f01a806110632cc",algorithm=md5 Content-Type: application/sdp Content-Length: 449 v=0 o=root 464796854 464796854 IN IP4 192.168.1.66 s=call c=IN IP4 192.168.1.66 t=0 0 m=audio 16690 RTP/AVP 18 8 0 2 3 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:x55uJCqZRnWpNPv7jlcjxhZNtRzh2XToQbMy0/oZ a=rtpmap:18 g729/8000 a=rtpmap:8 pcma/8000 a=rtpmap:0 pcmu/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:4 g723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=encryption:optional a=sendrecv [8] 2008/01/01 09:39:41: Tagging request with existing tag [7] 2008/01/01 09:39:41: Set packet length to 20 [6] 2008/01/01 09:39:41: Sending RTP for 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3#819f710c2c to 192.168.1.66:16690 [9] 2008/01/01 09:39:41: Resolve 1004: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1004: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1004: udp 192.168.1.66 5060 [7] 2008/01/01 09:39:41: SIP Tx udp:192.168.1.66:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-e9sm9u1q7i5g;rport=5060 From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 2 INVITE Content-Length: 0 [9] 2008/01/01 09:39:41: Dialplan: Evaluating !^(\+?[0-9]*)@.*!sip:\1@\r;user=phone!i against 66687600@192.168.1.64 [5] 2008/01/01 09:39:41: Dialplan PSTN-Singtel: Match 66687600@192.168.1.64 to <sip:66687600@127.0.0.1;user=phone> on trunk PSTN [8] 2008/01/01 09:39:41: Play audio_moh/noise.wav [7] 2008/01/01 09:39:41: UDP: Opening socket on port 50292 [7] 2008/01/01 09:39:41: UDP: Opening socket on port 50293 [9] 2008/01/01 09:39:41: Resolve 1005: url sip:127.0.0.1:5062 [9] 2008/01/01 09:39:41: Resolve 1005: udp 127.0.0.1 5062 [7] 2008/01/01 09:39:41: SIP Tx udp:127.0.0.1:5062: INVITE sip:66687600@127.0.0.1;user=phone SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-15db1c820a6d04695fb0280959b757c6;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=1195229907 To: <sip:66687600@127.0.0.1;user=phone> Call-ID: f1424f12@pbx CSeq: 10761 INVITE Max-Forwards: 70 Contact: <sip:102@127.0.0.1:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: 3rivers-PBX/3.0.0.2898 P-Preferred-Identity: "Tian Lee" <sip:102@localhost> Content-Type: application/sdp Content-Length: 270 v=0 o=- 1713418309 1713418309 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 50292 RTP/AVP 0 8 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [7] 2008/01/01 09:39:41: Set packet length to 20 [9] 2008/01/01 09:39:41: Resolve 1006: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1006: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1006: udp 192.168.1.66 5060 [7] 2008/01/01 09:39:41: SIP Tx udp:192.168.1.66:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-e9sm9u1q7i5g;rport=5060 From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 2 INVITE Contact: <sip:102@192.168.1.64:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: 3rivers-PBX/3.0.0.2898 Require: 100rel RSeq: 1 Content-Type: application/sdp Content-Length: 286 v=0 o=- 865532830 865532830 IN IP4 192.168.1.64 s=- c=IN IP4 192.168.1.64 t=0 0 m=audio 59892 RTP/AVP 0 8 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv [7] 2008/01/01 09:39:41: SIP Rx udp:192.168.1.66:5060: PRACK sip:102@192.168.1.64:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-6hwyrwfjgs5s;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 3 PRACK Max-Forwards: 70 Contact: <sip:102@192.168.1.66:5060;line=utmn2liy>;flow-id=1 RAck: 1 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer Content-Length: 0 [9] 2008/01/01 09:39:41: Resolve 1007: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1007: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:41: Resolve 1007: udp 192.168.1.66 5060 [7] 2008/01/01 09:39:41: SIP Tx udp:192.168.1.66:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-6hwyrwfjgs5s;rport=5060 From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 3 PRACK Contact: <sip:102@192.168.1.64:5060> User-Agent: 3rivers-PBX/3.0.0.2898 Content-Length: 0 [7] 2008/01/01 09:39:41: SIP Rx udp:127.0.0.1:5062: SIP/2.0 100 Trying Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-15db1c820a6d04695fb0280959b757c6;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=1195229907 To: <sip:66687600@127.0.0.1;user=phone> Call-ID: f1424f12@pbx CSeq: 10761 INVITE Content-Length: 0 [6] 2008/01/01 09:39:41: Sending RTP for f1424f12@pbx#1195229907 to 1.1.1.2:2048 [7] 2008/01/01 09:39:45: SIP Rx udp:127.0.0.1:5062: SIP/2.0 200 Ok Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-15db1c820a6d04695fb0280959b757c6;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=1195229907 To: <sip:66687600@127.0.0.1;user=phone>;tag=1 Call-ID: f1424f12@pbx CSeq: 10761 INVITE Contact: <sip:127.0.0.1:5062> Content-Type: application/sdp Content-Length: 137 v=0 o=root 0 0 IN IP4 1.1.1.2 s=- c=IN IP4 1.1.1.2 t=0 0 m=audio 2048 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=ptime:20 [7] 2008/01/01 09:39:45: Call f1424f12@pbx#1195229907: Clear last INVITE [7] 2008/01/01 09:39:45: Set packet length to 20 [9] 2008/01/01 09:39:45: Resolve 1008: url sip:127.0.0.1:5062 [9] 2008/01/01 09:39:45: Resolve 1008: udp 127.0.0.1 5062 [7] 2008/01/01 09:39:45: SIP Tx udp:127.0.0.1:5062: ACK sip:127.0.0.1:5062 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-4ece9e828e668292879a44029500dea6;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=1195229907 To: <sip:66687600@127.0.0.1;user=phone>;tag=1 Call-ID: f1424f12@pbx CSeq: 10761 ACK Max-Forwards: 70 Contact: <sip:102@127.0.0.1:5060;transport=udp> P-Preferred-Identity: "Tian Lee" <sip:102@localhost> Content-Length: 0 [7] 2008/01/01 09:39:45: Determine pass-through mode after receiving response [9] 2008/01/01 09:39:45: Resolve 1009: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:45: Resolve 1009: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:45: Resolve 1009: udp 192.168.1.66 5060 [7] 2008/01/01 09:39:45: SIP Tx udp:192.168.1.66:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-e9sm9u1q7i5g;rport=5060 From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 2 INVITE Contact: <sip:102@192.168.1.64:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: 3rivers-PBX/3.0.0.2898 Content-Type: application/sdp Content-Length: 286 v=0 o=- 865532830 865532830 IN IP4 192.168.1.64 s=- c=IN IP4 192.168.1.64 t=0 0 m=audio 59892 RTP/AVP 0 8 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv [7] 2008/01/01 09:39:45: f1424f12@pbx#1195229907: RTP pass-through mode [7] 2008/01/01 09:39:45: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3#819f710c2c: RTP pass-through mode [7] 2008/01/01 09:39:45: SIP Rx udp:192.168.1.66:5060: ACK sip:102@192.168.1.64:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.66:5060;branch=z9hG4bK-21fr55ekwgz4;rport From: "Tian Yew" <sip:102@192.168.1.64>;tag=5fdtu5e869 To: <sip:66687600@192.168.1.64;user=phone>;tag=819f710c2c Call-ID: 3c3b810c668a-ij3u0zomksum@IP150-00300A6E5AB3 CSeq: 2 ACK Max-Forwards: 70 Contact: <sip:102@192.168.1.66:5060;line=utmn2liy>;flow-id=1 Content-Length: 0 [9] 2008/01/01 09:39:50: Resolve 1010: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:39:50: Resolve 1010: a udp 192.168.1.66 5060 [9] 2008/01/01 09:39:50: Resolve 1010: udp 192.168.1.66 5060 [9] 2008/01/01 09:39:52: Resolve 1011: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:39:52: Resolve 1011: a udp 192.168.1.67 2051 [9] 2008/01/01 09:39:52: Resolve 1011: udp 192.168.1.67 2051 [9] 2008/01/01 09:40:04: Resolve 1012: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:40:04: Resolve 1012: a udp 192.168.1.66 5060 [9] 2008/01/01 09:40:04: Resolve 1012: udp 192.168.1.66 5060 [9] 2008/01/01 09:40:07: Resolve 1013: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:40:07: Resolve 1013: a udp 192.168.1.67 2051 [9] 2008/01/01 09:40:07: Resolve 1013: udp 192.168.1.67 2051 [7] 2008/01/01 09:40:08: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-b039l5uxz0yc;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3021 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:40:08: Resolve 1014: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:40:08: Resolve 1014: a udp 192.168.1.67 2051 [9] 2008/01/01 09:40:08: Resolve 1014: udp 192.168.1.67 2051 [7] 2008/01/01 09:40:08: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-b039l5uxz0yc;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3021 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 29 Content-Length: 0 [9] 2008/01/01 09:40:19: Resolve 1015: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:40:19: Resolve 1015: a udp 192.168.1.66 5060 [9] 2008/01/01 09:40:19: Resolve 1015: udp 192.168.1.66 5060 [9] 2008/01/01 09:40:21: Resolve 1016: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:40:21: Resolve 1016: a udp 192.168.1.67 2051 [9] 2008/01/01 09:40:21: Resolve 1016: udp 192.168.1.67 2051 [9] 2008/01/01 09:40:35: Resolve 1017: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:40:35: Resolve 1017: a udp 192.168.1.66 5060 [9] 2008/01/01 09:40:35: Resolve 1017: udp 192.168.1.66 5060 [9] 2008/01/01 09:40:36: Resolve 1018: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:40:36: Resolve 1018: a udp 192.168.1.67 2051 [9] 2008/01/01 09:40:36: Resolve 1018: udp 192.168.1.67 2051 [7] 2008/01/01 09:40:38: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-otmdpydesbk3;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3022 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:40:38: Resolve 1019: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:40:38: Resolve 1019: a udp 192.168.1.67 2051 [9] 2008/01/01 09:40:38: Resolve 1019: udp 192.168.1.67 2051 [7] 2008/01/01 09:40:38: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-otmdpydesbk3;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3022 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 29 Content-Length: 0 [9] 2008/01/01 09:40:50: Resolve 1020: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:40:50: Resolve 1020: a udp 192.168.1.66 5060 [9] 2008/01/01 09:40:50: Resolve 1020: udp 192.168.1.66 5060 [9] 2008/01/01 09:40:51: Resolve 1021: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:40:51: Resolve 1021: a udp 192.168.1.67 2051 [9] 2008/01/01 09:40:51: Resolve 1021: udp 192.168.1.67 2051 [9] 2008/01/01 09:41:05: Resolve 1022: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:41:05: Resolve 1022: a udp 192.168.1.66 5060 [9] 2008/01/01 09:41:05: Resolve 1022: udp 192.168.1.66 5060 [9] 2008/01/01 09:41:05: Resolve 1023: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:41:05: Resolve 1023: a udp 192.168.1.66 5060 [9] 2008/01/01 09:41:05: Resolve 1023: udp 192.168.1.66 5060 [9] 2008/01/01 09:41:06: Resolve 1024: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:06: Resolve 1024: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:06: Resolve 1024: udp 192.168.1.67 2051 [9] 2008/01/01 09:41:06: Resolve 1025: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:06: Resolve 1025: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:06: Resolve 1025: udp 192.168.1.67 2051 [7] 2008/01/01 09:41:08: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-74suttnach5w;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3023 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:41:08: Resolve 1026: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:08: Resolve 1026: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:08: Resolve 1026: udp 192.168.1.67 2051 [7] 2008/01/01 09:41:08: SIP Tx udp:192.168.1.67:2051: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-74suttnach5w;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3023 SUBSCRIBE User-Agent: 3rivers-PBX/3.0.0.2898 WWW-Authenticate: Digest realm="192.168.1.64",nonce="55391df46762d41e5c21ef1d47cfa2af",domain="sip:103@192.168.1.64",algorithm=MD5 Content-Length: 0 [7] 2008/01/01 09:41:09: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-kxji2uq1efxm;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3024 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Authorization: Digest username="103",realm="192.168.1.64",nonce="55391df46762d41e5c21ef1d47cfa2af",uri="sip:103@192.168.1.64",response="430b8d72a72f9589b3001562be562df5",algorithm=md5 Expires: 3600 l: 0 [9] 2008/01/01 09:41:09: Resolve 1027: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:09: Resolve 1027: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:09: Resolve 1027: udp 192.168.1.67 2051 [7] 2008/01/01 09:41:09: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-kxji2uq1efxm;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3024 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 31 Content-Length: 0 [9] 2008/01/01 09:41:20: Resolve 1028: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:20: Resolve 1028: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:20: Resolve 1028: udp 192.168.1.67 2051 [9] 2008/01/01 09:41:21: Resolve 1029: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:41:21: Resolve 1029: a udp 192.168.1.66 5060 [9] 2008/01/01 09:41:21: Resolve 1029: udp 192.168.1.66 5060 [9] 2008/01/01 09:41:36: Resolve 1030: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:36: Resolve 1030: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:36: Resolve 1030: udp 192.168.1.67 2051 [9] 2008/01/01 09:41:37: Resolve 1031: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:41:37: Resolve 1031: a udp 192.168.1.66 5060 [9] 2008/01/01 09:41:37: Resolve 1031: udp 192.168.1.66 5060 [7] 2008/01/01 09:41:39: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-0qm60fa2ufza;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3025 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:41:39: Resolve 1032: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:39: Resolve 1032: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:39: Resolve 1032: udp 192.168.1.67 2051 [7] 2008/01/01 09:41:39: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-0qm60fa2ufza;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3025 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 32 Content-Length: 0 [9] 2008/01/01 09:41:51: Resolve 1033: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:41:51: Resolve 1033: a udp 192.168.1.66 5060 [9] 2008/01/01 09:41:51: Resolve 1033: udp 192.168.1.66 5060 [9] 2008/01/01 09:41:52: Resolve 1034: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:41:52: Resolve 1034: a udp 192.168.1.67 2051 [9] 2008/01/01 09:41:52: Resolve 1034: udp 192.168.1.67 2051 [9] 2008/01/01 09:42:07: Resolve 1035: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:42:07: Resolve 1035: a udp 192.168.1.66 5060 [9] 2008/01/01 09:42:07: Resolve 1035: udp 192.168.1.66 5060 [9] 2008/01/01 09:42:08: Resolve 1036: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:42:08: Resolve 1036: a udp 192.168.1.67 2051 [9] 2008/01/01 09:42:08: Resolve 1036: udp 192.168.1.67 2051 [7] 2008/01/01 09:42:09: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-4ws3qjhw5o1w;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3026 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:42:09: Resolve 1037: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:42:09: Resolve 1037: a udp 192.168.1.67 2051 [9] 2008/01/01 09:42:09: Resolve 1037: udp 192.168.1.67 2051 [7] 2008/01/01 09:42:09: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-4ws3qjhw5o1w;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3026 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 30 Content-Length: 0 [9] 2008/01/01 09:42:23: Resolve 1038: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:42:23: Resolve 1038: a udp 192.168.1.66 5060 [9] 2008/01/01 09:42:23: Resolve 1038: udp 192.168.1.66 5060 [9] 2008/01/01 09:42:24: Resolve 1039: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:42:24: Resolve 1039: a udp 192.168.1.67 2051 [9] 2008/01/01 09:42:24: Resolve 1039: udp 192.168.1.67 2051 [9] 2008/01/01 09:42:38: Resolve 1040: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:42:38: Resolve 1040: a udp 192.168.1.66 5060 [9] 2008/01/01 09:42:38: Resolve 1040: udp 192.168.1.66 5060 [7] 2008/01/01 09:42:39: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-v5k0ba7i5514;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3027 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:42:39: Resolve 1041: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:42:39: Resolve 1041: a udp 192.168.1.67 2051 [9] 2008/01/01 09:42:39: Resolve 1041: udp 192.168.1.67 2051 [7] 2008/01/01 09:42:39: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-v5k0ba7i5514;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3027 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 30 Content-Length: 0 [9] 2008/01/01 09:42:39: Resolve 1042: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:42:39: Resolve 1042: a udp 192.168.1.67 2051 [9] 2008/01/01 09:42:39: Resolve 1042: udp 192.168.1.67 2051 [9] 2008/01/01 09:42:54: Resolve 1043: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:42:54: Resolve 1043: a udp 192.168.1.66 5060 [9] 2008/01/01 09:42:54: Resolve 1043: udp 192.168.1.66 5060 [9] 2008/01/01 09:42:54: Resolve 1044: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:42:54: Resolve 1044: a udp 192.168.1.67 2051 [9] 2008/01/01 09:42:54: Resolve 1044: udp 192.168.1.67 2051 [9] 2008/01/01 09:43:09: Resolve 1045: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:43:09: Resolve 1045: a udp 192.168.1.66 5060 [9] 2008/01/01 09:43:09: Resolve 1045: udp 192.168.1.66 5060 [7] 2008/01/01 09:43:09: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-g6vowc74btba;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3028 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:43:09: Resolve 1046: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:43:09: Resolve 1046: a udp 192.168.1.67 2051 [9] 2008/01/01 09:43:09: Resolve 1046: udp 192.168.1.67 2051 [7] 2008/01/01 09:43:09: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-g6vowc74btba;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3028 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 28 Content-Length: 0 [9] 2008/01/01 09:43:10: Resolve 1047: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:43:10: Resolve 1047: a udp 192.168.1.67 2051 [9] 2008/01/01 09:43:10: Resolve 1047: udp 192.168.1.67 2051 [9] 2008/01/01 09:43:24: Resolve 1048: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:43:24: Resolve 1048: a udp 192.168.1.66 5060 [9] 2008/01/01 09:43:24: Resolve 1048: udp 192.168.1.66 5060 [9] 2008/01/01 09:43:26: Resolve 1049: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:43:26: Resolve 1049: a udp 192.168.1.67 2051 [9] 2008/01/01 09:43:26: Resolve 1049: udp 192.168.1.67 2051 [7] 2008/01/01 09:43:39: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-5nyffu1xfhuj;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3029 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:43:39: Resolve 1050: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:43:39: Resolve 1050: a udp 192.168.1.67 2051 [9] 2008/01/01 09:43:39: Resolve 1050: udp 192.168.1.67 2051 [7] 2008/01/01 09:43:39: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-5nyffu1xfhuj;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3029 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 28 Content-Length: 0 [9] 2008/01/01 09:43:39: Resolve 1051: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:43:39: Resolve 1051: a udp 192.168.1.66 5060 [9] 2008/01/01 09:43:39: Resolve 1051: udp 192.168.1.66 5060 [9] 2008/01/01 09:43:41: Resolve 1052: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:43:41: Resolve 1052: a udp 192.168.1.67 2051 [9] 2008/01/01 09:43:41: Resolve 1052: udp 192.168.1.67 2051 [9] 2008/01/01 09:43:55: Resolve 1053: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:43:55: Resolve 1053: a udp 192.168.1.66 5060 [9] 2008/01/01 09:43:55: Resolve 1053: udp 192.168.1.66 5060 [9] 2008/01/01 09:43:57: Resolve 1054: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:43:57: Resolve 1054: a udp 192.168.1.67 2051 [9] 2008/01/01 09:43:57: Resolve 1054: udp 192.168.1.67 2051 [7] 2008/01/01 09:44:09: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-az3823kuqr39;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3030 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:44:09: Resolve 1055: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:44:09: Resolve 1055: a udp 192.168.1.67 2051 [9] 2008/01/01 09:44:09: Resolve 1055: udp 192.168.1.67 2051 [7] 2008/01/01 09:44:09: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-az3823kuqr39;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3030 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 32 Content-Length: 0 [9] 2008/01/01 09:44:11: Resolve 1056: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:44:11: Resolve 1056: a udp 192.168.1.66 5060 [9] 2008/01/01 09:44:11: Resolve 1056: udp 192.168.1.66 5060 [9] 2008/01/01 09:44:13: Resolve 1057: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:44:13: Resolve 1057: a udp 192.168.1.67 2051 [9] 2008/01/01 09:44:13: Resolve 1057: udp 192.168.1.67 2051 [9] 2008/01/01 09:44:25: Resolve 1058: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:44:25: Resolve 1058: a udp 192.168.1.66 5060 [9] 2008/01/01 09:44:25: Resolve 1058: udp 192.168.1.66 5060 [9] 2008/01/01 09:44:29: Resolve 1059: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:44:29: Resolve 1059: a udp 192.168.1.67 2051 [9] 2008/01/01 09:44:29: Resolve 1059: udp 192.168.1.67 2051 [7] 2008/01/01 09:44:39: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-7u7dnpnteywe;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3031 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:44:39: Resolve 1060: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:44:39: Resolve 1060: a udp 192.168.1.67 2051 [9] 2008/01/01 09:44:39: Resolve 1060: udp 192.168.1.67 2051 [7] 2008/01/01 09:44:39: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-7u7dnpnteywe;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3031 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 31 Content-Length: 0 [9] 2008/01/01 09:44:40: Resolve 1061: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:44:40: Resolve 1061: a udp 192.168.1.66 5060 [9] 2008/01/01 09:44:40: Resolve 1061: udp 192.168.1.66 5060 [9] 2008/01/01 09:44:45: Resolve 1062: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:44:45: Resolve 1062: a udp 192.168.1.67 2051 [9] 2008/01/01 09:44:45: Resolve 1062: udp 192.168.1.67 2051 [9] 2008/01/01 09:44:55: Resolve 1063: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:44:55: Resolve 1063: a udp 192.168.1.66 5060 [9] 2008/01/01 09:44:55: Resolve 1063: udp 192.168.1.66 5060 [9] 2008/01/01 09:44:59: Resolve 1064: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:44:59: Resolve 1064: a udp 192.168.1.67 2051 [9] 2008/01/01 09:44:59: Resolve 1064: udp 192.168.1.67 2051 [7] 2008/01/01 09:45:09: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-ubdoxjsnokkw;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3032 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:45:09: Resolve 1065: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:45:09: Resolve 1065: a udp 192.168.1.67 2051 [9] 2008/01/01 09:45:09: Resolve 1065: udp 192.168.1.67 2051 [7] 2008/01/01 09:45:09: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-ubdoxjsnokkw;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3032 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 32 Content-Length: 0 [9] 2008/01/01 09:45:11: Resolve 1066: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:45:11: Resolve 1066: a udp 192.168.1.66 5060 [9] 2008/01/01 09:45:11: Resolve 1066: udp 192.168.1.66 5060 [9] 2008/01/01 09:45:15: Resolve 1067: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:45:15: Resolve 1067: a udp 192.168.1.67 2051 [9] 2008/01/01 09:45:15: Resolve 1067: udp 192.168.1.67 2051 [9] 2008/01/01 09:45:27: Resolve 1068: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:45:27: Resolve 1068: a udp 192.168.1.66 5060 [9] 2008/01/01 09:45:27: Resolve 1068: udp 192.168.1.66 5060 [9] 2008/01/01 09:45:30: Resolve 1069: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:45:30: Resolve 1069: a udp 192.168.1.67 2051 [9] 2008/01/01 09:45:30: Resolve 1069: udp 192.168.1.67 2051 [7] 2008/01/01 09:45:39: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-pluzchgbak58;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3033 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:45:39: Resolve 1070: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:45:39: Resolve 1070: a udp 192.168.1.67 2051 [9] 2008/01/01 09:45:39: Resolve 1070: udp 192.168.1.67 2051 [7] 2008/01/01 09:45:39: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-pluzchgbak58;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3033 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 30 Content-Length: 0 [9] 2008/01/01 09:45:43: Resolve 1071: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:45:43: Resolve 1071: a udp 192.168.1.66 5060 [9] 2008/01/01 09:45:43: Resolve 1071: udp 192.168.1.66 5060 [9] 2008/01/01 09:45:46: Resolve 1072: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:45:46: Resolve 1072: a udp 192.168.1.67 2051 [9] 2008/01/01 09:45:46: Resolve 1072: udp 192.168.1.67 2051 [9] 2008/01/01 09:45:57: Resolve 1073: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:45:57: Resolve 1073: a udp 192.168.1.66 5060 [9] 2008/01/01 09:45:57: Resolve 1073: udp 192.168.1.66 5060 [9] 2008/01/01 09:46:01: Resolve 1074: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:46:01: Resolve 1074: a udp 192.168.1.67 2051 [9] 2008/01/01 09:46:01: Resolve 1074: udp 192.168.1.67 2051 [7] 2008/01/01 09:46:09: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-6b5i81v0yt40;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3034 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:46:09: Resolve 1075: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:46:09: Resolve 1075: a udp 192.168.1.67 2051 [9] 2008/01/01 09:46:09: Resolve 1075: udp 192.168.1.67 2051 [7] 2008/01/01 09:46:09: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-6b5i81v0yt40;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3034 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 30 Content-Length: 0 [9] 2008/01/01 09:46:12: Resolve 1076: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:46:12: Resolve 1076: a udp 192.168.1.66 5060 [9] 2008/01/01 09:46:12: Resolve 1076: udp 192.168.1.66 5060 [9] 2008/01/01 09:46:15: Resolve 1077: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:46:15: Resolve 1077: a udp 192.168.1.67 2051 [9] 2008/01/01 09:46:15: Resolve 1077: udp 192.168.1.67 2051 [9] 2008/01/01 09:46:27: Resolve 1078: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:46:27: Resolve 1078: a udp 192.168.1.66 5060 [9] 2008/01/01 09:46:27: Resolve 1078: udp 192.168.1.66 5060 [9] 2008/01/01 09:46:30: Resolve 1079: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:46:30: Resolve 1079: a udp 192.168.1.67 2051 [9] 2008/01/01 09:46:30: Resolve 1079: udp 192.168.1.67 2051 [7] 2008/01/01 09:46:39: SIP Rx udp:192.168.1.67:2051: SUBSCRIBE sip:103@192.168.1.64 SIP/2.0 v: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-ymgpuh3zkh7t;rport f: <sip:103@192.168.1.64>;tag=09pz6hyqrc t: <sip:103@192.168.1.64>;tag=88d985d181 i: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3035 SUBSCRIBE Max-Forwards: 70 m: <sip:103@192.168.1.67:2051;line=vakaz9es>;flow-id=1 Event: message-summary Accept: application/simple-message-summary Expires: 3600 l: 0 [9] 2008/01/01 09:46:39: Resolve 1080: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:46:39: Resolve 1080: a udp 192.168.1.67 2051 [9] 2008/01/01 09:46:39: Resolve 1080: udp 192.168.1.67 2051 [7] 2008/01/01 09:46:39: SIP Tx udp:192.168.1.67:2051: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.67:2051;branch=z9hG4bK-ymgpuh3zkh7t;rport=2051 From: <sip:103@192.168.1.64>;tag=09pz6hyqrc To: <sip:103@192.168.1.64>;tag=88d985d181 Call-ID: 3c26700d94ed-y2ixvwp1du6d@IP150-00300A6E5ABA CSeq: 3035 SUBSCRIBE Contact: <sip:192.168.1.64:5060;transport=udp> Expires: 28 Content-Length: 0 [9] 2008/01/01 09:46:42: Resolve 1081: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:46:42: Resolve 1081: a udp 192.168.1.66 5060 [9] 2008/01/01 09:46:42: Resolve 1081: udp 192.168.1.66 5060 [9] 2008/01/01 09:46:44: Resolve 1082: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:46:44: Resolve 1082: a udp 192.168.1.67 2051 [9] 2008/01/01 09:46:44: Resolve 1082: udp 192.168.1.67 2051 [9] 2008/01/01 09:46:57: Resolve 1083: aaaa udp 192.168.1.66 5060 [9] 2008/01/01 09:46:57: Resolve 1083: a udp 192.168.1.66 5060 [9] 2008/01/01 09:46:57: Resolve 1083: udp 192.168.1.66 5060 [8] 2008/01/01 09:46:58: Route: eth0 c0a80100 ffffff00 [8] 2008/01/01 09:46:58: Route: eth2 c0a80100 ffffff00 [8] 2008/01/01 09:46:58: Route: eth1 01010100 ffffff00 [8] 2008/01/01 09:46:58: Default Route uses 192.168.1.99 [8] 2008/01/01 09:46:58: Default Route uses 192.168.1.64 [9] 2008/01/01 09:46:58: Resolve 1084: aaaa udp 192.168.1.67 2051 [9] 2008/01/01 09:46:58: Resolve 1084: a udp 192.168.1.67 2051 [9] 2008/01/01 09:46:58: Resolve 1084: udp 192.168.1.67 2051 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 9, 2008 Report Share Posted July 9, 2008 Oh I think you need to update the PBX. There is a build 2933 available which might even solve your Caller-ID issues. But at least it will make PSTN logging possible. The SW is available from http://www.pbxnsip.com/software. 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.