Solved: Re: Platform independant cti integration

hanefi.turkoz · ‎12-22-2013

Dear,

i have fully integrate :

- cisco spa 50X

- CRM

- Extension mobility

- IPPBX

And all "not dependant platform", it's work on linux, windows, mac, ... over VPN or over internet ...

but my only problem is BLF and "subscribe" .. with spa500S console.

My question is : is there a way to control CISCO SPA 500S (attendant console) remotely ? by script, php.. ?

my issue is : cisco spa500S don't retry to subscribe with a new call transaction but always with a old... As a see in this forum, many persoon have problem with "subscribe" on spa500S. It's not possible to user to see 30 led blink yellow.. and all phone are online and registered.

Witch setting must i configure for that ?

Cisco Spa500S have some programming sample somewhere i can download ?

PS : i see, i have only this sip error : 481 : call transaction/leg don't exist ..

Regards.

Dan Lukes · ‎12-23-2013

My question is : is there a way to control CISCO SPA 500S (attendant console) remotely ?  by script, php.. ?

As far as I know, no. There are hardcoded interfaces selected by "Server Type" configuration value only, but vendor proprietary interfaces are not documented so much.

You may be interested to read Communities:DOC-11522 althougth it will not to solve your problems ...

View solution in original post

Dan Lukes · ‎01-07-2014

So, most relevant part are here:

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::SUBSCRIBE sip:203@10.0.0.254 SIP/2.0Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-8ddd94e4
From: "394" <394>;tag=32daf143ee67c542
To: <203>
Call-ID: 53c4e17-8c2fee7e@10.0.0.84
CSeq: 33996 SUBSCRIBE
Max-Forwards: 70
Contact: "394" <394>
Accept: application/dialog-info+xml
Expires: 1800
Event: dialog
User-Agent: Cisco/SPA504G-7.5.5
Content-Length: 0

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-Mlb-3409;rport
From: <203>;tag=21419
To: "394" <394>;tag=32daf143ee67c542
Call-ID: 53c4e17-8c2fee7e@10.0.0.84
CSeq: 100269 NOTIFY
Subscription-State: terminated;reason=noresource
Max-Forwards: 70
User-Agent: Draytek Mars 1.0.0
Event: dialog
Content-Type: application/dialog-info+xml
Content-Length:  207
terminated

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::SIP/2.0 200 OKVia: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-8ddd94e4
From: "394" <394>;tag=32daf143ee67c542
To: <203>;tag=21419
Call-ID: 53c4e17-8c2fee7e@10.0.0.84
CSeq: 33996 SUBSCRIBE
Contact: <203>
Server: Draytek Mars 1.0.0
Event: dialog
Expires: 1800
Content-Length: 0

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-XUT-5011;rport
From: <203>;tag=21419
To: "394" <394>;tag=32daf143ee67c542
Call-ID: 53c4e17-8c2fee7e@10.0.0.84
CSeq: 100453 NOTIFY
Subscription-State: terminated;reason=noresource
Max-Forwards: 70
User-Agent: Draytek Mars 1.0.0
Event: dialog
Content-Type: application/dialog-info+xml
Content-Length:  207
terminated

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::SIP/2.0 481 Call Leg/Transaction Does Not ExistTo: "394" <394>;tag=32daf143ee67c542
From: <203>;tag=21419
Call-ID: 53c4e17-8c2fee7e@10.0.0.84
CSeq: 100453 NOTIFY
Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-XUT-5011
Server: Cisco/SPA504G-7.5.5
Content-Length: 0

Lets analyze.

[1] is the SUBSCRIBE packet from 394 to Draytek

[2] is NOTIFYcation from Draytek related to subscription with Subscription-State: terminated

[3] is the response to SUBSCRIBE

[4] is another NOTIFY with Subscription-State: terminated

Taken from RFC3265:

A subscription is destroyed when a notifier sends a NOTIFY request
with a "Subscription-State" of "terminated".

So, subscription of 203 state request is accepted [3] by Draytek, but terminated [2] immediately. The further NOTIFY, like [4] are not part of of valid subscription, so they are rejected with 481 error code.

Conclusion ? 394 is not able to subscribe the 203 state, so button blink orange.

Problem is on Draytek side. I assume it doesn't distinguish between extension that doesn't exist and and extension that's not reachable just now. Describing it in Q.850 terms - it treat code 20 (subscriber absent) the same way as code 1 (unassigned number).

On the other side, I'm not sure what state you wish to see here. All at all, Draytek's behavior related to SUBSCRIPTION to unregistered extension needs to be configured on Draytek.

