scarlet voip

[philippe_d]

Dus de clip wordt niet goed doorgestuurd ?

Is dit geen betalende optie bij Scarlet?

[ Post made via mobile device ]

[honda4life]

Ja.

Puur uit principe weiger ik om deze 'dienst' te betalen.
Bijbetalen om een standaard functie te blokkeren... Mooi niet.

[ Post made via mobile device ]

[xming]

idd.

[Stefaand]

Ja dat is een betalende functie.
Maar die heeft altijd gewerkt.

Nu is mijn account overgezet op ims...maar ik betaal er nog steeds voor, dus moet dat ook geactiveerd zijn en werken.

Maar het werkt niet meer.

ik krijg bij iedereen die belt -1 op het display....en dat krijg je als de CLI niet wordt doorgestuurd.

[ikhlaske]

Ik betaal voor de functie, maar ik krijg geen nummerweergave aan de praat!

Dit zijn mijn instellingen voor Scarlet Voip (ims) op FB7390

Features
DTMF transmission Automatically
Suppress outgoing Caller ID (CLIR) disabled
Caller ID number in username and display name

Iemand die wete hoe ze juist moeten staan?

[xming]

Om zeker te zijn dat scarlet geen Caller ID door stuurt, kan je een tcpdump/sip trace proberen. Als je [email protected] ziet dan ligt de fout bij Scarlet.

[ikhlaske]

In bijlage zie je wat ik zie op mijn fritzbox. De caller id is nu Unknown

[Stefaand]

Ja dat is een betalende functie.
Maar die heeft altijd gewerkt.

Nu is mijn account overgezet op ims...maar ik betaal er nog steeds voor, dus moet dat ook geactiveerd zijn en werken.

Maar het werkt niet meer.

ik krijg bij iedereen die belt -1 op het display....en dat krijg je als de CLI niet wordt doorgestuurd.

misschien is deze setting niet juist :
Er blijken 8 mogelijkheden bij caller id method ?

[philippe_d]

@ikhlaske (FB7360)
@StefaanD (pap2p)

Caller-ID settings die je kan instellen zijn voor (a) uitgaande gesprekken of (b) voor Caller-ID op de aangesloten analoge toestellen.
Voor binnenkomende VoIP gesprekken is Caller-Id deel van de SIP signalling, en daar hoef je niets voor te doen.
De provider moet het wel activeren!
... en het is niet omdat je ervoor betaalt dat ze het ge-activeerd hebben .

In eerste instantie moet je de provider contacteren!

[Stefaand]

Philippe,

ja maar het IS geactiveerd.
Men heeft het zelfs even af gezet en weer op gezet.

Maar werkt niet hoor.

en betekent dit dat ik NIETS kan of moet doen ?
Het ligt 100% bij SCarlet ... ?

[ikhlaske]

Voordat het systeem op IMS werd overgezet werkte het wel via VoIP :/

[philippe_d]

Het is toch mogelijk dat de correcte CLIP setting niet overgenomen is op het IMS platform?
Dat het vroeger wel werkte, is toch het bewijs dat het niet aan jouw instellingen ligt .

Zoals ik zei: alleen Scarlet kan dit oplossen ...

[ikhlaske]

Merci philippe_d!

[Stefaand]

Tja als ik bel zeggen ze " meneer, het is geactiveerd, meer kunnen we niet doen"
Ik wacht nog een tijdje en anders ga ik de service afbellen en niet meer nemen,

Erg hoor als je van anderen afhangt.....heel erg....ik heb dit dus niet in de hand

[ Post made via mobile device ]

[Stefaand]

Vanuit een persoon (van scarlet) met kennis van zaken werd er een test gedaan met mijn nummer en de CLIP wordt WEL DEGELIJK meegstuurd.
Ik heb ook een foto te zien gekregen met de clip daarop.

Dus het ligt volgens scarlet wel degelijk aan mijn PAP2T toestel.
Maar er zijn 1001 settings die je kan instellen.

Het wordt dus een hopeloze zaak.
Tenzij er hier iemand ook met een PAP2T toestel van Linksys/Cisco werkt en het wel aan de praat heeft.

De nummer nummerherkenning is wel primordiaal voor ons want wij zijn geen telefoon-mensen en als het iemand is die we niet kennen nemen wij niet op.
Dus we gaan die service, waar we voor moeten betalen, afzeggen.

Maar dan nemen we de telefoon nooit meer op. Dus dat is dan ook niet echt een oplossing.

ik vrees dat de enige optie is over stappen op een andere provider OF.....of een andere VOIP toestelletje kopen.
want een modem/router/voip in 1 is geen optie, dat willen wij niet.

Ik ga nog even zoeken en testen en daarna is het richting vuilbak.

[lacer]

Ken je niemand die VoIp heeft bij een andere provider en die bereid zou zijn jouw Pap2T toestel even mijn zijn gegevens in te stellen op zijn locatie, dan zou je te weten komen of het wel aan het toestel ligt.
Indien je ten noorden van Gent woont ben ik wel kandidaat om dat even te testen.
Je kan het ook altijd voor een klein prijsje verkopen hier op Userbase in plaats van in de vuilbak te smijten

