Voxalot / SIP Broker Support Forums

Voxalot / SIP Broker Support Forums (https://forum.sipbroker.com/index.php)
-   Voxalot Support (https://forum.sipbroker.com/forumdisplay.php?f=4)
-   -   Strange Voxalot Dial Plan behaviour (https://forum.sipbroker.com/showthread.php?t=1578)

gambrinus 05-15-2007 08:57 PM

Strange Voxalot Dial Plan behaviour
 
Hello,
I setup a Voxalot accounts for my whole family :-) Thank you for the great service! Unfortunately I see a strange behaviour at my sister trying to call someone using VoiceTrading.

She has two dial plans
Prio 1:
Pattern: _9#01.
Replacement: ${EXTEN:4}
Provider: VoiceTrading
ENUM: no
This dial plan is to use prefixes (9#01) to choose specific providers and disable ENUM.

Prio 995:
Pattern: _Z.
Replacement: 00499973${EXTEN}
Provider: Voipdiscount
ENUM: 499973${EXTEN}
This dial plan ensures all numbers dialled without area code (local calls) will be properly put in international format including area code (9973).

When using 9#01 to select VoiceTrading as the VSP for this call she gets an 404 Not Found message and this is what happens:
She is dialling 9#010049821998xxxx.

Code:

RECEIVE TIME: 5420540
RECEIVE << 85.17.19.194:5060
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 131.130.145.148:5060;rport=49242;branch=z9hG4bK6E1F8170C1B34B5B8A44D821DAC13B97
From: Katarina xxxxxx <sip:8014xx@eu.voxalot.com>;tag=1531692762
To: <sip:9%23010049821998xxxx@eu.voxalot.com>;tag=as5cab230c
Call-ID: 87BD9390-2B8D-4059-BB11-5073798EEDAC@192.168.0.151
CSeq: 22408 INVITE
User-Agent: VoXaLot
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Contact: <sip:*1*8014xx-001004999739%23010049821998xxxx@85.17.19.194:5061>
Content-Length: 0

Have a close look at this line:
Code:

Contact: <sip:*1*8014xx-001004999739%23010049821998xxxx@85.17.19.194:5061>
It seems that 00499973 has been taken from dial plan 995 although dial plan 1 already matched the number!!!
If I disable dial plan 995 she gets: "the number you tried could not be connected" (sorry have no log for that).

Any ideas?

Thanks,
gambrinus


PS:
I have x-ed out some digits for privacy reasons. I can PM the whole Diagnostic log to one of the mods if it helps.

martin 05-15-2007 09:32 PM

I do see your problem. The device is passing the Voxalot %23 instead of a #. Some devices are known to do this.

As a result, what is happening, is that the dialed number is in fact matching dial plan 995 and not 1 as you wanted.

This is confirmed by the fact that when you disable 995 the call can not route.

Try changing the # in the dial plan to something else.

gambrinus 05-15-2007 09:51 PM

Quote:

Originally Posted by martin (Post 8912)
I do see your problem. The device is passing the Voxalot %23 instead of a #. Some devices are known to do this.

Thanks a lot. I must have been blind... ;-)
She uses a softphone, all others use hardware. That was the catch... :-)

Thanks a million!
gambrinus


All times are GMT. The time now is 04:49 AM.

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.