And rest seems to be obvious. The 203 will start and register to Draytek sometime. Next subscription from 394 will not be terminated anymore, so button become solid green. 394 should retry terminated subscription within 10 second (unless Sub Retry Intvl configured to non-default value by you). Of course, you may not wait 10 second, you may reboot 394. It will trigger new subscription as well.

View solution in original post

Dan Lukes · ‎01-07-2014

Subscription-State: terminated;reason=noresource

And after the 203 go power on, somebody forget the SUBSCRIBE and do not send the NOTIFY to 394.

394 should send SUBSCRIBE peridically (when subscription terminated). If it will not do it, then it seems to be Cisco's bug.

Try to shorten Sub Max Expires to something like 30 second or so. May be the phone is using expire timer dedicated to active subscriptions instead the one for failed subscriptions in our case ...

View solution in original post

Dan Lukes · ‎01-08-2014

Problem is on Draytek side ... it treat code 20 (subscriber absent) the same way as code 1 (unassigned number).

If someone from cisco and draytek "engineer" can confirm that

"Problem" is not the same as "bug". It may be intended behavior. It's questionable what status should be reported in the case the extension is not reachable. It is case-by-case decision.

cisco spa don't SUBSCRIBE if "noressource" ?

It subscribe. But such subscription is terminated immediately by Draytek. Client can do not so much with it.

I know now too why i must "hard reboot like power off power on".

When i reboot the phone by http://10.0.0.86/admin/reboot ..the registration of the extension is "directly removed" from draytek.

if i hard reboot like "power off, power on", the registration of the extension still in "draytek"..because registration time of 300s.

It's expected behavior. Phone should unregister whenever possible before before it go offline. PBX can recognize missing phone by timeout, but it's so late.

I hope cisco and draytek can find a solution for me.

According your log:

Wed Jan 08 2014 14:43:16 GMT+0100 (CET)::10.0.0.84::SUBSCRIBE
...
Wed Jan 08 2014 14:43:59 GMT+0100 (CET)::10.0.0.84::SUBSCRIBE

... the Cisco will try to subscribe periodically. Not sure what solution you are wishing for. If you want the Draytek not to terminate subscription despite the extension unavaiable, then ask Draytek. I'm not sure how the Cisco can help you ...

View solution in original post

Dan Lukes · ‎12-23-2013

My question is : is there a way to control CISCO SPA 500S (attendant console) remotely ?  by script, php.. ?

As far as I know, no. There are hardcoded interfaces selected by "Server Type" configuration value only, but vendor proprietary interfaces are not documented so much.

You may be interested to read Communities:DOC-11522 althougth it will not to solve your problems ...

hanefi.turkoz · ‎12-23-2013

Dan,

We do reverse ingeniering.. It's Time to cisco to give us somes documentations or howto.

I have see yours doc about syslog and call status....this is too reverse ingeniering.

Now it´s time to cisco to give all info... Blf-subscribe is a major feature for us.

Regards

Dan Lukes · ‎12-24-2013

Good luck! It's unfortunate that exact description of product features needs to be reverse-engineered by customers, but it's the life with Cisco products. They still have some important features not avaiable in competitor's products (thanks Sipura, you made some excelent design decisions) ...

By the way, it seems I did not understand completely your problem. BLF subscribe works for us. What you mean saying "spa500S don't retry to subscribe with a new call transaction" ? BLF is not related to call. BLF is persistent subscription to remote state. It is switch job to send "state changed" notification to subscriber ...

hanefi.turkoz · ‎12-24-2013

Dan,

BLF work for me too, but only if spa500s is registered to pbx after all other phone.

In this case, on idle state led is Green, on ringing is blink red and on call is red. That work very well.

Problem :

If a phoneX go offline (power off), in pbx ext is offline. Spa500s must change the Led Color from Green to yellow blink. This is the good scénario but Led stay Green !

If a phoneX go online (power on), in pbx ext is online. Spa500s must change the Led Color from yellow blink to Green. But Led stay "yellow blink"

For this 2 problem, i have to power off, power on spa500s for have the real situation of all extension (online or offline) and the good Color yellow blink or Green.

Imagine this situation in "extension mobility", how détermine who is online or offline because all Led Color is not correct (Green/yellow blink)

But when you push a bad Led Color (yellow blink but ext is online), speed dial work.

When a ext go online or offline, in ip pbx status of ext is directly refresh

For me, this is à error of cisco spa 500s or me :)

This is what say draytek :

I have discuss with R&D about BLF issue between Draytek and Phone , we thinks that could be a compatibility issue between them.

R&D said, the BLF in IPPBX follow RFC spec for communication and BLF working with all most of IPPhone now (Linksys/ Snom/VP350/Aastra...etc), so we thinks the issue may happen in Cisco Phone send BLF format have some different / special format caused IPPBX can't changed BLF status in Cisco Phone by sending Notify.