[Stefaand]

ik ben me aan het informeren.
Mijn vriend emailt me en zegt...pas op onze nummerherkenning is op een B&O BEOTALK 1200 en die kent ENKEL DTMF.
je kan dat oplossen met een toestelletje er tussen te zetten (https://www.gebruikershandleiding.com/B ... -8613.html) ...maar dan moet ik dat eerst zeker zijn dat het FSK is dat men gebruikt.


Dus als ims.scarlet.be waar ik naar overgestapt ben met FSK werkt, dan kan ik het vergeten en is mijn BEOTALK overbodig en nutteloos geworden.


ik heb dus een Siemens Gigaset 4010 classic op de lijn gezet , want misschien doet die wel FSK (als FSK gebruikt wordt....dat weet ik dus niet).
En ik krijg daar ook als nummerherkenning ANONIEM op. de BEOTALK geeft -1 en dat zijn wijze van anoniem te displayen (was vroeger ook zo).

Het is leuk hoor dingen uit te zoeken, maar je moet vooruitgang boeken en kennis inzamelen.
Ik heb nu aan mij goede contactpersoon bij scarlet gevraagd of ze van DTMF overgeschakelt zijn op FSK ?
Dan weet ik al iets meer ?

[xming]

Nogmaals, als je zeker wilt zijn wit of wat de schuldige is, tcpdump is het bewijs.

Wat je wel kan proberen is een softphone proberen die debugging/sip trace weergeeft (bvb http://www.linphone.org/downloads-for-desktop.html) en dan kan je zien wat je effectief binnen krijgt.

[Stefaand]

Ken je niemand die VoIp heeft bij een andere provider en die bereid zou zijn jouw Pap2T toestel even mijn zijn gegevens in te stellen op zijn locatie, dan zou je te weten komen of het wel aan het toestel ligt.
Indien je ten noorden van Gent woont ben ik wel kandidaat om dat even te testen.
Je kan het ook altijd voor een klein prijsje verkopen hier op Userbase in plaats van in de vuilbak te smijten

leuk hoor dat je je diensten aanbiedt...
ik woon midden tussen gent en brugge...

[Stefaand]

Nogmaals, als je zeker wilt zijn wit of wat de schuldige is, tcpdump is het bewijs.

Wat je wel kan proberen is een softphone proberen die debugging/sip trace weergeeft (bvb http://www.linphone.org/downloads-for-desktop.html) en dan kan je zien wat je effectief binnen krijgt.

ja dat lees ik.
maar ondanks dat ik een techneut ben, ik ben daarmee begonnen maar weet niet echt hoe het moet.
ik zou ook graag de log zien.

Maar ik weet niet hoe ik dit moet opzetten...sorry.

ik heb die linphone gedownload en geconfigureerd, maar ik ben geen telefonie-man...ik weet echt niet hoe dit werkt.
Tja...

[Stefaand]

Ik krijg net bericht dat het ims systeem van scarlet met FSK werkt !

dus mijn dtmf weergave box van B&O werkt dus niet meer.

misschien moet ik dan een Artech FSK-DTMF converter EX700 aanschaffen ?

[Stefaand]

het is wat hoor wat SCARLET zo maar doet met zijn klanten.

ik heb daar NIET om gevraagd.

[philippe_d]

Niet zo vlug paniekeren ...

DTMF en FSK zijn 2 verschillende protocollen, waarmee een CLIP doorgegeven wordt aan een analoog toestel. Dit heeft volgens mij dus niets met Scarlet te maken.

Jouw opstelling is dus:

• Scarlet IMS > PAP2T > analoge FSX poort > Siemens Gigaset (basis) > Siemens Gigaset DECT toestel.

Zoals je ziet zijn er verschillende plaatsen / overgangen waar die CLIP informatie moet overgedragen worden.

Scarlet beweert (met bewijzen) dat de CLIP informatie doorgestuurd wordt.
Jouw ATA (PAP2T) ontvangt dus deze informatie (via het SIP signalling protocol).
Totdaar de job van Scarlet.

Blijkbaar wordt deze informatie:

• a) ofwel door de PAP2T verkeerd geïnterpreteerd.
  b) ofwel door de PAP2T niet naar de analoge poort gestuurd.
  c) ofwel met een verkeerd protocol (FSK/DTMF) naar de analoge poort gestuurd, zodat de Siemens (basis) het niet begrijpt.

Volgens moet je het dus zoeken in de instellingen van de analoge poort van de Linksys ATA.

Dus het ligt volgens scarlet wel degelijk aan mijn PAP2T toestel.
Maar er zijn 1001 settings die je kan instellen..

Inderdaad. Heb je al alle mogelijkheden (8) van "Caller-ID method" uitgeprobeerd?

Ik krijg net bericht dat het ims systeem van Scarlet met FSK werkt !

Daar geloof ik dus geen snars van.
Misschien bedoelen ze dat de Scarlet VoIP modem (Sagem, B-box2) met FSK werkt?

[Stefaand]