Regards

Dan Lukes · ‎12-24-2013

So, are you saying that phone will unregister self from the switch during it's on->off transition, switch as event notifier will sent notification about state change to subscriber, but the message is not accepted by it ?

Catch the SIP messages between switch and both phones. I'm interested to see REGISTER, SUBSCRIBE and NOTIFY SIP messages (and responses to them). Syslog & debug messages may be usefull as well.

It should help with the problem analysis. I'm still not sure the problem is no Cisco's side ...

hanefi.turkoz · ‎12-24-2013

Dear Dan,

thanks for you help.

Maybe you will undertand better with printscreen

my spa500S connected to a cisco spa504G and his setting :

A sample of setting, (have 10 spa500S this is for a department)

This is the online offline status of registered extension to ippbx.

And this is the real problem :

All printscreen is at same moment then all subscribe must be same :

from a phoneX :

And this come from other cisco spa500S :

Why this is not "clone" ? Why all cisco spa500S do not refresh status of the extension?

Do you imagine the number of "led yellow blink" in the last printscreen

I have put a cisco spa504G in debug mode ..just see sip error 481. i will do full debug mode and look for log but i have see only sip error 481.

When a phone go offline (on -> off) .. between 5 or 10 secondes, ippbx status of extension go from online to offline. (see photo 3)

Dan, i am not at office, i will do debug/log and send here that next time a go to office.

Regards

Dan Lukes · ‎12-24-2013

SIP event notification is not based on client's refresh of status. Client (phone here) just subscribe, then status change notifications are sent on behalf of notifier (IPPBX switch here). By the way, SPA500S is unable to do anything related to SIP communication, including a refresh of STATE. SPA500S is dumb extension, it's behavior is driven by phone where the SPA500S is connected to.

I assume that NOTIFY sent by IPPBX is not recognized by phone. It may be because it's malformed (IPPBX bug) or you may hit the Cisco's firmware bug. Cath the packets, it will help.

Dan, i am not at office, i will do debug/log and send here that next time a go to office.

How it is possible you are not in office on advent evening ? ;-)

hanefi.turkoz · ‎12-24-2013

Thanks Dan,

I have send this post to draytek too.. maybe he will look and find the issue.

It's possible because i hate not find a solution to a problem and i work 24/24 7/7 in my mind

Happy Chrismas

Dan Lukes · ‎12-24-2013

I hate blackboxes, so I'm interested to found all about the device we are using. We have about thousand of SPA5xx, so I would like to avoid unwelcomed future surprises. Your problem may hit us as well ...

Happy Chrismas.

hanefi.turkoz · ‎01-07-2014

Dear Dan,

Here the log file :

The situation : 2x SPA504G

ext 203 is power of

ext 394 is power of (this have 1 line configured with

fnc=sd+blf+cp;sub=203@10.0.0.254;usr=203@10.0.0.254;nme=203)

ext 394 go power on, phone "register" to pbx but ext fonction line is blink orange.

ext 203 go power on and "register" to pbx

ext 394 : ext fonction line continue to blink orange.

ext 394 : power off

ext 394 : power on, phone "register" to pbx and ext fonction line is green

then i test blf, sd, ... and all work.

Have a nice new years

Edit : second try :

394 power on, just 5 sec after 203 power on.

394 extended line fonction : blink orange

And when i make a call with 203, this is the log : 481 Call Leg/Transaction Does Not Exist

Tue Jan 07 2014 11:21:55 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-bgA-1939;rport

From: <203>;tag=23263

To: "394" <394>;tag=5a7e9bc1747cecef

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95754 NOTIFY

Subscription-State: active

Max-Forwards: 70

User-Agent: Draytek Mars 1.0.0

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: 206

confirmed

Tue Jan 07 2014 11:21:55 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:21:55 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{311)

Tue Jan 07 2014 11:21:55 GMT+0100 (CET)::SIP/2.0 481 Call Leg/Transaction Does Not Exist

To: "394" <394>;tag=5a7e9bc1747cecef

From: <203>;tag=23263

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95754 NOTIFY

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-bgA-1939

Server: Cisco/SPA504G-7.5.5

Content-Length: 0

Tue Jan 07 2014 11:21:55 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:21:55 GMT+0100 (CET)::<134>[0]CC:NewCallState 13/8

Tue Jan 07 2014 11:21:55 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::<134>[0]CC:NewCallState 0/13

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-Eki-19049;rport

From: <203>;tag=23263

To: "394" <394>;tag=5a7e9bc1747cecef

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95755 NOTIFY

Subscription-State: active

Max-Forwards: 70

User-Agent: Draytek Mars 1.0.0

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: 207

terminated

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{312)

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::SIP/2.0 481 Call Leg/Transaction Does Not Exist

To: "394" <394>;tag=5a7e9bc1747cecef

From: <203>;tag=23263

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95755 NOTIFY

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-Eki-19049

Server: Cisco/SPA504G-7.5.5

Content-Length: 0

Tue Jan 07 2014 11:21:56 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:22:50 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{682)

Tue Jan 07 2014 11:22:50 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-5969ef7a

From: "394" <394>;tag=d946b88f7d07c672o0

To: "394" <394>

Call-ID: f8181c84-636625c2@10.0.0.84

CSeq: 32163 REGISTER

Max-Forwards: 70

Authorization: Digest username="394",realm="ABCD.BE",nonce="75970631c875072f787b2c986de0514e",uri="sip:10.0.0.254",algorithm=MD5,response="6ce027f55fc4174c7b37b08adb55a858",opaque="7422e18bbd76e68ad575621e34f93712"

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 11:22:50 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:22:50 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 11:22:50 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-5969ef7a

From: "394" <394>;tag=d946b88f7d07c672o0

To: "394" <394>;tag=2308

Call-ID: f8181c84-636625c2@10.0.0.84

CSeq: 32163 REGISTER

Contact: "394" <394>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 11:22:50 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:22:50 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

Tue Jan 07 2014 11:23:47 GMT+0100 (CET)::<134>[0]CC:NewCallState 6/0

Tue Jan 07 2014 11:23:47 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:49 GMT+0100 (CET)::<134>[0]CC:NewCallState 0/6

Tue Jan 07 2014 11:23:49 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:50 GMT+0100 (CET)::<134>[0]CC:NewCallState 6/0

Tue Jan 07 2014 11:23:50 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>[0]CC:NewCallState 8/6

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-aPb-6984;rport

From: <203>;tag=23263

To: "394" <394>;tag=5a7e9bc1747cecef

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95818 NOTIFY

Subscription-State: active

Max-Forwards: 70

User-Agent: Draytek Mars 1.0.0

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: 207

confirmed

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{311)

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::SIP/2.0 481 Call Leg/Transaction Does Not Exist

To: "394" <394>;tag=5a7e9bc1747cecef

From: <203>;tag=23263

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95818 NOTIFY

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-aPb-6984

Server: Cisco/SPA504G-7.5.5

Content-Length: 0

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>[0]CC:NewCallState 13/8

Tue Jan 07 2014 11:23:51 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::<134>[0]CC:NewCallState 0/13

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-lYj-19580;rport

From: <203>;tag=23263

To: "394" <394>;tag=5a7e9bc1747cecef

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95819 NOTIFY

Subscription-State: active

Max-Forwards: 70

User-Agent: Draytek Mars 1.0.0

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: 208

terminated

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::<134>

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{312)

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::SIP/2.0 481 Call Leg/Transaction Does Not Exist

To: "394" <394>;tag=5a7e9bc1747cecef

From: <203>;tag=23263

Call-ID: 28ecf9a9-f29be827@10.0.0.84

CSeq: 95819 NOTIFY

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-lYj-19580

Server: Cisco/SPA504G-7.5.5

Content-Length: 0

Tue Jan 07 2014 11:23:52 GMT+0100 (CET)::<134>

Regards

Dan Lukes · ‎01-07-2014

ext 394 is power of (this have 1 line configured with fnc=sd+blf+cp;sub=203@10.0.0.254;usr=203@10.0.0.254;nme=203)
ext 394 go power on, phone "register" to pbx but ext fonction line is blink orange.

394 should not only register, but also subscribe for 203@10.0.0.254 state. So we need to know:

did 394 sent SUBSCRIBE request to IPPBX ?
what IPPBX responded ?
did IPPBX sent NOTIFY related to 203@10.0.0.254 state ?

The log you copied here show NOTIFY from IPPBX with no previous SUBSCRIBE from 394. Phone 394 respond

481 Call Leg/Transaction Does Not Exist

It's correct as it's unsolicited NOTIFY. No NOTIFY without previous SUBSCRIBE is correct.

It's either because 394 did not sent SUBSCRIBE, or such kind of packet is not recorded in the LOG you catched or you didn't copied relevant part of LOG here.

I suspect that IPPBX rejects the 394's SUBSCRIBE because it treat unregistered extension 203 as nonexistent extension. But it's hard to make hypothesis with no complete packet trace.

Unfortunatelly, we need to see 394's SUBSCRIBE, Draytek's response to it and Draytek's NOTIFY together or we need to be sure such packets has not been sent by 394 and/or Draytek. Catch packets on the wire, using tcpdump or wireshark or so.