Tja weet ge....
jij zegt "daar geloof ik geen snars van"....
tja wie moet ik dan geloven.

ik denk dat ik overstap op telenet hoor.

heb net naar Belgacom gebeld om in een winkel terecht te komen en ik kom op de helpdesk.
De winkel kan je dus NIET bellen.

ik wou weten of zij een FSK to DTMF toestel verkopen.
maar daarvoor moet ik in de auto springen en 60 km rijden (zei de man aan de telefoon) om dan een NEEN te horen denk ik ?

mijn Bang & Olufsen antwoord apparaat werkt dus niet meer en mijn BEOCOM telefoon werkt dus ook niet meer.

Die Siemsens dect zat er eventjes tussen omdat ik dacht dat die wel FSK kan decoderen.
Die is er al weer af.

De meeste mensen waren hun geduld al lang kwijt hoor.
Ik ben toch niet de enige die dit probleem heeft.
Scarlet zet de mensen over op IMS ZONDER de mensen te verwittigen en al hun toestellen die met DTMF nummerherkenning werkten werken dus niet meer.

[Stefaand]

in Belgie is een FSK naar DTMF converter nergens te googlen (typisch belgie).
in NL is het in veel winkels te verkrijgen....ik ben ze allemaal aan het emailen.

[xming]

Hold your horses

Caller-ID met SIP is heel eenvoudig (out-of-band DTMF eigenlijk ook), je hebt geen adaptors/convertors ervoor nodig.

Er zijn maar een paar plaatsen waar Caller-ID verloren kunnen gaan.

1. Provider geeft het niet door
2. PAP2 geeft het niet door of niet goed geconfigureerd voor je DECT (Siemens)
3. Siemens geeft het niet weer

Aangezien dat het vroeger wel werkte en na de omschakeling niet meer, kan je zeker van zijn dat 2 en 3 goed functioneren. Dus het ligt heel wss aan punt 1.

Om harde bewijzen te hebben en aangezien dat je niet veel goesting hebt om tcpdump te doen, stelde ik in mijn vorige post linphone voor te gebruiken.

Linphone is gewoon een SIP softphone, je gebruikt die ipv PAP2 (je moet PAP2 eerst deregisteren/afzetten), en je scarlet voip gevens in Linphone instoppen.

Linphone heeft een debug functie (althans de Linux versie) om SIP trace weer te geven, als je een techneut ben, kan je toch wel een Windows progje downloaden, installeren en wat velden invullen?

[Stefaand]

message: channel [0756BF20] [337] bytes parsed
message: channel [0756BF20]: discovered public ip and port are [213.49.120.11:5060]
message: Found transaction matching response.
message: Changing [client] [REGISTER] transaction [07500098], from state [TRYING] to [COMPLETED]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher [403] reason [Forbidden] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationProgress] to [LinphoneRegistrationFailed]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: Changing [client] [REGISTER] transaction [07500098], from state [COMPLETED] to [TERMINATED]
message: Client internal REGISTER transaction [07500098] terminated
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]

[Stefaand]

Code: Selecteer alles