hanefi.turkoz · ‎01-07-2014

Dear Dan,

203 and 394 : power off

i make a new syslog :

394 power on :

Here log result, just 394 because 203 is power off.

Last login: Tue Jan 7 14:25:53 on ttys000

admin$ node syslogcisco.php

server listening 0.0.0.0:2514

Tue Jan 07 2014 14:28:51 GMT+0100 (CET)::<143> gateway ip: 10.0.0.254

Tue Jan 07 2014 14:28:51 GMT+0100 (CET)::<159>IDBG: LS, 270-4d8

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>IDBG: SOK

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>IDBG: st-0

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>SCCPTCP:ERR:Can't bind to a000054:5060 errno=49

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<151>Resolving 10.0.0.254

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::: save param: 547 = 0 548

save param: 548 = 0 548

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>[BKpic]Loading text background image

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkcfwd in Idle key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkdnd in Idle key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkcfwd in Progressing key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkdnd in Progressing key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkcfwd in Releasing key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkdnd in Releasing key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkcfwd in Hold key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkdnd in Hold key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkcfwd in Shared Active key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkdnd in Shared Active key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkcfwd in Shared Held key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<3>PGSK: chkdnd in Shared Held key list is not defined

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>[0]Reg Addr Change(0) 0:0->a0000fe:5060

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{456)

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-da81b8c6

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29948 REGISTER

Max-Forwards: 70

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-da81b8c6

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>;tag=20081

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29948 REGISTER

WWW-Authenticate: Digest realm="abcd.be", nonce="9e46a7318ea45242a69338c0c516348f", opaque="a72fbcefae7ea1339c24f287d773fc26"

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{681)

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-df9336d6

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29949 REGISTER

Max-Forwards: 70

Authorization: Digest username="394",realm="abcd.be",nonce="9e46a7318ea45242a69338c0c516348f",uri="sip:10.0.0.254",algorithm=MD5,response="6c0742814c961fb9b596fa2496535e81",opaque="a72fbcefae7ea1339c24f287d773fc26"

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-df9336d6

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>;tag=10050

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29949 REGISTER

Contact: "394" <394>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 300 (0)

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>[BKpic]Download picture from http://10.0.0.1/cisco/spa/rivagelogo.bmp

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>[create_tcp_netstrm1] use async to create tcp connection

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>connect succeed

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>[create_tcp_netstrm1] connect SUCCEED

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<134>content len (hdr) =990

Tue Jan 07 2014 14:28:52 GMT+0100 (CET)::<159>[BKpic]Same URL, not load

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{416)

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::SUBSCRIBE sip:203@10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-8ddd94e4

From: "394" <394>;tag=32daf143ee67c542

To: <203>

Call-ID: 53c4e17-8c2fee7e@10.0.0.84

CSeq: 33996 SUBSCRIBE

Max-Forwards: 70

Contact: "394" <394>

Accept: application/dialog-info+xml

Expires: 1800

Event: dialog

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-Mlb-3409;rport

From: <203>;tag=21419

To: "394" <394>;tag=32daf143ee67c542

Call-ID: 53c4e17-8c2fee7e@10.0.0.84

CSeq: 100269 NOTIFY

Subscription-State: terminated;reason=noresource

Max-Forwards: 70

User-Agent: Draytek Mars 1.0.0

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: 207

terminated

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{278)

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::SIP/2.0 200 OK

To: "394" <394>;tag=32daf143ee67c542

From: <203>;tag=21419

Call-ID: 53c4e17-8c2fee7e@10.0.0.84

CSeq: 100269 NOTIFY

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-Mlb-3409

Server: Cisco/SPA504G-7.5.5

Content-Length: 0

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-8ddd94e4

From: "394" <394>;tag=32daf143ee67c542

To: <203>;tag=21419

Call-ID: 53c4e17-8c2fee7e@10.0.0.84

CSeq: 33996 SUBSCRIBE

Contact: <203>

Server: Draytek Mars 1.0.0

Event: dialog

Expires: 1800

Content-Length: 0

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:28:53 GMT+0100 (CET)::<151>[0]SubOK. NextSub in 1799 (1)

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fs:048237:048237:262144

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fls:fuafffffff:2:144:58032

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fbr:0:3000:3000:0c62a:0016:0015:7.5.5

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:01:0:0001:upg:app:M:7.4.9c

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:02:0:0002:upg:app:0:7.5.2b

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:03:0:0003:upg:app:1:7.5.2b

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:04:0:0004:upg:app:2:7.5.2b

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:05:0:0005:upg:app:0:7.5.4

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:06:0:0006:upg:app:1:7.5.4

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:07:0:0007:upg:app:2:7.5.4

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:08:0:0008:upg:app:0:7.5.5

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:09:0:0009:upg:app:1:7.5.5

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fhs:0a:0:000a:upg:app:2:7.5.5

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>dhcp opt 66: ""

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>dhcp opt 160: ""

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>dhcp opt 159: ""

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>dhcp opt 150: ""