message: Using (r/w) config information from C:\Users\stefaan\AppData\Roaming\Linphone\linphonerc
warning: Fail to open file C:\Program Files (x86)\Linphone\bin\\..\linphonerc.factory
message: Initializing LinphoneCore 3.7.0
message: srtp init
message: oRTP-0.23.0 initialized.
message: assigning PCMU/8000 payload type number 0
message: assigning GSM/8000 payload type number 3
message: assigning PCMA/8000 payload type number 8
message: assigning speex/8000 payload type number 110
message: assigning speex/16000 payload type number 111
message: assigning speex/32000 payload type number 112
message: assigning telephone-event/8000 payload type number 101
message: assigning G722/8000 payload type number 9
message: assigning H263/90000 payload type number 34
message: assigning H263-1998/90000 payload type number 98
message: assigning MP4V-ES/90000 payload type number 99
message: assigning H264/90000 payload type number 102
message: assigning VP8/90000 payload type number 103
message: assigning theora/90000 payload type number 97
message: assigning x-snow/90000 payload type number 96
message: assigning iLBC/8000 payload type number 100
message: assigning AMR/8000 payload type number 104
message: assigning AMR-WB/16000 payload type number 105
message: assigning 1015/8000 payload type number 106
message: assigning G726-16/8000 payload type number 107
message: assigning G726-24/8000 payload type number 108
message: assigning G726-32/8000 payload type number 109
message: assigning G726-40/8000 payload type number 113
message: assigning AAL2-G726-16/8000 payload type number 114
message: assigning AAL2-G726-24/8000 payload type number 115
message: assigning AAL2-G726-32/8000 payload type number 116
message: assigning AAL2-G726-40/8000 payload type number 117
message: assigning SILK/8000 payload type number 118
message: assigning SILK/12000 payload type number 119
message: assigning SILK/16000 payload type number 120
message: assigning SILK/24000 payload type number 121
message: assigning G729/8000 payload type number 18
message: assigning mpeg4-generic/22050 payload type number 122
message: assigning mpeg4-generic/44100 payload type number 123
message: assigning opus/48000 payload type number 124
message: assigning iSAC/16000 payload type number 125
message: assigning 1016/8000 payload type number 1
message: assigning G723/8000 payload type number 4
message: assigning LPC/8000 payload type number 7
message: assigning L16/44100 payload type number 10
message: assigning L16/44100 payload type number 11
message: assigning H261/90000 payload type number 31
message: assigning MPV/90000 payload type number 32
message: Mediastreamer2 2.10.0 (git: unknown) starting.
message: CPU count set to 8
message: ms_base_init() done
message: Registering all soundcard handlers
message: Card 'WINSND: Line 1 (Virtual Audio Cable)' added
message: Card 'WINSND: Speakers (Bose USB Audio)' added
message: Card 'WINSND: Realtek Digital Output(Optical)' added
message: Card 'WINSND: Realtek Digital Output (3- Real' added
message: Registering all webcam handlers
error: Fail to create class enumerator.
message: Webcam StaticImage: Static picture added
message: ms_voip_init() done
message: Loading ms plugins from [./lib/mediastreamer/plugins]
message: no plugin (*.dll) found in ./lib/mediastreamer/plugins\*.dll.
message: Sal nat helper [enabled]
message: no plugin (*.dll) found in ./lib/liblinphone/plugins\*.dll.
message: linphone_core_set_playback_gain_db(): no active call.
message: linphone_core_set_mic_gain_db(): no active call.
message: MTU is supposed to be 1300, rtp payload max size will be 1240
message: Sal nat helper [enabled]
message: Sal use rport [enabled]
message: Adding new codec PCMU/8000 with fmtp 
message: Could not find encoder for 1016
message: Could not find decoder for 1016
message: Adding new codec GSM/8000 with fmtp 
message: Could not find encoder for G723
message: Could not find decoder for G723
message: Could not find encoder for LPC
message: Could not find decoder for LPC
message: Adding new codec PCMA/8000 with fmtp 
message: Adding new codec G722/8000 with fmtp 
message: Adding new codec L16/44100 with fmtp 
message: Adding new codec L16/44100 with fmtp 
message: Could not find encoder for G729
message: Could not find decoder for G729
message: Could not find encoder for iLBC
message: Could not find decoder for iLBC
message: Could not find encoder for telephone-event
message: Could not find decoder for telephone-event
message: Could not find encoder for AMR
message: Could not find decoder for AMR
message: Could not find encoder for AMR-WB
message: Could not find decoder for AMR-WB
message: Could not find encoder for 1015
message: Could not find decoder for 1015
message: Could not find encoder for G726-16
message: Could not find decoder for G726-16
message: Could not find encoder for G726-24
message: Could not find decoder for G726-24
message: Could not find encoder for G726-32
message: Could not find decoder for G726-32
message: Adding new codec speex/8000 with fmtp vbr=on
message: Adding new codec speex/16000 with fmtp vbr=on
message: Adding new codec speex/32000 with fmtp vbr=on
message: Could not find encoder for G726-40
message: Could not find decoder for G726-40
message: Could not find encoder for AAL2-G726-16
message: Could not find decoder for AAL2-G726-16
message: Could not find encoder for AAL2-G726-24
message: Could not find decoder for AAL2-G726-24
message: Could not find encoder for AAL2-G726-32
message: Could not find decoder for AAL2-G726-32
message: Could not find encoder for AAL2-G726-40
message: Could not find decoder for AAL2-G726-40
message: Could not find encoder for SILK
message: Could not find decoder for SILK
message: Could not find encoder for SILK
message: Could not find decoder for SILK
message: Could not find encoder for SILK
message: Could not find decoder for SILK
message: Could not find encoder for SILK
message: Could not find decoder for SILK
message: Could not find encoder for mpeg4-generic
message: Could not find decoder for mpeg4-generic
message: Could not find encoder for mpeg4-generic
message: Could not find decoder for mpeg4-generic
message: Adding new codec opus/48000 with fmtp useinbandfec=1; usedtx=1
message: Could not find encoder for iSAC
message: Could not find decoder for iSAC
message: Could not find encoder for H261
message: Could not find decoder for H261
message: Could not find encoder for MPV
message: Could not find decoder for MPV
message: Adding new codec H263/90000 with fmtp 
message: Adding new codec x-snow/90000 with fmtp 
message: Adding new codec theora/90000 with fmtp 
message: Adding new codec H263-1998/90000 with fmtp CIF=1;QCIF=1
message: Adding new codec MP4V-ES/90000 with fmtp profile-level-id=3
message: Could not find encoder for H264
message: Adding new codec VP8/90000 with fmtp 
message: Sal use rport [enabled]
message: sal_unlisten_ports done
message: Creating listening point [053B9720] on [sip:0.0.0.0:5060;transport=UDP]
warning: belle_sip_socket_set_dscp(): not implemented.
message: Creating listening point [053B97F8] on [sip:0.0.0.0:5060;transport=TCP]
warning: belle_sip_socket_set_dscp(): not implemented.
message: Creating listening point [053E02B8] on [sip:0.0.0.0:21624;transport=TLS]
warning: belle_sip_socket_set_dscp(): not implemented.
message: Root ca path set to ./share/linphone/rootca.pem
message: Notifying all friends that we are [online]
warning: Table already up to date: duplicate column name: url.

message: New local ip address is 192.168.1.103
message: Network state is now [UP]
message: Sal nat helper [enabled]
message: Sal use rport [enabled]
message: MTU is supposed to be 1300, rtp payload max size will be 1240
message: MTU is supposed to be 1300, rtp payload max size will be 1240
message: Sal nat helper [enabled]
message: Sal use rport [enabled]
message: MTU is supposed to be 1300, rtp payload max size will be 1240
message: MTU is supposed to be 1300, rtp payload max size will be 1240
message: Notifying all friends that we are [online]
message: Sal nat helper [enabled]
message: Sal use rport [enabled]
message: MTU is supposed to be 1300, rtp payload max size will be 1240
message: MTU is supposed to be 1300, rtp payload max size will be 1240
message: belle_sip_client_transaction_send_request(): waiting channel to be ready
message: channel 0756BF20: state RES_IN_PROGRESS
message: transaction [07500098] channel state changed to [RES_IN_PROGRESS]
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: Neither Expires header nor corresponding Contact header found, checking from original request
message: Refresher [074FFFD8] takes ownership of transaction [07500098]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationNone] to [LinphoneRegistrationProgress]
message: No SRV result for [_sip._udp.ims.scarlet.be], trying A/AAAA.
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: ims.scarlet.be resolved to 80.200.255.199
message: channel 0756BF20: state RES_DONE
message: transaction [07500098] channel state changed to [RES_DONE]
message: channel 0756BF20: state CONNECTING
message: transaction [07500098] channel state changed to [CONNECTING]
message: Trying to connect to [UDP://80.200.255.199:5060]
message: Channel has local address 192.168.1.103:5060
message: channel 0756BF20: state READY
message: transaction [07500098] channel state changed to [READY]
message: Changing [client] [REGISTER] transaction [07500098], from state [INIT] to [TRYING]
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.9vi~DGTnd;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 20 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [0756BF20]: received [337] new bytes from [UDP://ims.scarlet.be:5060]:
SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.1.103:5060;received=213.49.120.11;branch=z9hG4bK.9vi~DGTnd;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: <sip:[email protected]>;tag=SDigj5599-530407ad-142366019127675

CSeq: 20 REGISTER

Call-ID: U2Igny5-Pa

Date: Wed, 11 Feb 2015 13:09:51 GMT

Content-Length: 0




message: channel [0756BF20] [337] bytes parsed
message: channel [0756BF20]: discovered public ip and port are [213.49.120.11:5060]
message: Found transaction matching response.
message: Changing [client] [REGISTER] transaction [07500098], from state [TRYING] to [COMPLETED]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher  [403] reason [Forbidden] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationProgress] to [LinphoneRegistrationFailed]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: Changing [client] [REGISTER] transaction [07500098], from state [COMPLETED] to [TERMINATED]
message: Client internal REGISTER transaction [07500098] terminated
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: Changing [client] [REGISTER] transaction [075BD058], from state [INIT] to [TRYING]
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Ysz8vGc~r;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 21 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [0756BF20]: received [338] new bytes from [UDP://ims.scarlet.be:5060]:
SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.1.103:5060;received=213.49.120.11;branch=z9hG4bK.Ysz8vGc~r;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: <sip:[email protected]>;tag=SDigj5599-530407aa-1423660251328871

CSeq: 21 REGISTER

Call-ID: U2Igny5-Pa

Date: Wed, 11 Feb 2015 13:10:51 GMT

Content-Length: 0




message: channel [0756BF20] [338] bytes parsed
message: Found transaction matching response.
message: Changing [client] [REGISTER] transaction [075BD058], from state [TRYING] to [COMPLETED]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher  [403] reason [Forbidden] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: Changing [client] [REGISTER] transaction [075BD058], from state [COMPLETED] to [TERMINATED]
message: Client internal REGISTER transaction [075BD058] terminated
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: Changing [client] [REGISTER] transaction [075BD0B8], from state [INIT] to [TRYING]
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [0756BF20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [0756BF20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.~vjXb~u5z;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 22 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




warning: Transaction [075BD0B8] reporting timeout, reporting to channel.
message: A timeout related to this channel occured and no message received during last 60 seconds. This channel is suspect, moving to error state
message: channel 0756BF20: state ERROR
message: transaction [07500098] channel state changed to [ERROR]
message: transaction [075BD0B8] channel state changed to [ERROR]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher  [503] reason [io error] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Refresher: scheduling next timer in 2000 ms
message: Register refresher  [408] reason [timeout] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Changing [client] [REGISTER] transaction [075BD0B8], from state [TRYING] to [TERMINATED]
message: Client internal REGISTER transaction [075BD0B8] terminated
message: belle_sip_client_transaction_send_request(): waiting channel to be ready
message: channel 075E8F20: state RES_IN_PROGRESS
message: transaction [075BD6B8] channel state changed to [RES_IN_PROGRESS]
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: No SRV result for [_sip._udp.ims.scarlet.be], trying A/AAAA.
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: ims.scarlet.be resolved to 80.200.255.199
message: channel 075E8F20: state RES_DONE
message: transaction [075BD6B8] channel state changed to [RES_DONE]
message: channel 075E8F20: state CONNECTING
message: transaction [075BD6B8] channel state changed to [CONNECTING]
message: Trying to connect to [UDP://80.200.255.199:5060]
message: Channel has local address 192.168.1.103:5060
message: channel 075E8F20: state READY
message: transaction [075BD6B8] channel state changed to [READY]
message: Changing [client] [REGISTER] transaction [075BD6B8], from state [INIT] to [TRYING]
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Apih~Lqpa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 23 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




warning: Transaction [075BD6B8] reporting timeout, reporting to channel.
message: A timeout related to this channel occured and no message received during last 60 seconds. This channel is suspect, moving to error state
message: channel 075E8F20: state ERROR
message: transaction [075BD6B8] channel state changed to [ERROR]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher  [503] reason [io error] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Refresher: scheduling next timer in 2000 ms
message: Register refresher  [408] reason [timeout] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Changing [client] [REGISTER] transaction [075BD6B8], from state [TRYING] to [TERMINATED]
message: Client internal REGISTER transaction [075BD6B8] terminated
message: Channel [075E8F20] destroyed
message: belle_sip_client_transaction_send_request(): waiting channel to be ready
message: channel 075E8F20: state RES_IN_PROGRESS
message: transaction [075BDD18] channel state changed to [RES_IN_PROGRESS]
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: No SRV result for [_sip._udp.ims.scarlet.be], trying A/AAAA.
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: ims.scarlet.be resolved to 80.200.255.199
message: channel 075E8F20: state RES_DONE
message: transaction [075BDD18] channel state changed to [RES_DONE]
message: channel 075E8F20: state CONNECTING
message: transaction [075BDD18] channel state changed to [CONNECTING]
message: Trying to connect to [UDP://80.200.255.199:5060]
message: Channel has local address 192.168.1.103:5060
message: channel 075E8F20: state READY
message: transaction [075BDD18] channel state changed to [READY]
message: Changing [client] [REGISTER] transaction [075BDD18], from state [INIT] to [TRYING]
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.Bmo9ZNlEx;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 24 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




warning: Transaction [075BDD18] reporting timeout, reporting to channel.
message: A timeout related to this channel occured and no message received during last 60 seconds. This channel is suspect, moving to error state
message: channel 075E8F20: state ERROR
message: transaction [075BDD18] channel state changed to [ERROR]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher  [503] reason [io error] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Refresher: scheduling next timer in 2000 ms
message: Register refresher  [408] reason [timeout] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Changing [client] [REGISTER] transaction [075BDD18], from state [TRYING] to [TERMINATED]
message: Client internal REGISTER transaction [075BDD18] terminated
message: Channel [075E8F20] destroyed
message: belle_sip_client_transaction_send_request(): waiting channel to be ready
message: channel 075E8F20: state RES_IN_PROGRESS
message: transaction [07435A80] channel state changed to [RES_IN_PROGRESS]
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: No SRV result for [_sip._udp.ims.scarlet.be], trying A/AAAA.
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: ims.scarlet.be resolved to 80.200.255.199
message: channel 075E8F20: state RES_DONE
message: transaction [07435A80] channel state changed to [RES_DONE]
message: channel 075E8F20: state CONNECTING
message: transaction [07435A80] channel state changed to [CONNECTING]
message: Trying to connect to [UDP://80.200.255.199:5060]
message: Channel has local address 192.168.1.103:5060
message: channel 075E8F20: state READY
message: transaction [07435A80] channel state changed to [READY]
message: Changing [client] [REGISTER] transaction [07435A80], from state [INIT] to [TRYING]
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: Sal nat helper [enabled]
message: Sal use rport [enabled]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.zEjI63Wwa;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 25 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




warning: Transaction [07435A80] reporting timeout, reporting to channel.
message: A timeout related to this channel occured and no message received during last 60 seconds. This channel is suspect, moving to error state
message: channel 075E8F20: state ERROR
message: transaction [07435A80] channel state changed to [ERROR]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher  [503] reason [io error] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Refresher: scheduling next timer in 2000 ms
message: Register refresher  [408] reason [timeout] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Changing [client] [REGISTER] transaction [07435A80], from state [TRYING] to [TERMINATED]
message: Client internal REGISTER transaction [07435A80] terminated
message: Channel [075E8F20] destroyed
message: belle_sip_client_transaction_send_request(): waiting channel to be ready
message: channel 075E8F20: state RES_IN_PROGRESS
message: transaction [07436260] channel state changed to [RES_IN_PROGRESS]
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: No SRV result for [_sip._udp.ims.scarlet.be], trying A/AAAA.
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: ims.scarlet.be resolved to 80.200.255.199
message: channel 075E8F20: state RES_DONE
message: transaction [07436260] channel state changed to [RES_DONE]
message: channel 075E8F20: state CONNECTING
message: transaction [07436260] channel state changed to [CONNECTING]
message: Trying to connect to [UDP://80.200.255.199:5060]
message: Channel has local address 192.168.1.103:5060
message: channel 075E8F20: state READY
message: transaction [07436260] channel state changed to [READY]
message: Changing [client] [REGISTER] transaction [07436260], from state [INIT] to [TRYING]
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.ck5bcmJv2;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 26 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




warning: Transaction [07436260] reporting timeout, reporting to channel.
message: A timeout related to this channel occured and no message received during last 60 seconds. This channel is suspect, moving to error state
message: channel 075E8F20: state ERROR
message: transaction [07436260] channel state changed to [ERROR]
message: Refresher: scheduling next timer in 60000 ms
message: Register refresher  [503] reason [io error] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Refresher: scheduling next timer in 2000 ms
message: Register refresher  [408] reason [timeout] for proxy [sip:ims.scarlet.be]
message: Proxy config [054FA248] for identity [sip:[email protected]] moving from state [LinphoneRegistrationFailed] to [LinphoneRegistrationFailed]
message: Changing [client] [REGISTER] transaction [07436260], from state [TRYING] to [TERMINATED]
message: Client internal REGISTER transaction [07436260] terminated
message: Channel [075E8F20] destroyed
message: belle_sip_client_transaction_send_request(): waiting channel to be ready
message: channel 075E8F20: state RES_IN_PROGRESS
message: transaction [074FFF18] channel state changed to [RES_IN_PROGRESS]
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: No SRV result for [_sip._udp.ims.scarlet.be], trying A/AAAA.
message: Resolver is using DNS server(s):
message: 	193.121.171.135
message: 	193.74.208.65
message: resolver_process_data dns_res_check() in progress
message: DNS resolution awaiting response, queued to main loop
message: ims.scarlet.be resolved to 80.200.255.199
message: channel 075E8F20: state RES_DONE
message: transaction [074FFF18] channel state changed to [RES_DONE]
message: channel 075E8F20: state CONNECTING
message: transaction [074FFF18] channel state changed to [CONNECTING]
message: Trying to connect to [UDP://80.200.255.199:5060]
message: Channel has local address 192.168.1.103:5060
message: channel 075E8F20: state READY
message: transaction [074FFF18] channel state changed to [READY]
message: Changing [client] [REGISTER] transaction [074FFF18], from state [INIT] to [TRYING]
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.nlzUFbee8;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 27 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.nlzUFbee8;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 27 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.nlzUFbee8;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 27 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: channel [075E8F20]: keep alive sent to [UDP://ims.scarlet.be:5060]
message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.nlzUFbee8;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 27 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)




message: nict_on_timer_E: sending retransmission
message: channel [075E8F20]: message sent to [UDP://ims.scarlet.be:5060], size: [444] bytes
REGISTER sip:ims.scarlet.be SIP/2.0

Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK.nlzUFbee8;rport

From: <sip:[email protected]>;tag=zLbnke5JB

To: sip:[email protected]

CSeq: 27 REGISTER

Call-ID: U2Igny5-Pa

Max-Forwards: 70

Supported: replaces, outbound

Contact: <sip:[email protected]>;+sip.instance="<urn:uuid:90792172-9b0c-4cfa-884f-0834fccb130a>"

Expires: 3600

User-Agent: Linphone/3.7.0 (belle-sip/1.3.0)

[Stefaand]

dat is de logging.
maar ik kan niet bellen naar het nummer. ik hoor niets in de gsm...belt niet...niets.

[lacer]

Tja, dan is Linphone niet goed geconfigureerd denk ik zo

Offtopic:
Stefaan, je mag al jouw reacties samen zetten hoor. Je moet niet voor elke zin een nieuw bericht schrijven, je kan die steeds bewerken en tekst toevoegen

[Stefaand]

Zo het FSK <-> DTMF converter is toegekomen.
Er zitten 6 dip switches op die je kan combineren.

Ik heb al heel wat getest met de PAP2T met Caller ID Method op DTMF(Denmark) with PR en Caller ID FSK Standard op V.23 en dan krijg ik 3 in het display van mijn BEOTALK 1200.
Ik heb ook al eens 00 gehad.

Dus dat is al iets anders dan altijd die -1

Maar het werkt nog niet, dus ik hoop dat ik met dit toestelletje er wel in slaag.

Dit zijn de meeste settings zoals die in NL gebruikt worden : http://www.multicaresystems.nl/plaatjes ... 00_2.1.pdf



Nee het lukt niet.
ik zal een ander telefoontoestel moeten aanschaffen denk ik. Maar ja, ik wil dat eerst uit proberen natuurlijk.
Of ik moet een andere VOIP toestel hebben.
Ik weet het niet meer.

ik heb nog eens geprobeerd linphone aan de praat te krijgen.
Dit werkt van geen kanten he.
ik kan het niet goed configureren om in te loggen.


Bedankt SCARLET !

[Stefaand]

Vandaag heb ik een Gigaset E630 aangekocht.
Want ja, ik denk dat mijn "oude"toestellen het niet meer doen.

Ik denk dat dit nieuwe toestel wel FSK en DTMF aan kan.

Resultaat : identiek. (Anoniem of Extern krijg ik op het display van de gigaset).



ok dan maar de pap2t eruit en de sagem modem er weer tussen.
En dan loopt alles ok.

dus ligt aan de pap2t die de juiste codering niet kan toepassen.

Helaas.

[Bssoft]

In Nederland gebruikte KPN het DTMF systeem, waarom ? moet je vragen aan KPN, want er zijn niet veel landen die DTMF gebruiken !

Bij Belgacom en Telenet is het altijd het FSK protokol geweest, voor de OLO's is het dus beter dat ze dat systeem dan ook gebruiken
voor Belgie !!!!

http://www.cisco.com/c/dam/en/us/td/doc ... NC-WEB.pdf
In deze handleiding over de ATA's vanaf bladzijde 53 kan je lezen dat, binnen zowel DTMF als FSK, er nog verschillen zijn ook !

Zo te lezen staat per "default" Belcore en Bell 202 in de ATA ?
VB: Belgacom gebruikt als FSK ===> V23 .......................... Scarlet ook FSK maar dewelke ?
---- Belgacom FSK is tussen de 1ste twee belspanningen ===> FSK after ringing ....

Feitelijk is dat heel technisch die kleine verschillen binnen hetzelfde protocol, of het nu FSK of DTMF is, in elk geval het is niet aan
Jan met de pet om het te verstaan !

[Stefaand]

die PAP2T heeft zo verschrikkelijk veel mogelijkheden om in te stellen dat ik het nog altijd niet geloof dat het niet lukt.
Ik heb zoveel combinaties geprobeerd en zo....maar niets hielp.
de pap2t ligt dus weer in de kast.

[Bssoft]

Zoveel zijn er toch niet voor FSK volgens wat ik zie in je screenshot ? DTMF mag je vergeten en telt niet mee !

Eerst als je kan de "Caller ID FSK standard" in V23 zetten (standaard bell 202) !
Dan in "Caller ID method" eentje kiezen van FSK = 3 mogelijkheden (standaard Belcore) !

PS: zou kunnen dat je na een "save" de 220V moet uit zetten en terug aan zetten ?
Meer keuze is er niet volgens mij ....en als het niets doet dan is de kous af

[MarkDM]

Je zoekt veel te ver met DTMF en FSK. Eerst moet je weten of de caller-id toekomt in de PAP2T. Dat is los daarvan, via het Sip-protocol.
Die PAP2T is niet zo eenvoudig om te debuggen. Installeer Kiwi Syslog Server op een pc (freeware).
Ga dan op de PAP2T naar tabblad 'System'. Vul het ip-adres van je pc in als syslog-server en debug-server.

Dan zie wat er gebeurt in de PAP2T. Normaal moet de caller-id daar passeren.
Eventueel zet je 'Debug level' op 3, dan komt alles er op.
Veel succes !

[MarkDM]

Ik mis nog iets in dit verhaal. Welke caller id staat er op de info-pagina van de PAP2T ?
Er is daar een veldje " Last Caller Number:" , per telefoon. Als daar niets komt moet je niet verder zoeken naar fsk of dtmf. Dan heeft de PAP2T het nummer gewoon niet. Wel best het gesprek aannemen om te forceren dat het veldje ingevuld wordt.
Dit is toch een gemakkelijke test ?

[philippe_d]

Gezien vroeger alles werkte (telephony voip.scarlet.be), en het probleem pas begon na de overschakeling (telephony via ims.scarlet.be), denk ik toch dat er iets mis is aan de Scarlet kant (hoewel ze beweren dat CLIP aan staat).

Scarlet kan op géén enkele manier het CLIP gedrag (op de analoge FSX uitgang) van jouw PAP2T beïnvloeden (zoals overschakelen van DTMF naar FSK of omgekeerd).

[Stefaand]

Ik mis nog iets in dit verhaal. Welke caller id staat er op de info-pagina van de PAP2T ?
Er is daar een veldje " Last Caller Number:" , per telefoon. Als daar niets komt moet je niet verder zoeken naar fsk of dtmf. Dan heeft de PAP2T het nummer gewoon niet. Wel best het gesprek aannemen om te forceren dat het veldje ingevuld wordt.
Dit is toch een gemakkelijke test ?

Dat veldje had ik ook al lang zien staan en dat blijft blanco.
Geloof me, ik heb alle combinaties uitgeprobeerd. Het werkt niet met de pap2.
De sagem modem heeft zo'n sumiere input van veldjes en daar gaat het wel.

Het ligt dus wel degelijk aan de pap2T hoor. die krijgt het gewoon niet binnen of kan er niets mee, dat veldje LAST CALLER ID blijft altijd blanco staan.

[MarkDM]

Dan moet je niet verder zoeken. Dit heeft niets met FSK of DTMF te maken.
Misschien zijn er dialecten of formats in het Sip-protocol .