Tue Jan 07 2014 14:29:07 GMT+0100 (CET)::<159>fu:0:0c644, 5.1.1 1

Tue Jan 07 2014 14:29:14 GMT+0100 (CET)::<134>resync rule: /spa504G.cfg

Tue Jan 07 2014 14:30:59 GMT+0100 (CET)::<159>PHN_setAudioPath(1)

Tue Jan 07 2014 14:30:59 GMT+0100 (CET)::<134>[0]CC:NewCallState 6/0

Tue Jan 07 2014 14:30:59 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:30:59 GMT+0100 (CET)::<134>[0]CC:NewCallState 0/6

Tue Jan 07 2014 14:30:59 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:30:59 GMT+0100 (CET)::<159>PHN_setAudioPath(0)

Tue Jan 07 2014 14:31:31 GMT+0100 (CET)::<151>CC:Clean Up

Tue Jan 07 2014 14:31:31 GMT+0100 (CET)::<151>--- OBJ POOL STAT ---

Tue Jan 07 2014 14:31:31 GMT+0100 (CET)::<151>OP:? = 2 ( 8 1328)

Tue Jan 07 2014 14:31:31 GMT+0100 (CET)::<151>

Tue Jan 07 2014 14:32:47 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{681)

Tue Jan 07 2014 14:32:47 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-f5c3ea83

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29950 REGISTER

Max-Forwards: 70

Authorization: Digest username="394",realm="abcd.be",nonce="9e46a7318ea45242a69338c0c516348f",uri="sip:10.0.0.254",algorithm=MD5,response="6c0742814c961fb9b596fa2496535e81",opaque="a72fbcefae7ea1339c24f287d773fc26"

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 14:32:47 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:32:47 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:32:47 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-f5c3ea83

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>;tag=27112

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29950 REGISTER

Contact: "394" <394>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:32:47 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:32:47 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

Tue Jan 07 2014 14:33:26 GMT+0100 (CET)::<159>PHN_setAudioPath(1)

Tue Jan 07 2014 14:33:26 GMT+0100 (CET)::<134>[0]CC:NewCallState 6/0

Tue Jan 07 2014 14:33:26 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:33:26 GMT+0100 (CET)::<134>[0]CC:NewCallState 0/6

Tue Jan 07 2014 14:33:26 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:33:26 GMT+0100 (CET)::<159>PHN_setAudioPath(0)

Tue Jan 07 2014 14:33:58 GMT+0100 (CET)::<151>CC:Clean Up

Tue Jan 07 2014 14:33:58 GMT+0100 (CET)::<151>--- OBJ POOL STAT ---

Tue Jan 07 2014 14:33:58 GMT+0100 (CET)::<151>OP:? = 2 ( 8 1328)

Tue Jan 07 2014 14:33:58 GMT+0100 (CET)::<151>

Tue Jan 07 2014 14:36:41 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{680)

Tue Jan 07 2014 14:36:41 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-4b192c9

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29951 REGISTER

Max-Forwards: 70

Authorization: Digest username="394",realm="abcd.be",nonce="9e46a7318ea45242a69338c0c516348f",uri="sip:10.0.0.254",algorithm=MD5,response="6c0742814c961fb9b596fa2496535e81",opaque="a72fbcefae7ea1339c24f287d773fc26"

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 14:36:41 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:36:41 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:36:41 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-4b192c9

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>;tag=6625

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29951 REGISTER

Contact: "394" <394>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:36:41 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:36:41 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::NOTIFY sip:394@10.0.0.84:5060 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-XUT-5011;rport

From: <203>;tag=21419

To: "394" <394>;tag=32daf143ee67c542

Call-ID: 53c4e17-8c2fee7e@10.0.0.84

CSeq: 100453 NOTIFY

Subscription-State: terminated;reason=noresource

Max-Forwards: 70

User-Agent: Draytek Mars 1.0.0

Event: dialog

Content-Type: application/dialog-info+xml

Content-Length: 207

terminated

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{311)

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::SIP/2.0 481 Call Leg/Transaction Does Not Exist

To: "394" <394>;tag=32daf143ee67c542

From: <203>;tag=21419

Call-ID: 53c4e17-8c2fee7e@10.0.0.84

CSeq: 100453 NOTIFY

Via: SIP/2.0/UDP 10.0.0.254:5060;branch=z9hG4bK-XUT-5011

Server: Cisco/SPA504G-7.5.5

Content-Length: 0

Tue Jan 07 2014 14:38:38 GMT+0100 (CET)::<134>

hanefi.turkoz · ‎01-07-2014

And this log : when i power on 203

Actual : 394 bink orange

Normal : 394 must go from blink orange to green because 203 is online.

Tue Jan 07 2014 14:52:07 GMT+0100 (CET)::<143> gateway ip: 10.0.0.254

Tue Jan 07 2014 14:52:07 GMT+0100 (CET)::<134>SCCPTCP:ERR:Can't bind to a000056:5060 errno=49

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>IDBG: LS, 270-4d8

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>IDBG: SOK

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>IDBG: st-0

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<151>Resolving 10.0.0.254

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::: save param: 547 = 0 548

save param: 548 = 0 548

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>[BKpic]Loading text background image

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>[0]Reg Addr Change(0) 0:0->a0000fe:5060

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{481)

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-cd0c9450

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12273 REGISTER

Max-Forwards: 70

Contact: "203" <203>;expires=3600

User-Agent: Cisco/SPA501G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE, MESSAGE

Supported: replaces

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-cd0c9450

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>;tag=17073

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12273 REGISTER

WWW-Authenticate: Digest realm="abcd.be", nonce="7b3b4f9d307321fd1c5ead3c06dfcc86", opaque="89014d3688bc9fcf75e8943add0afc66"

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{706)

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-5a21d268

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12274 REGISTER

Max-Forwards: 70

Authorization: Digest username="203",realm="abcd.be",nonce="7b3b4f9d307321fd1c5ead3c06dfcc86",uri="sip:10.0.0.254",algorithm=MD5,response="fee96b0ed56536e5a2b1457af5672b0b",opaque="89014d3688bc9fcf75e8943add0afc66"

Contact: "203" <203>;expires=3600

User-Agent: Cisco/SPA501G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE, MESSAGE

Supported: replaces

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-5a21d268

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>;tag=10617

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12274 REGISTER

Contact: "203" <203>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>[BKpic]Download picture from http://10.0.0.1/cisco/spa/rivagelogo.bmp

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>[create_tcp_netstrm1] use async to create tcp connection

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>connect succeed

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>[create_tcp_netstrm1] connect SUCCEED

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<134>content len (hdr) =990

Tue Jan 07 2014 14:52:08 GMT+0100 (CET)::<159>[BKpic]Same URL, not load

Tue Jan 07 2014 14:52:18 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{681)

Tue Jan 07 2014 14:52:18 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-bb5b31b9

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29955 REGISTER

Max-Forwards: 70

Authorization: Digest username="394",realm="abcd.be",nonce="9e46a7318ea45242a69338c0c516348f",uri="sip:10.0.0.254",algorithm=MD5,response="6c0742814c961fb9b596fa2496535e81",opaque="a72fbcefae7ea1339c24f287d773fc26"

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 14:52:18 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:52:18 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:52:18 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-bb5b31b9

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>;tag=17259

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29955 REGISTER

Contact: "394" <394>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:52:18 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:52:18 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fs:054575:054575:262144

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fls:fafuffffff:9:5898:61200

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fbr:0:3000:3000:0eb98:0032:0031:7.5.5

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:01:1:002d:upg:app:1:7.5.2b

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:02:1:002e:upg:app:2:7.5.2b

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:03:1:002f:upg:app:0:7.5.3

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:04:1:0030:upg:app:1:7.5.3

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:05:1:0031:upg:app:2:7.5.3

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:06:1:0032:upg:app:0:7.5.2b

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:07:1:0033:upg:app:1:7.5.2b

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:08:1:0034:upg:app:2:7.5.2b

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:09:1:0035:upg:app:0:7.5.3

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:0a:1:0036:upg:app:1:7.5.3

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:0b:1:0037:upg:app:2:7.5.3

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:0c:1:0038:upg:app:0:7.5.4

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:0d:1:0039:upg:app:1:7.5.4

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:0e:1:003a:upg:app:2:7.5.4

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:0f:1:003b:upg:app:0:7.5.5

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:10:1:003c:upg:app:1:7.5.5

Tue Jan 07 2014 14:52:25 GMT+0100 (CET)::<159>fhs:11:1:003d:upg:app:2:7.5.5

Tue Jan 07 2014 14:52:26 GMT+0100 (CET)::<159>dhcp opt 66: ""

Tue Jan 07 2014 14:52:26 GMT+0100 (CET)::<159>dhcp opt 160: ""

Tue Jan 07 2014 14:52:26 GMT+0100 (CET)::<159>dhcp opt 159: ""

Tue Jan 07 2014 14:52:26 GMT+0100 (CET)::<159>dhcp opt 150: ""

Tue Jan 07 2014 14:52:26 GMT+0100 (CET)::<159>fu:0:0ebb2, 5.1.1 1

Tue Jan 07 2014 14:56:02 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{706)

Tue Jan 07 2014 14:56:02 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-5833a9ff

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12275 REGISTER

Max-Forwards: 70

Authorization: Digest username="203",realm="abcd.be",nonce="7b3b4f9d307321fd1c5ead3c06dfcc86",uri="sip:10.0.0.254",algorithm=MD5,response="fee96b0ed56536e5a2b1457af5672b0b",opaque="89014d3688bc9fcf75e8943add0afc66"

Contact: "203" <203>;expires=3600

User-Agent: Cisco/SPA501G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE, MESSAGE

Supported: replaces

Tue Jan 07 2014 14:56:02 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:56:02 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:56:02 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-5833a9ff

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>;tag=20568

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12275 REGISTER

Contact: "203" <203>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:56:02 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:56:02 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

Tue Jan 07 2014 14:56:12 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{681)

Tue Jan 07 2014 14:56:12 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-a88f7423

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29956 REGISTER

Max-Forwards: 70

Authorization: Digest username="394",realm="abcd.be",nonce="9e46a7318ea45242a69338c0c516348f",uri="sip:10.0.0.254",algorithm=MD5,response="6c0742814c961fb9b596fa2496535e81",opaque="a72fbcefae7ea1339c24f287d773fc26"

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 14:56:12 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:56:12 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:56:12 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-a88f7423

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>;tag=9646

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29956 REGISTER

Contact: "394" <394>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:56:12 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:56:12 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 300 (0)

Tue Jan 07 2014 14:59:56 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{706)

Tue Jan 07 2014 14:59:56 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-502ababe

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12276 REGISTER

Max-Forwards: 70

Authorization: Digest username="203",realm="abcd.be",nonce="7b3b4f9d307321fd1c5ead3c06dfcc86",uri="sip:10.0.0.254",algorithm=MD5,response="fee96b0ed56536e5a2b1457af5672b0b",opaque="89014d3688bc9fcf75e8943add0afc66"

Contact: "203" <203>;expires=3600

User-Agent: Cisco/SPA501G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE, MESSAGE

Supported: replaces

Tue Jan 07 2014 14:59:56 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:59:56 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 14:59:56 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.86:5060;branch=z9hG4bK-502ababe

From: "203" <203>;tag=e750783586359b27o0

To: "203" <203>;tag=10983

Call-ID: 3429fec4-d593a8ab@10.0.0.86

CSeq: 12276 REGISTER

Contact: "203" <203>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 14:59:56 GMT+0100 (CET)::<134>

Tue Jan 07 2014 14:59:56 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

Tue Jan 07 2014 15:00:07 GMT+0100 (CET)::<134>[0:5060]->10.0.0.254:5060{681)

Tue Jan 07 2014 15:00:07 GMT+0100 (CET)::REGISTER sip:10.0.0.254 SIP/2.0

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-394fc150

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29957 REGISTER

Max-Forwards: 70

Authorization: Digest username="394",realm="abcd.be",nonce="9e46a7318ea45242a69338c0c516348f",uri="sip:10.0.0.254",algorithm=MD5,response="6c0742814c961fb9b596fa2496535e81",opaque="a72fbcefae7ea1339c24f287d773fc26"

Contact: "394" <394>;expires=3600

User-Agent: Cisco/SPA504G-7.5.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE

Supported: replaces

Tue Jan 07 2014 15:00:07 GMT+0100 (CET)::<134>

Tue Jan 07 2014 15:00:07 GMT+0100 (CET)::<134>[0:5060]<<10.0.0.254:5060

Tue Jan 07 2014 15:00:07 GMT+0100 (CET)::SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.0.0.84:5060;branch=z9hG4bK-394fc150

From: "394" <394>;tag=3b00b8ecc4af76do0

To: "394" <394>;tag=26613

Call-ID: b7dca833-343ff5cd@10.0.0.84

CSeq: 29957 REGISTER

Contact: "394" <394>;expires=300

Server: Draytek Mars 1.0.0

Content-Length: 0

Tue Jan 07 2014 15:00:07 GMT+0100 (CET)::<134>

Tue Jan 07 2014 15:00:07 GMT+0100 (CET)::<151>[0]RegOK. NextReg in 299 (1)

hanefi.turkoz · ‎01-07-2014

Dear Dan,

i think, after this :

Subscription-State: terminated;reason=noresource

And after the 203 go power on, somebody forget the SUBSCRIBE and do not send the NOTIFY to 394.

I am correct ?

Regards